[yocto] Compiling custom kernel

Bruce Ashfield bruce.ashfield at windriver.com
Wed Mar 29 11:23:32 PDT 2017


On 2017-03-29 1:11 PM, Alvaro Garcia wrote:
> Hi, I'm trying to compile a custom kernel (just custom config).
> I created a recipe called linux-yocto in my layer:
> meta-test
> -recipes-test
> --linux-yocto
> ---linux-yocto.bbapend
> ---files
> ----enable_various_options.cfg
>
> The content of the linux-yocto.bbapend is:
>
> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
> SRC_URI += "file://enable_various_options.cfg"
>
> And the content of enable_various_options.cfg is:
> CONFIG_DRM_NOUVEAU=y

Assuming that you do have your bbappend created properly
(i.e. with the version number suggestion that was sent) a
configuration option cannot always be blanket enabled. If there
are missing dependencies for that option, it won't make it into
the final .config.

So it is worth checking that all dependencies are also included
in that same .cfg.

Bruce

>
> The way I generated enable_various_options.cfg was
> bitbake -c menuconfig virtual/kernel
> Select my configuration
> bitbake -c devshell virtual/kernel
> diff of the original .config and the new one.
> I just followed the instructions here
> https://lists.yoctoproject.org/pipermail/yocto/2014-June/020174.html
> and here
> https://software.intel.com/sites/default/files/m/4/d/8/5/8/42868-11__Developing_Kernel_Module_on_Yocto.pdf
>
> Then I run bitbake core-image-x11
> I got this warning:
> WARNING:
> /home/amacho/poky/meta/recipes-kernel/linux/linux-yocto_4.4.bb.do_kernel_configme
> is tainted from a forced run
> but the kernel is not compiled with the new config (I do md5 to vmlinuz
> and was exactly the same).
>
> Can you help me to find the way I can compile this kernel?
>
> Thank you
>
>
>
>




More information about the yocto mailing list