summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--documentation/kernel-dev/kernel-dev-common.xml44
1 files changed, 25 insertions, 19 deletions
diff --git a/documentation/kernel-dev/kernel-dev-common.xml b/documentation/kernel-dev/kernel-dev-common.xml
index 31a7743c17..0b31de0c60 100644
--- a/documentation/kernel-dev/kernel-dev-common.xml
+++ b/documentation/kernel-dev/kernel-dev-common.xml
@@ -276,8 +276,8 @@ apply the new configuration before rebuilding the Linux kernel.
276 you can iteratively generate them from within the BitBake build 276 you can iteratively generate them from within the BitBake build
277 environment as described within this section. 277 environment as described within this section.
278 During an iterative workflow, running a previously completed BitBake 278 During an iterative workflow, running a previously completed BitBake
279 task causes BitBake to invalidate the tasks that follow that 279 task causes BitBake to invalidate the tasks that follow the
280 task in the build sequence. 280 completed task in the build sequence.
281 Invalidated tasks rebuild the next time you run the build using 281 Invalidated tasks rebuild the next time you run the build using
282 BitBake. 282 BitBake.
283 </para> 283 </para>
@@ -386,8 +386,8 @@ working with.
386 requested configuration does not appear in the final 386 requested configuration does not appear in the final
387 <filename>.config</filename> file or when you override a 387 <filename>.config</filename> file or when you override a
388 policy configuration in a hardware configuration fragment. 388 policy configuration in a hardware configuration fragment.
389 Following is the command that runs these tools and some 389 Here is an example with some sample output of the command
390 sample output: 390 that runs these tools:
391 <literallayout class='monospaced'> 391 <literallayout class='monospaced'>
392 $ bitbake linux-yocto -c kernel_configcheck -f 392 $ bitbake linux-yocto -c kernel_configcheck -f
393 393
@@ -531,7 +531,7 @@ adjust your configuration files and repeat the "kernel_configme" and
531 the <filename>compile</filename>. 531 the <filename>compile</filename>.
532 Once compilation is successful, you can inspect and test 532 Once compilation is successful, you can inspect and test
533 the resulting build (i.e. kernel, modules, and so forth) from 533 the resulting build (i.e. kernel, modules, and so forth) from
534 the build directory: 534 the <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>:
535 <literallayout class='monospaced'> 535 <literallayout class='monospaced'>
536 ${WORKDIR}/linux-${MACHINE}-${KTYPE}-build 536 ${WORKDIR}/linux-${MACHINE}-${KTYPE}-build
537 </literallayout> 537 </literallayout>
@@ -622,21 +622,26 @@ to the Yocto Project Development Manual, section 5.7.3 Creating the Patch.
622 <title>Working With Your Own Sources</title> 622 <title>Working With Your Own Sources</title>
623 623
624 <para> 624 <para>
625 If you find yourself unable to work with one of the Linux kernel 625 If you cannot work with one of the Linux kernel
626 versions supported by existing linux-yocto recipes, you can 626 versions supported by existing linux-yocto recipes, you can
627 still make use of the Yocto Project Linux kernel tooling by 627 still make use of the Yocto Project Linux kernel tooling by
628 working with your own sources. 628 working with your own sources.
629 You will not be able to leverage the existing 629 When you use your own sources, you will not be able to
630 leverage the existing
630 <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink> and 631 <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink> and
631 stabilization work of the linux-yocto sources, but you will be 632 stabilization work of the linux-yocto sources.
632 able to manage your own Metadata in the same format as the 633 However, you will be able to manage your own Metadata in the same
633 linux-yocto sources. 634 format as the linux-yocto sources.
634 Format compatibility facilitates converging with 635 Maintaining format compatibility facilitates converging with
635 linux-yocto on a future, mutually-supported kernel version. 636 linux-yocto on a future, mutually-supported kernel version.
636 </para> 637 </para>
637 638
638 <para> 639 <para>
639 The linux-yocto custom recipe is located in the 640 To help you use your own sources, the Yocto Project provides a
641 linux-yocto custom recipe that uses
642 <filename>kernel.org</filename> sources
643 and the Yocto Project Linux kernel tools for managing Metadata.
644 You can find this recipe in the
640 <filename>poky</filename> Git repository of the 645 <filename>poky</filename> Git repository of the
641 Yocto Project <ulink url='&YOCTO_GIT_URL;'>Source Repository</ulink> 646 Yocto Project <ulink url='&YOCTO_GIT_URL;'>Source Repository</ulink>
642 at: 647 at:
@@ -646,11 +651,6 @@ to the Yocto Project Development Manual, section 5.7.3 Creating the Patch.
646 </para> 651 </para>
647 652
648 <para> 653 <para>
649 The example recipe uses <filename>kernel.org</filename> sources
650 and the Yocto Project Linux kernel tools for managing Metadata.
651 </para>
652
653 <para>
654 Here are some basic steps you can use to work with your own sources: 654 Here are some basic steps you can use to work with your own sources:
655 <orderedlist> 655 <orderedlist>
656 <listitem><para>Copy the <filename>linux-yocto-custom.bb</filename> 656 <listitem><para>Copy the <filename>linux-yocto-custom.bb</filename>
@@ -713,8 +713,14 @@ to the Yocto Project Development Manual, section 5.7.3 Creating the Patch.
713 only the empty string, "(^$)". 713 only the empty string, "(^$)".
714 This default setting triggers an explicit build failure. 714 This default setting triggers an explicit build failure.
715 You must change it to match a list of the machines 715 You must change it to match a list of the machines
716 that your new recipe supports (e.g. "qemux86|qemux86-64"). 716 that your new recipe supports.
717 </para></listitem> 717 For example, to support the <filename>qemux86</filename>
718 and <filename>qemux86-64</filename> machines, use
719 the following form with your layer name as the
720 override:
721 <literallayout class='monospaced'>
722 COMPATIBLE_MACHINE_yourmachine = "qemux86|qemux86-64"
723 </literallayout></para></listitem>
718 </itemizedlist></para></listitem> 724 </itemizedlist></para></listitem>
719 <listitem><para>Provide further customizations to your recipe 725 <listitem><para>Provide further customizations to your recipe
720 as needed just as you would customize an existing 726 as needed just as you would customize an existing