sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

kernel-dev: Small fixes. 

Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 198ce97a1158237056f035ade555ce04a6031c56)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2015-02-25 08:46:19 -08:00 committed by Richard Purdie
parent 1a74c797a0
commit 4bdaa5c5ba
1 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
documentation/kernel-dev/kernel-dev-common.xml
View File

@ -133,16 +133,16 @@
<para> <para>
For example, you can apply a three-patch series by adding the For example, you can apply a three-patch series by adding the
following lines to your linux-yocto <filename>.bbappend</filename> following lines to your linux-yocto
file in your layer: <filename>.bbappend</filename> file in your layer:
<literallayout class='monospaced'> <literallayout class='monospaced'>
SRC_URI += "file://0001-first-change.patch" SRC_URI += "file://0001-first-change.patch"
SRC_URI += "file://0002-first-change.patch" SRC_URI += "file://0002-second-change.patch"
SRC_URI += "file://0003-first-change.patch" SRC_URI += "file://0003-third-change.patch"
</literallayout> </literallayout>
The next time you run BitBake to build the Linux kernel, BitBake The next time you run BitBake to build the Linux kernel,
detects the change in the recipe and fetches and applies the patches BitBake detects the change in the recipe and fetches and
before building the kernel. applies the patches before building the kernel.
</para> </para>
<para> <para>
@ -187,14 +187,14 @@
<note> <note>
The build system applies the configurations from the The build system applies the configurations from the
<filename>.config</filename> file before applying any <filename>defconfig</filename> file before applying any
subsequent configuration fragments. subsequent configuration fragments.
The final kernel configuration is a combination of the The final kernel configuration is a combination of the
configurations in the <filename>.config</filename> file and configurations in the <filename>defconfig</filename> file and
any configuration fragments you provide. any configuration fragments you provide.
You need to realize that if you have any configuration You need to realize that if you have any configuration
fragments, the build system applies these on top of and fragments, the build system applies these on top of and
after applying the existing <filename>.config</filename> after applying the existing <filename>defconfig</filename>
file configurations. file configurations.
</note> </note>
@ -399,7 +399,7 @@
WARNING: There were 2 hardware options requested that do not WARNING: There were 2 hardware options requested that do not
have a corresponding value present in the final ".config" file. have a corresponding value present in the final ".config" file.
This probably means you are not't getting the config you wanted. This probably means you are not getting the config you wanted.
The full list can be found in your kernel src dir at: The full list can be found in your kernel src dir at:
meta/cfg/standard/mybsp/mismatch.cfg meta/cfg/standard/mybsp/mismatch.cfg
</literallayout> </literallayout>