Navigation

    UBports Robot Logo

    UBports Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    Stuck at checking kernel configuration.

    Porting
    3
    9
    397
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • C
      Carlo last edited by

      I can't understand how to check the kernel config and apply the changes as shown as in the Modify the kernel configuration part of the porting guide. I guess it might not be generating since under BUILDDIR/kernel/ folder I cannot find my device. Am I missing something? I am new to the argument of porting so please be kind if this was a trivial question. Thanks!

      Lakotaubp 1 Reply Last reply Reply Quote 0
      • Lakotaubp
        Lakotaubp @Carlo last edited by

        @carlo Which device are you porting? it might help with an answer, Thanks.

        C 1 Reply Last reply Reply Quote 0
        • C
          Carlo @Lakotaubp last edited by

          @lakotaubp I get the same error both for nexus 9 and for samsung s4. I initially speculated that it was a nexus 9 related error, maybe due to the manifest or something, but got the same result with the s4.

          1 Reply Last reply Reply Quote 0
          • Flohack
            Flohack last edited by

            Well to get a kernel you have to add it to a local manifest in the halium/devices repo and then let it be set up by the setup script in that repo. Otherwise kernel will be empty, yes πŸ˜‰

            My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

            C 1 Reply Last reply Reply Quote 0
            • C
              Carlo @Flohack last edited by Carlo

              @flohack I have created the repo manifests. For example a rough manifest for jfltexx is

              <?xml version="1.0" encoding="UTF-8"?>
              <manifest>
              <remote name="LineageOS"
                  fetch="https://github.com/LineageOS"
                  revision="los-16.0" />
              <!--Dependencies-->
              <project path="device/samsung/jfltexx" name="android_device_samsung_jfltexx" remote="LineageOS" revision="lineage-16.0" />
              <project path="device/samsung/jf-common" name="android_device_samsung_jf-common" remote="LineageOS" revision="lineage-16.0" />
              </manifest>
              

              I have created it under BUILDDIR/halium/devices/manifests/samsung_jfltexx.xml

              The jf-common line comes from the lineage.dependencies file.

              Flohack 1 Reply Last reply Reply Quote 0
              • Flohack
                Flohack @Carlo last edited by

                @carlo Yes you are missing the kernel in the anifest.

                My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                C 1 Reply Last reply Reply Quote 0
                • C
                  Carlo @Flohack last edited by

                  @flohack Ok, thanks, now I understand better. So I will add a line that goes something like:

                  <project path="kernel/samsung/jf" name="android_kernel_samsung_jf" remote="LineageOS" revision="lineage-16.0" />
                  

                  Thanks.

                  1 Reply Last reply Reply Quote 0
                  • Flohack
                    Flohack last edited by

                    You probably want to fork those repos, since you will have to make modifications 100% πŸ˜‰

                    BR

                    My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                    C 1 Reply Last reply Reply Quote 0
                    • C
                      Carlo @Flohack last edited by

                      @flohack thanks a lot, I will do. BR

                      1 Reply Last reply Reply Quote 0
                      • First post
                        Last post