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

[Denys Dmytriyenko <denys@ti.com>]

On Tue, Mar 21, 2017 at 07:52:41AM -0400, Glenn Schmottlach wrote:
> >> 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?
> >
> 
> I set my BBFILE_PRIORITY to "8" which is higher than meta-ti ("6") so
> I would've thought it takes precedence over meta-ti recipes. My layer
> is referenced in bblayers.conf and the layer's "conf/layer.conf" looks
> like this:
> 
> =====================================================
> 
> # We have a conf and classes directory, append to BBPATH
> BBPATH .= ":${LAYERDIR}"
> 
> # We have a recipes directory, add to BBFILES
> BBFILES += "${LAYERDIR}/recipes*/*/*.bb
> ${LAYERDIR}/recipes*/*/*.bbappend ${LAYERDIR}/images/*.bb"
> 
> BBFILE_COLLECTIONS += "meta-acme"
> BBFILE_PATTERN_meta-acme := "^${LAYERDIR}/"
> BBFILE_PRIORITY_meta-acme = "8"
> 
> =======================================================
> 
> Pretty standard stuff. It's definitely finding my recipes so I don't
> think that's an issue. What do you suspect might be going on?

Looks good... Can you try moving your defconfig into "ti33x" folder?

recipes-kernel/linux/linux-ti-staging-rt_%.bbappend
recipes-kernel/linux/linux-ti-staging-rt/ti33x/defconfig

-- 
Denys