Skip to content
Snippets Groups Projects

Add configs for sargo and bonito

Closed erebion requested to merge erebion/mobian-recipes:erebion-master-patch-62863 into master
1 unresolved thread

I'm not sure whether I have to add append = "console=tty0,115200", but at least it does not boot successfully if I set it to ttyMSM0, like for some other devices. Someone please enlighten me.

Edited by erebion

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • Arnaud Ferraris
  • erebion added 1 commit

    added 1 commit

    • 57aa03e3 - Add configs for sargo and bonito

    Compare with previous version

  • erebion added 1 commit

    added 1 commit

    • 3db49249 - Add configs for sargo and bonito

    Compare with previous version

  • erebion resolved all threads

    resolved all threads

  • Arnaud Ferraris approved this merge request

    approved this merge request

  • Looks good thanks, will merge once we have the kernel for that one.

    • Resolved by erebion

      @a-wai This looks interesting and I'd like to test this on my bonito/3axl, do I just flash the qcom image with fastboot or I need to create a custom kernel?

  • erebion resolved all threads

    resolved all threads

    • Author Contributor

      @a-wai

      "Conflict: This file was modified in both the source and target branches. Ask someone with write access to resolve it."

      I guess you're someone with write access, so... Help pls.

    • Author Contributor

      Curious it tells me I cannot solve it.

    • No, that means GitLab cannot rebase automatically, so you have to do it yourself using git rebase then force-push.

    • (in this context, "write access" means "write access to your forked repo")

    • it should be as easy as

      --- qcom_sdm670.toml    2024-10-03 21:03:34.085988146 +0200
      +++ qcom_master.toml    2024-10-03 21:05:02.543485575 +0200
      @@ -27,19 +27,16 @@
       vendor = "xiaomi"
       model = "beryllium"
       variant = "ebbg"
      -append = "console=ttyMSM0,115200"
       
       [[device]]
       vendor = "xiaomi"
       model = "beryllium"
       variant = "tianma"
      -append = "console=ttyMSM0,115200"
       
       [[device]]
       vendor = "fairphone"
       model = "fp4"
       chipset = "sm7225"
      -append = "sdhci.debug_quirks=0x40"
       
       [[device]]
       vendor = "google"

      but TBH, it's just a matter of appending 11 lines to a config file, isn't rebasing an option?

    • Author Contributor

      As it will only get merged once the patches are in Mobian, I will do it then.

    • Now that we have the sdm670 kernel, I guess this MR will have to be refactored in order to have a devices/sdm670 folder? Or is it enough to have the chipset = 'sdm670' specification in devices/qcom/configs/qcom.toml so that everything can be kept in devices/qcom without duplications?

    • Please register or sign in to reply
  • Closing as this was superseded by !132 (merged)

  • Please register or sign in to reply
    Loading