Hi Bruce, Thanks for your response.
> You can't suppress the kernel's config step, it is always going to > run. You can't just copy over .config and have the kernel build. If the OE build kernel config step can be disabled to compile kernel using customer defconfig, that will make users life much easier to disable unwanted kernel drivers and features. The customer defconfig can be certainly generated from bitbake -c menuconfig, but honestly, the kernel configure selection is not easier to understand, we have to use defconfig to disable unwanted the configures and tested it, inadvertently disable some configures could cause kernel panic regardless if the OE build system config step is running or not. I have searched the internet, it is not just me, there are many others who requested to run customer defconfig without OE build kernel config step. Are you a contributor in the OE dev team? Are there any reasons why the OE dev team won't consider this feature? Thank you very much. Kind regards, jupiter
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#96838): https://lists.openembedded.org/g/openembedded-devel/message/96838 Mute This Topic: https://lists.openembedded.org/mt/90749427/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
