Re: Raspberrypi3 - Kernel configurations

[Jan-Simon Möller <jsmoeller@xxxxxxxxxxxxxxxxxxx>]

Hi Chris,

please find my comments inline ...


Am Samstag, 10. November 2018, 10:54:57 CET schrieb Chris Chros:
> Hello,
>  
> 
> where can I make kernel configurations for the Raspberrypi with version ff?
> In the EEL version, I defined the kernel configurations in
> "meta-raspbarrypi/recipes-kernel/linux/linux-raspbarrypi_4.9.bb" by adding
> the following line: "SRC_URI_append = " file://kernelconfig". I copied the
> kernelconfig file to the
> folder meta-raspbarrypi/recipes-kernel/linux/linux-raspbarrypi. 

First of all: this is the wrong place to modify. Yocto offers you the means to
amend existing recipes so you don't need to hack the original recipes and thus can keep it unchanged so it survives updates as well.

> However, I updated AGL to version FF and now the folder linux-raspbarrypi is
> no longer available. There is just a
> folder "linux-raspberrypi-dev" in meta-raspberrypi/recipes-kernel/Linux and
> the file "linux-raspberrypi-dev.bb".  I have tried to add the Kernel
> configurations there and after that I checked the /proc/config.gz File and
> the defined configuration isnt available. 
> So Where can i put my configurations?

Again, upstream changes are expected through uprev's . So another reason not the modify the recipes in place.

Now where should things be added:
AGL has 2 mechanisms for this:
a) if we want to apply a config option to all kernels in use by AGL, there is:
meta-agl/meta-agl-bsp/recipes-kernel/linux/linux-agl.inc 
You add a fragment (.cfg) file with your added options and add it to this include file.
b) if you want it only for a particular board, then you use
meta-agl/meta-agl-bsp/meta-<layername>/recipes-kernel/linux/linux-<XYZ>_%.bbappend
e.g.
meta-agl/meta-agl-bsp/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_%.bbappend
with the .cfg fragment in a subfolder as well.

These methods are the safe ways to do this if being uploaded to AGL.

########################## USE THIS ############################
However, for local development, you'd use the agl-localdev feature and follow:

a) source meta-agl/scripts/aglsetup.sh -b build-rpi3 -m raspberrypi3 agl-demo agl-devel agl-localdev
b) bitbake-layers create-layer ../meta-localdev/
c) mkdir -p ../meta-localdev/recipes-kernel/linux/files
d) create the fragment ../meta-localdev/recipes-kernel/linux/files/myconffragment.cfg
e) create the bbappend ../meta-localdev/recipes-kernel/linux/linux-raspberrypi_%.bbappend
content might look like:

FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
SRC_URI_append = " file://myconffragment.cfg"
KERNEL_CONFIG_FRAGMENTS_append = " ${WORKDIR}/myconffragment.cfg"
########################## USE THIS ############################

The effect of all of these variants is the same. 
The original recipe is amended with the options specified in the bbappend without
us modifying the original git tree which can then be updated w/o issue.

HTH,
Jan-Simon Möller
> 
> 
> Thanks,
> 
> Chris_Chros
> _______________________________________________
> automotive-discussions mailing list
> automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx
> https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions


_______________________________________________
automotive-discussions mailing list
automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions