From: Quentin Schulz <quentin.schulz@cherry.de>
To: yocto@lists.yoctoproject.org, david.daniel@vrag.ch
Subject: Re: [yocto] kernel append file with dts in SRC_URI and subdir
Date: Mon, 27 Jan 2025 16:02:45 +0100 [thread overview]
Message-ID: <b9caa6eb-7244-4872-988e-c90f21fb5675@cherry.de> (raw)
In-Reply-To: <6761dc4a56d319b617e61e18fb37df8e6c5e227b.camel@vrag.ch>
Hi David,
On 1/27/25 12:12 PM, David Daniel via lists.yoctoproject.org wrote:
> Hi
>
> I am trying to figure out why the following snippet of a kernel
> .bbappend file does not populate the custom device tree source file in
> the proper location:
>
>
> FILESEXTRAPATHS:prepend := "${THISDIR}/files:"
> SRC_URI += "\
> file://defconfig;name=config \
> file://cf200.dts;name=dts;subdir=git/arch/${ARCH}/boot/dts/freescale \
> "
>
You should consider putting this dts in a separate recipe, see
https://docs.yoctoproject.org/ref-manual/classes.html#devicetree for how
to do it.
> COMPATIBLE_MACHINE = "(cf200)"
>
> It also seems the configuration is not applied. If I rename the
> defconfig file to doesntexist the build fails early. The defconfig file
It depends on what the kernel recipe is doing with that defconfig. Could
also be trying to apply fragments afterwards for example. Without having
a look at the recipe, it'll be difficult to tell. You haven't said to
which recipe this bbappend is supposed to apply though and there are
many ways and many kernel recipes around :)
Cheers,
Quentin
next prev parent reply other threads:[~2025-01-27 15:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-27 11:12 kernel append file with dts in SRC_URI and subdir David Daniel
2025-01-27 14:10 ` [yocto] " Gyorgy Sarvari
2025-01-27 14:33 ` David Daniel
2025-01-27 14:39 ` Gyorgy Sarvari
2025-01-27 14:54 ` David Daniel
2025-01-27 14:48 ` Michael Opdenacker
2025-01-27 15:02 ` Quentin Schulz [this message]
2025-01-27 16:04 ` David Daniel
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=b9caa6eb-7244-4872-988e-c90f21fb5675@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=david.daniel@vrag.ch \
--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.