All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gyorgy Sarvari <skandigraun@gmail.com>
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 15:39:42 +0100	[thread overview]
Message-ID: <79a79a8a-7494-45d1-9333-22c18deeb2c3@gmail.com> (raw)
In-Reply-To: <a1657de15b95836d7694155634388de223edae86.camel@vrag.ch>

For git fetcher, if the unpack directory already exists at the time of 
unpacking, then it first gets deleted recursively: 
https://git.yoctoproject.org/poky/tree/bitbake/lib/bb/fetch2/git.py#n660 
- it doesn't check if the content conflicts or not :)

On 27.01.25 15:33, David Daniel via lists.yoctoproject.org wrote:
> Ah I see. That's weird though, as the name is unique, it shouldn't
> collide with any existing file. But adding as a patch sounds
> reasonable. I'll try this instead and see.
> Thanks!
>
> Am Montag, dem 27.01.2025 um 15:10 +0100 schrieb Gyorgy Sarvari:
>> 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?
>>
>> 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
>>>   \
>>>       "
>>>
>>>       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
>>> does get placed within the sources-unpack folder though. Within the
>>> sources-unpack folder there is no dts file though and the dts file
>>> is
>>> as well not placed within the dts folder of the kernel build or
>>> source
>>> folder.
>>>
>>> Is it possible to modify a kernel somewhat like this? What am I
>>> doing
>>> wrong?
>>>
>>> Thanks for any hints!
>>> Dave
>>>
>>>
>>>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#64639): https://lists.yoctoproject.org/g/yocto/message/64639
> Mute This Topic: https://lists.yoctoproject.org/mt/110836825/6084445
> Group Owner: yocto+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [skandigraun@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>


  reply	other threads:[~2025-01-27 14:39 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 [this message]
2025-01-27 14:54       ` David Daniel
2025-01-27 14:48   ` Michael Opdenacker
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=79a79a8a-7494-45d1-9333-22c18deeb2c3@gmail.com \
    --to=skandigraun@gmail.com \
    --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.