From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
To: yocto@lists.yoctoproject.org, skandigraun@gmail.com,
david.daniel@vrag.ch
Cc: michael.opdenacker@rootcommit.com
Subject: Re: [yocto] kernel append file with dts in SRC_URI and subdir
Date: Mon, 27 Jan 2025 14:48:07 +0000 (UTC) [thread overview]
Message-ID: <7e0a1c17-1615-4fc1-937f-897a8329a8f6@rootcommit.com> (raw)
In-Reply-To: <4dff1359-2be1-4ad7-b7f0-22e9f968edd2@gmail.com>
Hi Dave,
On 1/27/25 15:10, Gyorgy Sarvari via lists.yoctoproject.org wrote:
> Depending on the order of unpacking, it is possible that your dts file
> overwritten by the actual kernel source.
>
> Try adding it as a patch?
I agree. As far as I have seen, it's more frequent to use a patch to add
files to the sources.
>
> On 27.01.25 12:12, 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 \
>> "
I guess you're using "name=" for checksums, right?
Did you check that ARCH is defined here? You may try to hardcore its
value here.
Cheers
Michael.
--
Michael Opdenacker
Root Commit
Yocto Project and OpenEmbedded Training course - Learn by doing:
https://rootcommit.com/training/yocto/
next prev parent reply other threads:[~2025-01-27 14:48 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 [this message]
2025-01-27 15:02 ` Quentin Schulz
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=7e0a1c17-1615-4fc1-937f-897a8329a8f6@rootcommit.com \
--to=michael.opdenacker@rootcommit.com \
--cc=david.daniel@vrag.ch \
--cc=skandigraun@gmail.com \
--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.