Re: Trouble modifying defconfig for linux-ti-staging_rt recipe

[Denys Dmytriyenko <denys@ti.com>]

On Mon, Mar 20, 2017 at 04:59:30PM -0400, Glenn Schmottlach wrote:
> > So, beaglebone.conf sets up SOC_FAMILY to use "ti33x" override, hence it uses
> > defconfig in the corresponding ti33x directory. And that defconfig is just a
> > redirect to "ti_sdk_am3x_release" entry in the map file I explain below.
> >
> > That said, since you prepend to FILESEXTRAPATHS and provide your own full
> > defconfig, I expect it to take precedence and overwrite everything our recipe
> > does - so not sure what didn't work here in your case...
> >
> 
> I had hoped just adding a full defconfig to the SRC_URI in my
> *.bbappend file would've overwritten the one generated by the TI
> kernel recipe but unfortunately (at least in my situation) my custom
> defconfig got clobbered by the default one for the BBB. I dumped the
> SRC_URI (bitbake -e linux-ti-staging-rt | grep SRC_URI=) and it
> contained two defconfig's so it was not entirely clear which one was
> being applied last. The KERNEL_CONFIG_FRAGMENTS trick gets my by my
> initial issue but I hope I won't get to the point of needing my own
> custom defconfig. Wish I understood why mine didn't take . . . sort of
> bothers me given that you said it should have overwritten the default.

Yeah, SRC_URI already contains "defconfig" entry, thus no need to add it the 
second time in your bbappend. Just doing the standard FILESEXTRAPATHS_prepend 
trick in your bbappend should be enough to get it loaded in place of standard 
meta-ti config stuff.

What is your layer's BBFILE_PRIORITY? And where exactly do you add it to 
BBLAYERS list in your conf/bblayers.conf file?

-- 
Denys