diff options
author | takeshi_hoshina <takeshi_hoshina@mail.toyota.co.jp> | 2020-11-02 11:07:33 +0900 |
---|---|---|
committer | takeshi_hoshina <takeshi_hoshina@mail.toyota.co.jp> | 2020-11-02 11:07:33 +0900 |
commit | 1c7d6584a7811b7785ae5c1e378f14b5ba0971cf (patch) | |
tree | cd70a267a5ef105ba32f200aa088e281fbd85747 /external/poky/documentation/kernel-dev/kernel-dev-common.xml | |
parent | 4204309872da5cb401cbb2729d9e2d4869a87f42 (diff) |
basesystem-jjsandbox/ToshikazuOhiwa/master-jj
recipes
Diffstat (limited to 'external/poky/documentation/kernel-dev/kernel-dev-common.xml')
-rw-r--r-- | external/poky/documentation/kernel-dev/kernel-dev-common.xml | 84 |
1 files changed, 52 insertions, 32 deletions
diff --git a/external/poky/documentation/kernel-dev/kernel-dev-common.xml b/external/poky/documentation/kernel-dev/kernel-dev-common.xml index 90528761..c1c2d6d7 100644 --- a/external/poky/documentation/kernel-dev/kernel-dev-common.xml +++ b/external/poky/documentation/kernel-dev/kernel-dev-common.xml @@ -89,8 +89,8 @@ <emphasis>Prepare Your <filename>local.conf</filename> File:</emphasis> By default, the <ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE'><filename>MACHINE</filename></ulink> - variable is set to "qemux86", which is fine if you are - building for the QEMU emulator in 32-bit mode. + variable is set to "qemux86-64", which is fine if you are + building for the QEMU emulator in 64-bit mode. However, if you are not, you need to set the <filename>MACHINE</filename> variable appropriately in your <filename>conf/local.conf</filename> file found in @@ -104,10 +104,12 @@ <ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS'><filename>MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS</filename></ulink> variable to include kernel modules.</para> - <para>This example uses the default "qemux86" for the - <filename>MACHINE</filename> variable but needs to - add the "kernel-modules": + <para>In this example we wish to build for qemux86 so + we must set the <filename>MACHINE</filename> variable + to "qemux86" and also add the "kernel-modules". As described + we do this by appending to <filename>conf/local.conf</filename>: <literallayout class='monospaced'> + MACHINE = "qemux86" MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS += "kernel-modules" </literallayout> </para></listitem> @@ -185,7 +187,7 @@ Poky (Yocto Project Reference Distro) Extensible SDK installer version &DISTRO; ============================================================================ Enter target directory for SDK (default: ~/poky_sdk): - You are about to install the SDK to "/home/scottrif/poky_sdk". Proceed[Y/n]? Y + You are about to install the SDK to "/home/scottrif/poky_sdk". Proceed [Y/n]? Y Extracting SDK......................................done Setting it up... Extracting buildtools... @@ -314,8 +316,8 @@ File:</emphasis> By default, the <ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE'><filename>MACHINE</filename></ulink> - variable is set to "qemux86", which is fine if you are - building for the QEMU emulator in 32-bit mode. + variable is set to "qemux86-64", which is fine if you are + building for the QEMU emulator in 64-bit mode. However, if you are not, you need to set the <filename>MACHINE</filename> variable appropriately in your <filename>conf/local.conf</filename> file found @@ -329,10 +331,12 @@ <ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS'><filename>MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS</filename></ulink> variable to include kernel modules.</para> - <para>This example uses the default "qemux86" for the - <filename>MACHINE</filename> variable but needs to - add the "kernel-modules": + <para>In this example we wish to build for qemux86 so + we must set the <filename>MACHINE</filename> variable + to "qemux86" and also add the "kernel-modules". As described + we do this by appending to <filename>conf/local.conf</filename>: <literallayout class='monospaced'> + MACHINE = "qemux86" MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS += "kernel-modules" </literallayout> </para></listitem> @@ -549,9 +553,9 @@ <literallayout class='monospaced'> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" - SRC_URI_append += "file://<replaceable>patch-file-one</replaceable>" - SRC_URI_append += "file://<replaceable>patch-file-two</replaceable>" - SRC_URI_append += "file://<replaceable>patch-file-three</replaceable>" + SRC_URI_append = " file://<replaceable>patch-file-one</replaceable>" + SRC_URI_append = " file://<replaceable>patch-file-two</replaceable>" + SRC_URI_append = " file://<replaceable>patch-file-three</replaceable>" </literallayout> The <ulink url='&YOCTO_DOCS_REF_URL;#var-FILESEXTRAPATHS'><filename>FILESEXTRAPATHS</filename></ulink> @@ -655,26 +659,22 @@ KMACHINE_genericx86-64 ?= "common-pc-64" KBRANCH_edgerouter = "standard/edgerouter" KBRANCH_beaglebone = "standard/beaglebone" - KBRANCH_mpc8315e-rdb = "standard/fsl-mpc8315e-rdb" SRCREV_machine_genericx86 ?= "d09f2ce584d60ecb7890550c22a80c48b83c2e19" SRCREV_machine_genericx86-64 ?= "d09f2ce584d60ecb7890550c22a80c48b83c2e19" SRCREV_machine_edgerouter ?= "b5c8cfda2dfe296410d51e131289fb09c69e1e7d" SRCREV_machine_beaglebone ?= "b5c8cfda2dfe296410d51e131289fb09c69e1e7d" - SRCREV_machine_mpc8315e-rdb ?= "2d1d010240846d7bff15d1fcc0cb6eb8a22fc78a" COMPATIBLE_MACHINE_genericx86 = "genericx86" COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64" COMPATIBLE_MACHINE_edgerouter = "edgerouter" COMPATIBLE_MACHINE_beaglebone = "beaglebone" - COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb" LINUX_VERSION_genericx86 = "4.12.7" LINUX_VERSION_genericx86-64 = "4.12.7" LINUX_VERSION_edgerouter = "4.12.10" LINUX_VERSION_beaglebone = "4.12.10" - LINUX_VERSION_mpc8315e-rdb = "4.12.10" </literallayout> This append file contains statements used to support several BSPs that ship with the Yocto Project. @@ -948,12 +948,14 @@ <literallayout class='monospaced'> KBUILD_DEFCONFIG_<replaceable>KMACHINE</replaceable> ?= <replaceable>defconfig_file</replaceable> </literallayout> - Here is an example that appends the - <filename>KBUILD_DEFCONFIG</filename> variable with - "common-pc" and provides the path to the "in-tree" - <filename>defconfig</filename> file: + Here is an example that assigns the + <filename>KBUILD_DEFCONFIG</filename> variable based on + "raspberrypi2" and provides the path to the "in-tree" + <filename>defconfig</filename> file + to be used for a Raspberry Pi 2, + which is based on the Broadcom 2708/2709 chipset: <literallayout class='monospaced'> - KBUILD_DEFCONFIG_common-pc ?= "/home/scottrif/configfiles/my_defconfig_file" + KBUILD_DEFCONFIG_raspberrypi2 ?= "bcm2709_defconfig" </literallayout> </para> @@ -1479,15 +1481,33 @@ <para> To use the <filename>menuconfig</filename> tool in the Yocto - Project development environment, you must launch it using - BitBake. - Thus, the environment must be set up using the - <ulink url='&YOCTO_DOCS_REF_URL;#structure-core-script'><filename>&OE_INIT_FILE;</filename></ulink> - script found in the - <ulink url='&YOCTO_DOCS_REF_URL;#build-directory'>Build Directory</ulink>. - You must also be sure of the state of your build's - configuration in the - <ulink url='&YOCTO_DOCS_REF_URL;#source-directory'>Source Directory</ulink>. + Project development environment, you must do the following: + <itemizedlist> + <listitem><para> + Because you launch <filename>menuconfig</filename> + using BitBake, you must be sure to set up your + environment by running the + <ulink url='&YOCTO_DOCS_REF_URL;#structure-core-script'><filename>&OE_INIT_FILE;</filename></ulink> + script found in the + <ulink url='&YOCTO_DOCS_REF_URL;#build-directory'>Build Directory</ulink>. + </para></listitem> + <listitem><para> + You must be sure of the state of your build's + configuration in the + <ulink url='&YOCTO_DOCS_REF_URL;#source-directory'>Source Directory</ulink>. + </para></listitem> + <listitem><para> + Your build host must have the following two packages + installed: + <literallayout class='monospaced'> + libncurses5-dev + libtinfo-dev + </literallayout> + </para></listitem> + </itemizedlist> + </para> + + <para> The following commands initialize the BitBake environment, run the <ulink url='&YOCTO_DOCS_REF_URL;#ref-tasks-kernel_configme'><filename>do_kernel_configme</filename></ulink> |