All of lore.kernel.org
 help / color / mirror / Atom feed
From: florian.kauer@koalo.de
To: yocto@lists.yoctoproject.org
Subject: Can the Linux kernel reuse the barebox device tree? #kernel
Date: Fri, 04 Jun 2021 02:00:17 -0700	[thread overview]
Message-ID: <td3c.1622797217734922140.8fqZ@lists.yoctoproject.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1090 bytes --]

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?

Greetings,
Florian

[-- Attachment #2: Type: text/html, Size: 1118 bytes --]

             reply	other threads:[~2021-06-04  9:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-04  9:00 florian.kauer [this message]
2021-06-04 13:03 ` [yocto] Can the Linux kernel reuse the barebox device tree? #kernel Bruce Ashfield
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=td3c.1622797217734922140.8fqZ@lists.yoctoproject.org \
    --to=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.