From: "Bruce Ashfield" <bruce.ashfield@gmail.com>
To: florian.kauer@koalo.de
Cc: yocto <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] Can the Linux kernel reuse the barebox device tree? #kernel
Date: Fri, 4 Jun 2021 09:03:51 -0400 [thread overview]
Message-ID: <CADkTA4NEZ0h7rEiSw4Q0CwLbReoSNkZAuyS=NO0LN-GPf1dKGA@mail.gmail.com> (raw)
In-Reply-To: <td3c.1622797217734922140.8fqZ@lists.yoctoproject.org>
On Fri, Jun 4, 2021 at 5:00 AM <florian.kauer@koalo.de> wrote:
>
> Hi,
> I made the following observation in my custom Yocto system:
> The device tree loaded by the Linux kernel is one that is only available in the barebox directory, but not available in the kernel sources. In fact, it is quite similar, but I made some changes to it in the device tree provided to the kernel. Especially the machine model that is shown during kernel boot is a string that can only be found in the compiled barebox image, but not in the dtb files (where I can find the correct machine model string) or anywhere else in the compilation results. But also other messages indicate that the wrong device tree is loaded.
>
> It was correct before, and I am not really sure what triggered that (just upgraded from zeus, but it might or might not be triggered by that) and I wouldn't expect that anyone could guess what I have done wrong without debugging my setup in depth. But, my general question is: Is there any mechanism that could explain such a behavior? Any configuration that means "extract the device tree from the bootloader" or something similar?
>
In your upgrade, did the bootloader/initramfs/kernel version change ?
The passing of the device tree to the kernel is (commonly) part of the
bootflow, so changes to any of the components in that flow could cause
the different device tree usage you are seeing.
The bbclass and recipes involved wouldn't have been packaging up the
barebox tree and pulling it into the kernel in zeus, so while it isn't
impossible, it isn't likely to be in the build or packaging changes.
Bruce
> Greetings,
> Florian
>
>
--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
next prev parent reply other threads:[~2021-06-04 13:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 9:00 Can the Linux kernel reuse the barebox device tree? #kernel florian.kauer
2021-06-04 13:03 ` Bruce Ashfield [this message]
2021-06-09 16:14 ` florian.kauer
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='CADkTA4NEZ0h7rEiSw4Q0CwLbReoSNkZAuyS=NO0LN-GPf1dKGA@mail.gmail.com' \
--to=bruce.ashfield@gmail.com \
--cc=florian.kauer@koalo.de \
--cc=yocto@lists.yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.