kernel configuration fragments

-
bitbake linux-yocto-custom -c menuconfig 
 
make whatever adjustments here
 
bitbake linux-yocto-custom -c diffconfig
 
this spits out a configuration fragment
 
add it to your kernel configuration fragments
 
make sure it made it into your kernel configuration:
 
bitbake linux-yocto-custom -c cleansstate

bitbake linux-yocto-custom -c menuconfig
 
Now you should find your new configuration settings in menuconfig 




 


































Comments











Post a Comment



















Popular posts from this blog









Yocto: BitBake and Dependencies - e.g. One recipe to use output of another recipe






-














Image







It feels weird to help some get their working  build to fail and then for them to be happy  about it... (RP)     Introduction    This work is sponsored by Reliable  Embedded  Systems . You can find more information about our training/consulting services here .   Objectives The  goal of this blog post is to look into BitBake dependencies. As an example let's take recipe A ( u-boot-phytex-imx ) which needs the output of recipe B ( firmware-imx-8m ) for a successful compilation. (Please don't ask why.) To be more precise here is an excerpt of recipe A ( u-boot-phytex-imx ):   # --> this funny u-boot from Phytec needs the ddr_firmware binaries in ${S}  # Note: here we copy deployed stuff from another recipe  #       to the source dir of this recipe!  #  # DEPENDS deals with build-time depenencies  # Read my blog post to find out why DEPENDS does not work here  #  # DEPENDS += " \  #           firmware-imx-8m \  #           "  # RDEPENDS is wrong anyhow for what I want 








Read more










Yocto: kernel modules not showing up in the rootfs






-














Image







Introduction     This work is sponsored by Reliable  Embedded  Systems . You can find more information about our training/consulting services here .   Objectives The  goal of this blog post is to point out a well known and documented issue with kernel modules not ending up on the root file system which is likely overseen by people until they stumble over it.   Kernel module(s) So you created a brand new kernel module, or you just wanted to include all the kernel modules in the root file system, or just one of them. You reach out to the community mailing list or chat with something like this:     I have MACHINE_EXTRA_RRECOMMENDS + =  "kernel-modules"  in my machine configuration.  When I look into the rootfs I see no modules installed in /lib/modules/ $( uname -r ) .  I get only a modules tarball in the deploy directory. I also tried  MACHINE_EXTRA_RDEPENDS + =  "kernel-modules"  and it still does not work. What am I doing wrong?     Check the Mega Manual If things d








Read more










Yocto/Qt5: hello-qt part2 - Licensing 






-














Image







Introduction     This work is sponsored by Reliable  Embedded  Systems . You can find more information about our training/consulting services here .   Objectives The  goal of this blog post is to show my journey trying to build a hello-qt  application and reasons why I don't like Qt . As far as I can tell this is going to be a multi part blog post. You might want to have a look at part one  as well. Disclaimer: I am not a lawyer, so I can not give legal advice.  GPL and LGPL licenses LGPL v2.x Typically libraries are licensed with this license You need to provide the source code (including modifications) and instructions on how to build the LGPL v2.1 licensed code In case your application links statically against LGPL licensed code you need to provide the object files of your applications to be able to replace the LGPL'ed code with different versions In case your application links dynamically against LGPL licensed code you can replace the LGPL'ed libraries without the objec








Read more