From: Mike Crowe <mac@mcrowe.com>
To: OE-core <openembedded-core@lists.openembedded.org>
Subject: Using kernel device tree when compiling U-Boot
Date: Mon, 25 Nov 2019 15:34:10 +0000 [thread overview]
Message-ID: <20191125153410.GA31863@mcrowe.com> (raw)
I'd like to use a single set of device tree sources for both the kernel and
U-Boot. I'd like to take the dtb files generated when compiling the kernel
and use it for U-Boot. This means that I need to able to find them from the
U-Boot recipe - ideally without having a list of them there.
So, I thought that I'd teach my kernel recipe to install the device trees
in the sysroot. I ought to be able to do this by adding
SYSROOT_DIRS +="/boot"
to my kernel recipe. Unfortunately, kernel.bbclass contains:
# We don't need to stage anything, not the modules/firmware since those would clash with linux-firmware
sysroot_stage_all () {
:
}
which stops this being effective. This code predates
80e7e7f78d957b8159bede2a5cd5614d8d73039c. Would it now be more appropriate
to influence staging.bbclass's behaviour by setting SYSROOT_DIRS_BLACKLIST
to fix the mentioned clashes? Perhaps the invention of recipe-specific
sysroots might mean that these clashes no longer occur?
The device tree dtb files are published to the deploy directory. I could
try to grab them from there, but even apart from having to deal with the
symlinks, it doesn't feel quite right to do so.
Or perhaps I've missed a much simpler way to solve this problem.
Thanks.
Mike.
reply other threads:[~2019-11-25 15:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20191125153410.GA31863@mcrowe.com \
--to=mac@mcrowe.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox