Skip to contentSkip to conversation

potentially confusing explanation of "defconfig" in kernel dev manual

DISCUSSION Robert P. J. Day 2 participants 2 messages Apr 13, 2013 – Apr 14, 2013

lore
Share & tools
lore
#0 lore raw

here:

http://www.yoctoproject.org/docs/latest/kernel-dev/kernel-dev.html#changing-the-configuration

one reads:

"If you have a complete Linux kernel .config file you want to use, copy it to the ${FILES} directory within your layer and name it "defconfig"."

that pretty clearly suggests that the "defconfig" file *must*
represent a *complete* .config file. but just above that, you read:

"You can make wholesale or incremental changes to the Linux kernel .config file by including a defconfig or by specifying configuration fragments in the SRC_URI."

so it's confusing -- must defconfig represent a complete .config
file, or can it represent a fragment?

rday

Signature · 7 lines
========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================
#1 lore raw

That's how I interpret it:

Wholesale = defconfig
Incremental = configuration fragments

Following kernel practices my defconfig files always have a working configuration and then I use configuration fragments to make adjustments.

But of course you can have an incomplete configuration in defconfig and make it complete with configuration fragments.

:rjs

Quoted 38 lines · Robert P. J. Day

here:

http://www.yoctoproject.org/docs/latest/kernel-dev/kernel-dev.html#changing-the-configuration

one reads:

"If you have a complete Linux kernel .config file you want to use, copy it to the ${FILES} directory within your layer and name it "defconfig"."

that pretty clearly suggests that the "defconfig" file *must*
represent a *complete* .config file. but just above that, you read:

"You can make wholesale or incremental changes to the Linux kernel .config file by including a defconfig or by specifying configuration fragments in the SRC_URI."

so it's confusing -- must defconfig represent a complete .config
file, or can it represent a fragment?

rday

--

========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday

========================================================================
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto