[meta-ti] Trouble modifying defconfig for linux-ti-staging_rt recipe

[Glenn Schmottlach]

> 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.

Thanks again,

Glenn