Re: [yocto] kernel append file with dts in SRC_URI and subdir

[David Daniel <david.daniel@vrag.ch>]

You're right, sorry, I thought it wouldn't matter much but I intended
to append to an imx kernel (linux-imx from freescale). And yes, I have
finally taken the route of a separate kernel recipe - it makes
everything easier in the end as I can now simply include the source dts
file and don't have to create a patch for it.
And you're right of course, it seems the defconfig was ignored and
instead another predefined default got caught (one I didn't override
correctly I guess).
Thanks for all this great help! Really amazing ❤️

Am Montag, dem 27.01.2025 um 16:02 +0100 schrieb Quentin Schulz:
> 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