[yocto] supplying your own "defconfig" in a kernel recipe

[Robert P. J. Day]

  a bit of inconsistent wording between the kernel hands-on lab1 and
the kernel dev manual (unless i'm misreading).

  in lab1, we read:

"This is a bare-bones simple Linux kernel recipe. It inherits all of
the logic for configuring and building the kernel from the
kernel.bbclass (the 'inherit kernel' line). It specifies the Linux
kernel sources in SRC_URI as a recent tarball release from kernel.org.
It also specifies a defconfig, this file is used as the .config to
build the kernel. It is empty for now, so the Linux kernel
configuration system will use defaults."

  suggesting an empty defconfig will force the config step to use
defaults. but the kernel dev manual states:

"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". Then, add the following line to your linux-yocto
.bbappend file in your layer:

     SRC_URI += "file://defconfig"

which suggests to the reader that a user-supplied defconfig file
should represent *only* a "complete" .config file.

  the kernel.bbclass itself seems to suggest that your defconfig file
can represent any part of the configuration you want to override the
default.

  does anyone else see the apparent inconsistency that might trip up a
reader?

rday

-- 

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

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