($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: Quentin Schulz <foss+yocto@0leil.net>
To: yocto@lists.yoctoproject.org, zoran.stojsavljevic@gmail.com
Subject: Re: [yocto] Still problems with my experimental bbb-yocto repo on branch scarthgap
Date: Thu, 23 May 2024 13:51:27 +0200	[thread overview]
Message-ID: <ECEF5EF0-20F0-4C4B-A5C0-CCC7C1844DD3@0leil.net> (raw)
In-Reply-To: <CAGAf8LyERGTEWr-3wUX1wH-=1Shri=uq1Y+MrM8Jz0aWrxv8Og@mail.gmail.com>

Hi Zoran,

On May 23, 2024 10:21:27 AM GMT+02:00, Zoran <zoran.stojsavljevic@gmail.com> wrote:
>Hello Yocto Folks.
>
>Still interesting problems with my experimental bbb-yocto repo on
>branch  scarthgap.
>
>Let me remind you all what the issues were:
>https://lists.yoctoproject.org/g/yocto/message/63118
>
>Everything works after some temp fixes I made (with sticks and ropes),
>but with the latest kernel 6.1.45 I used, as a scarthgap Stage 1.
>
>Now, I replaced kernel 6.1.45 with kernel 6.9.0 (Stage 2),
>
>I needed to rebase some patches, since they do NOT work for kernel 6.9.0 .
>
>And here very interesting things started to happen. Namely, kernel
>6.9.0 failed compiling in the last phase.
>
>The bbb-yocto_kernel-6.9.0.log file is attached.
>
>Here is the issue (from bbb-yocto_kernel-6.9.0..log file):
>
>|   SYNC    include/config/auto.conf
>|   GEN     Makefile
>| make[2]: *** No rule to make target
>'arch/arm/boot/dts/am335x-boneblack.dtb'.  Stop.
>
>The file am335x-boneblack.dtb for kernel 6.9.0 is rebased in
>arch/arm/boot/dts/ti/omap/am335x-boneblack.dtb from
>arch/arm/boot/dts/am335x-boneblack.dtb .
>
>And this net pointer reflects the correct position of it (rebased 0002-patch):
>https://github.com/ZoranStojsavljevic/meta-bbb/blob/scarthgap/recipes-kernel/linux/linux-stable-6.9/0002-dts-Remove-bbb-cape-i2c-definitions.patch
>
>And this is the kernel recipe:
>https://github.com/ZoranStojsavljevic/meta-bbb/blob/scarthgap/recipes-kernel/linux/linux-stable_6.9.bb
>
>from:
>https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a38297e3fb012ddfa7ce0321a7e5a8daeb1872b6
>
>I recompiled the whole thing from scratch. Introducing again
>.../poky/build and rebuilding from beginning with bitbake -k
>core-image-minimal
>
>Still: | make[2]: *** No rule to make target
>'arch/arm/boot/dts/am335x-boneblack.dtb'.  Stop.
>
>Where does this path come from? No idea!
>
>Should be: arch/arm/boot/dts/ti/omap/am335x-boneblack.dtb (as in 6.9.0) !?
>

KERNEL_DEVICETREE needs the vendor prefix with newer kernels for Aarch32 machines (it's always been the case for Aarch64), so it should be ti/am335x-boneblack.dtb I believe.

Let us know how this works,
Cheers,
Quentin

>Thank you,
>Zee
>_______


  reply	other threads:[~2024-05-23 11:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-23  8:21 Still problems with my experimental bbb-yocto repo on branch scarthgap Zoran
2024-05-23 11:51 ` Quentin Schulz [this message]
2024-05-23 17:03   ` [yocto] " Zoran

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ECEF5EF0-20F0-4C4B-A5C0-CCC7C1844DD3@0leil.net \
    --to=foss+yocto@0leil.net \
    --cc=yocto@lists.yoctoproject.org \
    --cc=zoran.stojsavljevic@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).