Kernel configuration using bitbake menuconfig in yocto?

1
votes

I am trying to remove some drivers from the yocto kernel using menuconfig like this below..

bitbake -c menuconfig virtual/kernel

after all the configurations i generate the fragment.cfg with.

bitbake -c diffconfig virtual/kernel

Then i make a .bbappend file in recipes-kernel/linux directory and bitbake my image.

Now the problem is that all the configuration which i do is reset to the default everytime for some reason. how can i make the configuration permanent ?

1
linuxlinux-kernelyoctobitbake
When you say "reset to default everytime" what do you mean by "everytime"? everytime you bitbake? flash the image? – embedded_dev
everytime i do bitbake -C compile virtual/kernel or bitbake virtual/kernel or bitbake image.. for all the commands it do the same... – Hsn
How is your building environment set up? Are you using devtool? The image could be being built using another kernel configuration that wasn't affected by your changes. – embedded_dev
It has been a while since I last dealt with Yocto, but have you tried building the image after doing the bitbake -c menuconfig virtual/kernel without doing a diffconfig? If I remember correctly, I was successful editing the kernel only with that. – embedded_dev
When you use -C or -c -f with bitbake, you are forcing it to do something it didn't want in the first place, hence the warning. To get rid of it (and have a sane build), you need to clean the shared-state cache (-c cleansstate) of the incriminated recipe (virtual/kernel in your case). – qschulz

1 Answers

1
votes

One solution is to create own receipt and override default.
For example, we are using linux-yocto-rt kernel and create own receipt with name linux-yocto-rt and following files:

linux-yocto-rt\linux-yocto-rt_4.9.bb
linux-yocto-rt\linux-yocto-rt\defconfig

defconfig file changes default configuration.
In bb file you should add link to this file like:

SRC_URI += "file://defconfig "

You can always look inside official documentation