summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <srifenbark@gmail.com>2017-09-20 08:05:07 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2017-09-22 17:53:44 +0100
commit46d9bd00761854527748ffdcfe6896e88187bbf2 (patch)
tree877ae9fbb779ad850c0f27858d0e80f2169b9463
parent4db9f488546fda5eb287a1337bd7213005aed864 (diff)
downloadpoky-46d9bd00761854527748ffdcfe6896e88187bbf2.tar.gz
kernel-dev: Updated 4.4 to 4.12 for kernel example in layer
(From yocto-docs rev: ba8dd3676e3800b8356b7de948ceeb6e4cba4bbf) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--documentation/kernel-dev/kernel-dev-common.xml72
1 files changed, 40 insertions, 32 deletions
diff --git a/documentation/kernel-dev/kernel-dev-common.xml b/documentation/kernel-dev/kernel-dev-common.xml
index c6d1bdaac1..c4396696b8 100644
--- a/documentation/kernel-dev/kernel-dev-common.xml
+++ b/documentation/kernel-dev/kernel-dev-common.xml
@@ -563,11 +563,11 @@
563 You also name it accordingly based on the linux-yocto recipe 563 You also name it accordingly based on the linux-yocto recipe
564 you are using. 564 you are using.
565 For example, if you are modifying the 565 For example, if you are modifying the
566 <filename>meta/recipes-kernel/linux/linux-yocto_4.4.bb</filename> 566 <filename>meta/recipes-kernel/linux/linux-yocto_4.12.bb</filename>
567 recipe, the append file will typically be located as follows 567 recipe, the append file will typically be located as follows
568 within your custom layer: 568 within your custom layer:
569 <literallayout class='monospaced'> 569 <literallayout class='monospaced'>
570 <replaceable>your-layer</replaceable>/recipes-kernel/linux/linux-yocto_4.4.bbappend 570 <replaceable>your-layer</replaceable>/recipes-kernel/linux/linux-yocto_4.12.bbappend
571 </literallayout> 571 </literallayout>
572 The append file should initially extend the 572 The append file should initially extend the
573 <ulink url='&YOCTO_DOCS_REF_URL;#var-FILESPATH'><filename>FILESPATH</filename></ulink> 573 <ulink url='&YOCTO_DOCS_REF_URL;#var-FILESPATH'><filename>FILESPATH</filename></ulink>
@@ -598,7 +598,7 @@
598 As an example, consider the following append file 598 As an example, consider the following append file
599 used by the BSPs in <filename>meta-yocto-bsp</filename>: 599 used by the BSPs in <filename>meta-yocto-bsp</filename>:
600 <literallayout class='monospaced'> 600 <literallayout class='monospaced'>
601 meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend 601 meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.12.bbappend
602 </literallayout> 602 </literallayout>
603 The following listing shows the file. 603 The following listing shows the file.
604 Be aware that the actual commit ID strings in this 604 Be aware that the actual commit ID strings in this
@@ -615,11 +615,12 @@
615 KBRANCH_beaglebone = "standard/beaglebone" 615 KBRANCH_beaglebone = "standard/beaglebone"
616 KBRANCH_mpc8315e-rdb = "standard/fsl-mpc8315e-rdb" 616 KBRANCH_mpc8315e-rdb = "standard/fsl-mpc8315e-rdb"
617 617
618 SRCREV_machine_genericx86 ?= "ad8b1d659ddd2699ebf7d50ef9de8940b157bfc2" 618 SRCREV_machine_genericx86 ?= "d09f2ce584d60ecb7890550c22a80c48b83c2e19"
619 SRCREV_machine_genericx86-64 ?= "ad8b1d659ddd2699ebf7d50ef9de8940b157bfc2" 619 SRCREV_machine_genericx86-64 ?= "d09f2ce584d60ecb7890550c22a80c48b83c2e19"
620 SRCREV_machine_edgerouter ?= "cebe1ad56aebd89e0de29412e19433fb441bf13c" 620 SRCREV_machine_edgerouter ?= "b5c8cfda2dfe296410d51e131289fb09c69e1e7d"
621 SRCREV_machine_beaglebone ?= "cebe1ad56aebd89e0de29412e19433fb441bf13c" 621 SRCREV_machine_beaglebone ?= "b5c8cfda2dfe296410d51e131289fb09c69e1e7d"
622 SRCREV_machine_mpc8315e-rdb ?= "06c0dbdcba374ca7f92a53d69292d6bb7bc9b0f3" 622 SRCREV_machine_mpc8315e-rdb ?= "2d1d010240846d7bff15d1fcc0cb6eb8a22fc78a"
623
623 624
624 COMPATIBLE_MACHINE_genericx86 = "genericx86" 625 COMPATIBLE_MACHINE_genericx86 = "genericx86"
625 COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64" 626 COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
@@ -627,11 +628,11 @@
627 COMPATIBLE_MACHINE_beaglebone = "beaglebone" 628 COMPATIBLE_MACHINE_beaglebone = "beaglebone"
628 COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb" 629 COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
629 630
630 LINUX_VERSION_genericx86 = "4.4.41" 631 LINUX_VERSION_genericx86 = "4.12.7"
631 LINUX_VERSION_genericx86-64 = "4.4.41" 632 LINUX_VERSION_genericx86-64 = "4.12.7"
632 LINUX_VERSION_edgerouter = "4.4.53" 633 LINUX_VERSION_edgerouter = "4.12.10"
633 LINUX_VERSION_beaglebone = "4.4.53" 634 LINUX_VERSION_beaglebone = "4.12.10"
634 LINUX_VERSION_mpc8315e-rdb = "4.4.53" 635 LINUX_VERSION_mpc8315e-rdb = "4.12.10"
635 </literallayout> 636 </literallayout>
636 This append file contains statements used to support 637 This append file contains statements used to support
637 several BSPs that ship with the Yocto Project. 638 several BSPs that ship with the Yocto Project.
@@ -662,8 +663,8 @@
662 663
663 <para> 664 <para>
664 One thing missing in this particular BSP, which you will 665 One thing missing in this particular BSP, which you will
665 typically need when developing a BSP, is the kernel configuration 666 typically need when developing a BSP, is the kernel
666 file (<filename>.config</filename>) for your BSP. 667 configuration file (<filename>.config</filename>) for your BSP.
667 When developing a BSP, you probably have a kernel configuration 668 When developing a BSP, you probably have a kernel configuration
668 file or a set of kernel configuration files that, when taken 669 file or a set of kernel configuration files that, when taken
669 together, define the kernel configuration for your BSP. 670 together, define the kernel configuration for your BSP.
@@ -671,7 +672,8 @@
671 in a file or a set of files inside a directory located at the 672 in a file or a set of files inside a directory located at the
672 same level as your kernel's append file and having the same 673 same level as your kernel's append file and having the same
673 name as the kernel's main recipe file. 674 name as the kernel's main recipe file.
674 With all these conditions met, simply reference those files in the 675 With all these conditions met, simply reference those files in
676 the
675 <ulink url='&YOCTO_DOCS_REF_URL;#var-SRC_URI'><filename>SRC_URI</filename></ulink> 677 <ulink url='&YOCTO_DOCS_REF_URL;#var-SRC_URI'><filename>SRC_URI</filename></ulink>
676 statement in the append file. 678 statement in the append file.
677 </para> 679 </para>
@@ -717,25 +719,31 @@
717 719
718 <note> 720 <note>
719 <para> 721 <para>
720 Other methods exist to accomplish grouping and defining configuration options. 722 Other methods exist to accomplish grouping and defining
721 For example, if you are working with a local clone of the kernel repository, 723 configuration options.
722 you could checkout the kernel's <filename>meta</filename> branch, make your changes, 724 For example, if you are working with a local clone of the
723 and then push the changes to the local bare clone of the kernel. 725 kernel repository, you could checkout the kernel's
724 The result is that you directly add configuration options to the 726 <filename>meta</filename> branch, make your changes, and
725 <filename>meta</filename> branch for your BSP. 727 then push the changes to the local bare clone of the
726 The configuration options will likely end up in that location anyway if the BSP gets 728 kernel.
727 added to the Yocto Project. 729 The result is that you directly add configuration options
730 to the <filename>meta</filename> branch for your BSP.
731 The configuration options will likely end up in that
732 location anyway if the BSP gets added to the Yocto Project.
728 </para> 733 </para>
729 734
730 <para> 735 <para>
731 In general, however, the Yocto Project maintainers take care of moving the 736 In general, however, the Yocto Project maintainers take
732 <filename>SRC_URI</filename>-specified 737 care of moving the <filename>SRC_URI</filename>-specified
733 configuration options to the kernel's <filename>meta</filename> branch. 738 configuration options to the kernel's
734 Not only is it easier for BSP developers to not have to worry about putting those 739 <filename>meta</filename> branch.
735 configurations in the branch, but having the maintainers do it allows them to apply 740 Not only is it easier for BSP developers to not have to
736 'global' knowledge about the kinds of common configuration options multiple BSPs in 741 worry about putting those configurations in the branch,
737 the tree are typically using. 742 but having the maintainers do it allows them to apply
738 This allows for promotion of common configurations into common features. 743 'global' knowledge about the kinds of common configuration
744 options multiple BSPs in the tree are typically using.
745 This allows for promotion of common configurations into
746 common features.
739 </para> 747 </para>
740 </note> 748 </note>
741 </section> 749 </section>