On 2016-06-12 9:40 PM, Kunihiko Hayashi wrote:
Hello, all
Now I'm trying to build my own kernel with linux-yocto recipe,
and I make kernel configuration fragments (".cfg" file) according to
"Linux Kernel Development Manual", and my fragments can't be applied
to the kernel at all.
I find that linux-yocto recipe uses "allnoconfig" as default, and
configurations that my fragments depend on are disabled.
Your fragments really should be specifying not only their options,
but the dependencies as well, or you need to have them
include other fragments that set those dependencies.
If you don't, you are relying on the baseline configuration .. which
is either a defconfig or ktype fragments in linux-yocto. That is also
ok, just something to be aware of.
KCONFIG_MODE = "--allnoconfig"
I assume that KCONFIG_MODE has the option of "configme" script,
but this option is undocumented on any manuals.
If I apply "defconfig" and my additional fragments as it is,
how do I set KCONFIG_MODE in my recipe? (null string or another option?)
KCONFIG_MODE is a variable like any other. In your kernel recipe,
you can just set it to one of the valid options.
KCONFIG_MODE = "..."
Note: those valid options are only [--alldefconfig] [--allnoconfig],
since that is what the kernel merge_config.sh script can process.
Cheers,
Bruce
Regards,
---
Kunihiko Hayashi
:hayashi.kunih...@socionext.com
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
