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

[Denys Dmytriyenko]

On Mon, Mar 20, 2017 at 11:44:16AM -0400, Glenn Schmottlach wrote:
> I am having trouble modifying the kernel configuration for the
> following TI kernel recipe using the Yocto Morty environment:
> 
> linux-ti-staging-rt_4.9.bb
> 
> I have created my own layer and with a *.bbappend file for this recipe, e.g.
> 
> linux-ti-staging-rt_4.9.bbappend
> 
> It appears the TI kernel recipes are not (yet) proper "Yocto" kernel
> recipes in that they are not "fragment" aware.

TI kernel recipe is not "Yocto" kernel (which is really to say WindRiver 
format), but the fragment support got upstreamed to the mainline kernel and 
kernel itself now supports config fragments! That is what TI kernel uses and 
meta-ti kernel recipe supports.


> It appears I cannot do
> the following inside of my *.bbappend recipe:
> 
> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
> SRC_URI += "file://eem.cfg"

You can add any additional fragments you want to be applied by the recipe to 
KERNEL_CONFIG_FRAGMENTS variable.


> Inside of "eem.cfg" I want to set the following kernel options:
> 
> CONFIG_USB_NET_CDC_EEM=m
> CONFIG_USB_F_EEM=m
> CONFIG_USB_ETH_EEM=y
> 
> This has no affect. I tried creating my own defconfig based on the
> '.config' generated from the original recipe. I modified my *.bbappend
> file as follows:
> 
> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
> SRC_URI += "file://defconfig"
> 
> Again, my defconfig is not applied to the build.

It already has file://defconfig in SRC_URI, that's how it works and gets the 
fragments assembled.

What's your platform? Are you sure one of the existing defconfigs are not 
used instead?


> I even tried patching kernel-source/ti_config_fragments and placing a
> eem.cfg in that directory hoping the configuration generation script
> (defconfig_builder.sh) might apply this fragment.
> 
> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
> SRC_URI += "file://0001-eem-config.patch"
> 
> Where the patch contains:
> 
> Index: kernel-source/ti_config_fragments/eem.cfg
> ===================================================================
> --- /dev/null
> +++ kernel-source/ti_config_fragments/eem.cfg
> @@ -0,0 +1,4 @@
> +CONFIG_USB_NET_CDC_EEM=m
> +CONFIG_USB_F_EEM=m
> +CONFIG_USB_ETH_EEM=y
> +
> 
> Unfortunately this did not work either.

You also need to update the "map" file, which basically lists all the 
fragments it needs to assemble for a platform. And platform's defconfig only 
points to one of the entries in the map file.


> I suspect this question has been asked before, but what is the
> RECOMMENDED procedure for making kernel configuration changes to the
> TI kernel recipes in a Yocto environment? What methods have others
> used to tweak the TI kernel options from their *.bbappend files?
> 
> Thanks for any insights . . .
> -- 
> _______________________________________________
> meta-ti mailing list
> meta-ti at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti