diff options
Diffstat (limited to 'poky/documentation')
20 files changed, 147 insertions, 184 deletions
diff --git a/poky/documentation/bsp-guide/bsp-guide.xml b/poky/documentation/bsp-guide/bsp-guide.xml index addb421181..f559e0809c 100644 --- a/poky/documentation/bsp-guide/bsp-guide.xml +++ b/poky/documentation/bsp-guide/bsp-guide.xml @@ -128,13 +128,8 @@ </revision> <revision> <revnumber>2.7</revnumber> - <date>May 2019</date> - <revremark>Released with the Yocto Project 2.7 Release.</revremark> - </revision> - <revision> - <revnumber>2.8</revnumber> <date>&REL_MONTH_YEAR;</date> - <revremark>Released with the Yocto Project 2.8 Release.</revremark> + <revremark>Released with the Yocto Project 2.7 Release.</revremark> </revision> </revhistory> diff --git a/poky/documentation/bsp-guide/bsp.xml b/poky/documentation/bsp-guide/bsp.xml index 58f5733f7a..0327f6db62 100644 --- a/poky/documentation/bsp-guide/bsp.xml +++ b/poky/documentation/bsp-guide/bsp.xml @@ -1902,11 +1902,10 @@ IMAGE_INSTALL_append = " kernel-devicetree kernel-image-zimage" do_image_wic[depends] += "mtools-native:do_populate_sysroot dosfstools-native:do_populate_sysroot" - SERIAL_CONSOLES ?= "115200;ttyS0 115200;ttyO0" - SERIAL_CONSOLES_CHECK = "${SERIAL_CONSOLES}" + SERIAL_CONSOLES = "115200;ttyO0" PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto" - PREFERRED_VERSION_linux-yocto ?= "5.0%" + PREFERRED_VERSION_linux-yocto ?= "4.12%" KERNEL_IMAGETYPE = "zImage" KERNEL_DEVICETREE = "am335x-bone.dtb am335x-boneblack.dtb am335x-bonegreen.dtb" @@ -1914,13 +1913,13 @@ SPL_BINARY = "MLO" UBOOT_SUFFIX = "img" - UBOOT_MACHINE = "am335x_evm_defconfig" + UBOOT_MACHINE = "am335x_boneblack_config" UBOOT_ENTRYPOINT = "0x80008000" UBOOT_LOADADDRESS = "0x80008000" MACHINE_FEATURES = "usbgadget usbhost vfat alsa" - IMAGE_BOOT_FILES ?= "u-boot.${UBOOT_SUFFIX} MLO zImage am335x-bone.dtb am335x-boneblack.dtb am335x-bonegreen.dtb" + IMAGE_BOOT_FILES ?= "u-boot.${UBOOT_SUFFIX} MLO" </literallayout> The variables used to configure the machine define machine-specific properties. @@ -1949,7 +1948,7 @@ In this case, the recipe that provides "virtual/xserver" is "xserver-xorg", which exists in - <filename>poky/meta/recipes-graphics/xorg-xserver</filename>. + <filename>poky/meta/recipes-graphics/xserver-xorg</filename>. </para></listitem> <listitem><para> <ulink url='&YOCTO_DOCS_REF_URL;#var-XSERVER'><filename>XSERVER</filename></ulink>: @@ -2062,7 +2061,7 @@ <listitem><para> <ulink url='&YOCTO_DOCS_REF_URL;#var-PREFERRED_VERSION'><filename>PREFERRED_VERSION_linux-yocto</filename></ulink>: Defines the version of the recipe used - to build the kernel, which is "5.0" in this + to build the kernel, which is "4.12" in this case. </para></listitem> <listitem><para> @@ -2073,8 +2072,8 @@ </para></listitem> <listitem><para> <ulink url='&YOCTO_DOCS_REF_URL;#var-KERNEL_DEVICETREE'><filename>KERNEL_DEVICETREE</filename></ulink>: - The names of the generated Linux kernel device - trees (i.e. the <filename>*.dtb</filename>) files. + The name of the generated Linux kernel device + tree (i.e. the <filename>.dtb</filename>) file. All the device trees for the various BeagleBone devices are included. <!-- @@ -2148,6 +2147,8 @@ when preparing the image using the Wic tool with the <filename>bootimg-partition</filename> source plugin. + In this case, the "u-boot.${UBOOT_SUFFIX}" and + "MLO" files are installed. </para></listitem> </itemizedlist> </para> @@ -2162,37 +2163,38 @@ machine configuration: <literallayout class='monospaced'> PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto" - PREFERRED_VERSION_linux-yocto ?= "5.0%" + PREFERRED_VERSION_linux-yocto ?= "4.12%" </literallayout> The <filename>meta-yocto-bsp/recipes-kernel/linux</filename> directory in the layer contains metadata used to build the kernel. - In this case, a kernel append file (i.e. - <filename>linux-yocto_5.0.bbappend</filename>) is used to - override an established kernel recipe (i.e. - <filename>linux-yocto_5.0.bb</filename>), which is + In this case, a kernel append file is used to + override an established kernel recipe, which is located in - <ulink url='&YOCTO_GIT_URL;/cgit/cgit.cgi/poky/tree/meta/recipes-kernel/linux'></ulink>. + <ulink url='&YOCTO_GIT_URL;/cgit/cgit.cgi/poky/tree/meta/recipes-kernel/linux'></ulink> + and named + <filename>linux-yocto_4.12.bb</filename>. </para> <para> Following is the contents of the append file: <literallayout class='monospaced'> - KBRANCH_genericx86 = "v5.0/standard/base" - KBRANCH_genericx86-64 = "v5.0/standard/base" - KBRANCH_edgerouter = "v5.0/standard/edgerouter" - KBRANCH_beaglebone-yocto = "v5.0/standard/beaglebone" - KBRANCH_mpc8315e-rdb = "v5.0/standard/fsl-mpc8315e-rdb" + KBRANCH_genericx86 = "standard/base" + KBRANCH_genericx86-64 = "standard/base" KMACHINE_genericx86 ?= "common-pc" KMACHINE_genericx86-64 ?= "common-pc-64" - KMACHINE_beaglebone-yocto ?= "beaglebone" + KBRANCH_edgerouter = "standard/edgerouter" + KBRANCH_beaglebone-yocto = "standard/beaglebone" + KMACHINE_beaglebone-yocto = "beaglebone" + KBRANCH_mpc8315e-rdb = "standard/fsl-mpc8315e-rdb" + + SRCREV_machine_genericx86 ?= "1c4ad569af3e23a77994235435040e322908687f" + SRCREV_machine_genericx86-64 ?= "1c4ad569af3e23a77994235435040e322908687f" + SRCREV_machine_edgerouter ?= "257f843ea367744620f1d92910afd2f454e31483" + SRCREV_machine_beaglebone-yocto ?= "257f843ea367744620f1d92910afd2f454e31483" + SRCREV_machine_mpc8315e-rdb ?= "014560874f9eb2a86138c9cc35046ff1720485e1" - SRCREV_machine_genericx86 ?= "3df4aae6074e94e794e27fe7f17451d9353cdf3d" - SRCREV_machine_genericx86-64 ?= "3df4aae6074e94e794e27fe7f17451d9353cdf3d" - SRCREV_machine_edgerouter ?= "3df4aae6074e94e794e27fe7f17451d9353cdf3d" - SRCREV_machine_beaglebone-yocto ?= "3df4aae6074e94e794e27fe7f17451d9353cdf3d" - SRCREV_machine_mpc8315e-rdb ?= "8b62af7f252af10588276802c4c6d7c502e875be" COMPATIBLE_MACHINE_genericx86 = "genericx86" COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64" @@ -2200,11 +2202,11 @@ COMPATIBLE_MACHINE_beaglebone-yocto = "beaglebone-yocto" COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb" - LINUX_VERSION_genericx86 = "5.0.3" - LINUX_VERSION_genericx86-64 = "5.0.3" - LINUX_VERSION_edgerouter = "5.0.3" - LINUX_VERSION_beaglebone-yocto = "5.0.3" - LINUX_VERSION_mpc8315e-rdb = "5.0.3" + LINUX_VERSION_genericx86 = "4.12.20" + LINUX_VERSION_genericx86-64 = "4.12.20" + LINUX_VERSION_edgerouter = "4.12.19" + LINUX_VERSION_beaglebone-yocto = "4.12.19" + LINUX_VERSION_mpc8315e-rdb = "4.12.19" </literallayout> This particular append file works for all the machines that are part of the @@ -2231,6 +2233,15 @@ <ulink url='&YOCTO_DOCS_REF_URL;#var-SRCREV'><filename>SRCREV</filename></ulink>: Identifies the revision of the source code used to build the image. +<!-- + You find out about that point in the kernel source tree by + doing the following command: + + git log ‐‐decorate 257f843ea367744620f1d92910afd2f454e31483 + + Returns information about the commit, which is usually + that it is a merge point for a stable kernel release. +--> </para></listitem> <listitem><para> <ulink url='&YOCTO_DOCS_REF_URL;#var-COMPATIBLE_MACHINE'><filename>COMPATIBLE_MACHINE</filename></ulink>: diff --git a/poky/documentation/dev-manual/dev-manual-common-tasks.xml b/poky/documentation/dev-manual/dev-manual-common-tasks.xml index 9231d1416e..8bc7fd8b2b 100644 --- a/poky/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/poky/documentation/dev-manual/dev-manual-common-tasks.xml @@ -1883,8 +1883,7 @@ <ulink url='&YOCTO_DOCS_REF_URL;#ref-tasks-fetch'><filename>do_fetch</filename></ulink> task uses the prefix of each entry in the <filename>SRC_URI</filename> variable value to determine which - <ulink url='&YOCTO_DOCS_BB_URL;#bb-fetchers'>fetcher</ulink> - to use to get your source files. + fetcher to use to get your source files. It is the <filename>SRC_URI</filename> variable that triggers the fetcher. The @@ -7398,17 +7397,17 @@ it is based on is by definition incomplete. The purpose of the command is to allow the generation of customized images, and as such, was designed to be - completely extensible through a plugin interface. + completely extensible through a plug-in interface. See the - "<link linkend='wic-using-the-wic-plugin-interface'>Using the Wic PlugIn Interface</link>" - section for information on these plugins. + "<link linkend='wic-using-the-wic-plug-ins-interface'>Using the Wic Plug-Ins Interface</link>" + section for information on these plug-ins. </para> <para> This section provides some background information on Wic, describes what you need to have in place to run the tool, provides instruction on how to use - the Wic utility, provides information on using the Wic plugins + the Wic utility, provides information on using the Wic plug-ins interface, and provides several examples that show how to use Wic. </para> @@ -7803,28 +7802,28 @@ </para> </section> - <section id='wic-using-the-wic-plugin-interface'> - <title>Using the Wic Plugin Interface</title> + <section id='wic-using-the-wic-plug-ins-interface'> + <title>Using the Wic Plug-Ins Interface</title> <para> You can extend and specialize Wic functionality by using - Wic plugins. - This section explains the Wic plugin interface. + Wic plug-ins. + This section explains the Wic plug-in interface. <note> - Wic plugins consist of "source" and "imager" plugins. - Imager plugins are beyond the scope of this section. + Wic plug-ins consist of "source" and "imager" plug-ins. + Imager plug-ins are beyond the scope of this section. </note> </para> <para> - Source plugins provide a mechanism to customize partition + Source plug-ins provide a mechanism to customize partition content during the Wic image generation process. - You can use source plugins to map values that you specify + You can use source plug-ins to map values that you specify using <filename>--source</filename> commands in kickstart - files (i.e. <filename>*.wks</filename>) to a plugin + files (i.e. <filename>*.wks</filename>) to a plug-in implementation used to populate a given partition. <note> - If you use plugins that have build-time dependencies + If you use plug-ins that have build-time dependencies (e.g. native tools, bootloaders, and so forth) when building a Wic image, you need to specify those dependencies using the @@ -7834,43 +7833,43 @@ </para> <para> - Source plugins are subclasses defined in plugin files. - As shipped, the Yocto Project provides several plugin + Source plug-ins are subclasses defined in plug-in files. + As shipped, the Yocto Project provides several plug-in files. - You can see the source plugin files that ship with the + You can see the source plug-in files that ship with the Yocto Project <ulink url='&YOCTO_GIT_URL;/cgit/cgit.cgi/poky/tree/scripts/lib/wic/plugins/source'>here</ulink>. - Each of these plugin files contains source plugins that + Each of these plug-in files contains source plug-ins that are designed to populate a specific Wic image partition. </para> <para> - Source plugins are subclasses of the + Source plug-ins are subclasses of the <filename>SourcePlugin</filename> class, which is defined in the <filename>poky/scripts/lib/wic/pluginbase.py</filename> file. For example, the <filename>BootimgEFIPlugin</filename> - source plugin found in the + source plug-in found in the <filename>bootimg-efi.py</filename> file is a subclass of the <filename>SourcePlugin</filename> class, which is found in the <filename>pluginbase.py</filename> file. </para> <para> - You can also implement source plugins in a layer outside + You can also implement source plug-ins in a layer outside of the Source Repositories (external layer). - To do so, be sure that your plugin files are located in + To do so, be sure that your plug-in files are located in a directory whose path is <filename>scripts/lib/wic/plugins/source/</filename> within your external layer. - When the plugin files are located there, the source - plugins they contain are made available to Wic. + When the plug-in files are located there, the source + plug-ins they contain are made available to Wic. </para> <para> When the Wic implementation needs to invoke a - partition-specific implementation, it looks for the plugin + partition-specific implementation, it looks for the plug-in with the same name as the <filename>--source</filename> parameter used in the kickstart file given to that partition. @@ -7880,13 +7879,13 @@ part /boot --source bootimg-pcbios --ondisk sda --label boot --active --align 1024 </literallayout> The methods defined as class members of the matching - source plugin (i.e. <filename>bootimg-pcbios</filename>) - in the <filename>bootimg-pcbios.py</filename> plugin file + source plug-in (i.e. <filename>bootimg-pcbios</filename>) + in the <filename>bootimg-pcbios.py</filename> plug-in file are used. </para> <para> - To be more concrete, here is the corresponding plugin + To be more concrete, here is the corresponding plug-in definition from the <filename>bootimg-pcbios.py</filename> file for the previous command along with an example method called by the Wic implementation when it needs to @@ -7918,19 +7917,19 @@ . . </literallayout> - If a subclass (plugin) itself does not implement a + If a subclass (plug-in) itself does not implement a particular function, Wic locates and uses the default version in the superclass. - It is for this reason that all source plugins are derived + It is for this reason that all source plug-ins are derived from the <filename>SourcePlugin</filename> class. </para> <para> The <filename>SourcePlugin</filename> class defined in the <filename>pluginbase.py</filename> file defines - a set of methods that source plugins can implement or + a set of methods that source plug-ins can implement or override. - Any plugins (subclass of + Any plug-ins (subclass of <filename>SourcePlugin</filename>) that do not implement a particular method inherit the implementation of the method from the <filename>SourcePlugin</filename> class. @@ -7991,11 +7990,11 @@ </para> <para> - You can extend the source plugin mechanism. - To add more hooks, create more source plugin methods + You can extend the source plug-in mechanism. + To add more hooks, create more source plug-in methods within <filename>SourcePlugin</filename> and the corresponding derived subclasses. - The code that calls the plugin methods uses the + The code that calls the plug-in methods uses the <filename>plugin.get_source_plugin_methods()</filename> function to find the method or methods needed by the call. Retrieval of those methods is accomplished by filling up @@ -9421,7 +9420,7 @@ <para> Many pieces of software split functionality into optional - modules (or plugins) and the plugins that are built + modules (or plug-ins) and the plug-ins that are built might depend on configuration options. To avoid having to duplicate the logic that determines what modules are available in your recipe or to avoid having @@ -15364,12 +15363,12 @@ </para> <para> - Specifying audio and video plugins as part of the + Specifying audio and video plug-ins as part of the <filename>COMMERCIAL_AUDIO_PLUGINS</filename> and <filename>COMMERCIAL_VIDEO_PLUGINS</filename> statements (along with the enabling <filename>LICENSE_FLAGS_WHITELIST</filename>) includes the - plugins or components into built images, thus adding + plug-ins or components into built images, thus adding support for media formats or components. </para> </section> diff --git a/poky/documentation/dev-manual/dev-manual.xml b/poky/documentation/dev-manual/dev-manual.xml index 42deff1028..5dda016d78 100644 --- a/poky/documentation/dev-manual/dev-manual.xml +++ b/poky/documentation/dev-manual/dev-manual.xml @@ -113,13 +113,8 @@ </revision> <revision> <revnumber>2.7</revnumber> - <date>May 2019</date> - <revremark>Released with the Yocto Project 2.7 Release.</revremark> - </revision> - <revision> - <revnumber>2.8</revnumber> <date>&REL_MONTH_YEAR;</date> - <revremark>Released with the Yocto Project 2.8 Release.</revremark> + <revremark>Released with the Yocto Project 2.7 Release.</revremark> </revision> </revhistory> diff --git a/poky/documentation/kernel-dev/kernel-dev.xml b/poky/documentation/kernel-dev/kernel-dev.xml index c43330a31e..33553df060 100644 --- a/poky/documentation/kernel-dev/kernel-dev.xml +++ b/poky/documentation/kernel-dev/kernel-dev.xml @@ -98,13 +98,8 @@ </revision> <revision> <revnumber>2.7</revnumber> - <date>May 2019</date> - <revremark>Released with the Yocto Project 2.7 Release.</revremark> - </revision> - <revision> - <revnumber>2.8</revnumber> <date>&REL_MONTH_YEAR;</date> - <revremark>Released with the Yocto Project 2.8 Release.</revremark> + <revremark>Released with the Yocto Project 2.7 Release.</revremark> </revision> </revhistory> diff --git a/poky/documentation/mega-manual/mega-manual.xml b/poky/documentation/mega-manual/mega-manual.xml index b66b9334fb..37d26492d9 100644 --- a/poky/documentation/mega-manual/mega-manual.xml +++ b/poky/documentation/mega-manual/mega-manual.xml @@ -84,13 +84,8 @@ </revision> <revision> <revnumber>2.7</revnumber> - <date>May 2019</date> - <revremark>Released with the Yocto Project 2.7 Release.</revremark> - </revision> - <revision> - <revnumber>2.8</revnumber> <date>&REL_MONTH_YEAR;</date> - <revremark>Released with the Yocto Project 2.8 Release.</revremark> + <revremark>Released with the Yocto Project 2.7 Release.</revremark> </revision> </revhistory> diff --git a/poky/documentation/overview-manual/overview-manual-concepts.xml b/poky/documentation/overview-manual/overview-manual-concepts.xml index f085dd710d..1f41ac8cf6 100644 --- a/poky/documentation/overview-manual/overview-manual-concepts.xml +++ b/poky/documentation/overview-manual/overview-manual-concepts.xml @@ -943,7 +943,7 @@ <ulink url='&YOCTO_DOCS_REF_URL;#var-DL_DIR'><filename>DL_DIR</filename></ulink> directory, see the <ulink url='&YOCTO_DOCS_REF_URL;#var-BB_GENERATE_MIRROR_TARBALLS'><filename>BB_GENERATE_MIRROR_TARBALLS</filename></ulink> - variable in the Yocto Project Reference Manual. + variable. </note> </para> diff --git a/poky/documentation/overview-manual/overview-manual.xml b/poky/documentation/overview-manual/overview-manual.xml index e74ba8d5c2..b23c39497c 100644 --- a/poky/documentation/overview-manual/overview-manual.xml +++ b/poky/documentation/overview-manual/overview-manual.xml @@ -37,14 +37,9 @@ <revremark>The initial document released with the Yocto Project 2.5 Release.</revremark> </revision> <revision> - <revnumber>2.7</revnumber> - <date>May 2019</date> - <revremark>Released with the Yocto Project 2.7 Release.</revremark> - </revision> - <revision> - <revnumber>2.8</revnumber> + <revnumber>2.6</revnumber> <date>&REL_MONTH_YEAR;</date> - <revremark>Released with the Yocto Project 2.8 Release.</revremark> + <revremark>Released with the Yocto Project 2.6 Release.</revremark> </revision> </revhistory> diff --git a/poky/documentation/poky.ent b/poky/documentation/poky.ent index b5f6009698..199e651089 100644 --- a/poky/documentation/poky.ent +++ b/poky/documentation/poky.ent @@ -1,17 +1,17 @@ -<!ENTITY DISTRO "2.8"> -<!ENTITY DISTRO_COMPRESSED "28"> -<!ENTITY DISTRO_NAME_NO_CAP "zeus"> -<!ENTITY DISTRO_NAME "Zeus"> -<!ENTITY DISTRO_NAME_NO_CAP_MINUS_ONE "warrior"> -<!ENTITY DISTRO_NAME_MINUS_ONE "Warrior"> -<!ENTITY YOCTO_DOC_VERSION "2.8"> -<!ENTITY YOCTO_DOC_VERSION_MINUS_ONE "2.7"> -<!ENTITY DISTRO_REL_TAG "yocto-2.8"> -<!ENTITY METAINTELVERSION "9.0"> -<!ENTITY REL_MONTH_YEAR "TBD"> +<!ENTITY DISTRO "2.7"> +<!ENTITY DISTRO_COMPRESSED "27"> +<!ENTITY DISTRO_NAME_NO_CAP "warrior"> +<!ENTITY DISTRO_NAME "Warrior"> +<!ENTITY DISTRO_NAME_NO_CAP_MINUS_ONE "thud"> +<!ENTITY DISTRO_NAME_MINUS_ONE "Thud"> +<!ENTITY YOCTO_DOC_VERSION "2.7"> +<!ENTITY YOCTO_DOC_VERSION_MINUS_ONE "2.6"> +<!ENTITY DISTRO_REL_TAG "yocto-2.7"> +<!ENTITY METAINTELVERSION "11.0"> +<!ENTITY REL_MONTH_YEAR "May 2019"> <!ENTITY META_INTEL_REL_TAG "&METAINTELVERSION;-&DISTRO_NAME_NO_CAP;-&YOCTO_DOC_VERSION;"> -<!ENTITY POKYVERSION "22.0.0"> -<!ENTITY POKYVERSION_COMPRESSED "2200"> +<!ENTITY POKYVERSION "21.0.0"> +<!ENTITY POKYVERSION_COMPRESSED "2100"> <!ENTITY YOCTO_POKY "poky-&DISTRO_NAME_NO_CAP;-&POKYVERSION;"> <!ENTITY COPYRIGHT_YEAR "2010-2019"> <!ENTITY YOCTO_DL_URL "http://downloads.yoctoproject.org"> diff --git a/poky/documentation/profile-manual/profile-manual.xml b/poky/documentation/profile-manual/profile-manual.xml index c6e8baf023..af2c7baf72 100644 --- a/poky/documentation/profile-manual/profile-manual.xml +++ b/poky/documentation/profile-manual/profile-manual.xml @@ -98,13 +98,8 @@ </revision> <revision> <revnumber>2.7</revnumber> - <date>May 2019</date> - <revremark>Released with the Yocto Project 2.7 Release.</revremark> - </revision> - <revision> - <revnumber>2.8</revnumber> <date>&REL_MONTH_YEAR;</date> - <revremark>Released with the Yocto Project 2.8 Release.</revremark> + <revremark>Released with the Yocto Project 2.7 Release.</revremark> </revision> </revhistory> diff --git a/poky/documentation/ref-manual/migration.xml b/poky/documentation/ref-manual/migration.xml index ade8787b4d..a4d72dd6b7 100644 --- a/poky/documentation/ref-manual/migration.xml +++ b/poky/documentation/ref-manual/migration.xml @@ -4504,8 +4504,8 @@ id=f4d4f99cfbc2396e49c1613a7d237b9e57f06f81'>commit message</ulink>. </para></listitem> <listitem><para> <emphasis>fsimage Plug-in Removed:</emphasis> - The Wic fsimage plugin has been removed as it duplicates - functionality of the rawcopy plugin. + The Wic fsimage plug-in has been removed as it duplicates + functionality of the rawcopy plug-in. </para></listitem> </itemizedlist> </para> @@ -6361,7 +6361,7 @@ id=f4d4f99cfbc2396e49c1613a7d237b9e57f06f81'>commit message</ulink>. Support for the Eclipse IDE has been removed. Support continues for those releases prior to 2.7 that did include support. - The 2.7 release does not include the Eclipse Yocto plugin. + The 2.7 release does not include the Eclipse Yocto plug-in. </para> </section> diff --git a/poky/documentation/ref-manual/ref-features.xml b/poky/documentation/ref-manual/ref-features.xml index b057d2d040..7a3555d0b9 100644 --- a/poky/documentation/ref-manual/ref-features.xml +++ b/poky/documentation/ref-manual/ref-features.xml @@ -76,6 +76,8 @@ </para></listitem> <listitem><para><emphasis>ext2:</emphasis> Hardware HDD or Microdrive </para></listitem> + <listitem><para><emphasis>irda:</emphasis> Hardware has IrDA support + </para></listitem> <listitem><para><emphasis>keyboard:</emphasis> Hardware has a keyboard </para></listitem> <listitem><para><emphasis>pcbios:</emphasis> Support for booting through BIOS @@ -188,6 +190,8 @@ support.</para></listitem> <listitem><para><emphasis>ipv6:</emphasis> Include IPv6 support. </para></listitem> + <listitem><para><emphasis>irda:</emphasis> Include IrDA support. + </para></listitem> <listitem><para><emphasis>keyboard:</emphasis> Include keyboard support (e.g. keymaps will be loaded during boot). </para></listitem> diff --git a/poky/documentation/ref-manual/ref-kickstart.xml b/poky/documentation/ref-manual/ref-kickstart.xml index 1128bd50d0..a58f9d7c96 100644 --- a/poky/documentation/ref-manual/ref-kickstart.xml +++ b/poky/documentation/ref-manual/ref-kickstart.xml @@ -117,9 +117,9 @@ This option is a Wic-specific option that names the source of the data that populates the partition. The most common value for this option is "rootfs", but you - can use any value that maps to a valid source plugin. - For information on the source plugins, see the - "<ulink url='&YOCTO_DOCS_DEV_URL;#wic-using-the-wic-plugin-interface'>Using the Wic Plugins Interface</ulink>" + can use any value that maps to a valid source plug-in. + For information on the source plug-ins, see the + "<ulink url='&YOCTO_DOCS_DEV_URL;#wic-using-the-wic-plug-ins-interface'>Using the Wic Plug-Ins Interface</ulink>" section in the Yocto Project Development Tasks Manual. </para> @@ -139,12 +139,12 @@ <filename>--source <replaceable>plugin-name</replaceable></filename>, Wic creates a partition as large as needed and fills it with the contents of the partition that is generated by the - specified plugin name using the data pointed to by the + specified plug-in name using the data pointed to by the <filename>-r</filename> command-line option or the equivalent rootfs derived from the <filename>-e</filename> command-line option. Exactly what those contents are and filesystem type used are - dependent on the given plugin implementation. + dependent on the given plug-in implementation. </para> <para>If you do not use the <filename>--source</filename> @@ -220,7 +220,7 @@ This option is a Wic-specific option that excludes the given relative path from the resulting image. This option is only effective with the rootfs source - plugin. + plug-in. </para></listitem> <listitem><para> <emphasis><filename>--extra-space</filename>:</emphasis> @@ -299,7 +299,7 @@ supports the following options: <note> Bootloader functionality and boot partitions are implemented by - the various <filename>--source</filename> plugins that + the various <filename>--source</filename> plug-ins that implement bootloader functionality. The bootloader command essentially provides a means of modifying bootloader configuration. diff --git a/poky/documentation/ref-manual/ref-manual.xml b/poky/documentation/ref-manual/ref-manual.xml index fc4319773b..26295f02f6 100644 --- a/poky/documentation/ref-manual/ref-manual.xml +++ b/poky/documentation/ref-manual/ref-manual.xml @@ -129,13 +129,8 @@ </revision> <revision> <revnumber>2.7</revnumber> - <date>May 2019</date> - <revremark>Released with the Yocto Project 2.7 Release.</revremark> - </revision> - <revision> - <revnumber>2.8</revnumber> <date>&REL_MONTH_YEAR;</date> - <revremark>Released with the Yocto Project 2.8 Release.</revremark> + <revremark>Released with the Yocto Project 2.7 Release.</revremark> </revision> </revhistory> diff --git a/poky/documentation/ref-manual/ref-tasks.xml b/poky/documentation/ref-manual/ref-tasks.xml index 011e0d7496..734a5a752d 100644 --- a/poky/documentation/ref-manual/ref-tasks.xml +++ b/poky/documentation/ref-manual/ref-tasks.xml @@ -166,8 +166,7 @@ This task uses the <link linkend='var-SRC_URI'><filename>SRC_URI</filename></link> variable and the argument's prefix to determine the correct - <ulink url='&YOCTO_DOCS_BB_URL;#bb-fetchers'>fetcher</ulink> - module. + fetcher module. </para> </section> diff --git a/poky/documentation/ref-manual/ref-variables.xml b/poky/documentation/ref-manual/ref-variables.xml index 12876e3d9a..1e3f282a53 100644 --- a/poky/documentation/ref-manual/ref-variables.xml +++ b/poky/documentation/ref-manual/ref-variables.xml @@ -11309,7 +11309,7 @@ Here are two examples: <literallayout class='monospaced'> PREFERRED_VERSION_python = "3.4.0" - PREFERRED_VERSION_linux-yocto = "5.0%" + PREFERRED_VERSION_linux-yocto = "4.12%" </literallayout> <note><title>Important</title> The use of the "<filename>%</filename>" character @@ -11355,14 +11355,14 @@ to set a machine-specific override. Here is an example: <literallayout class='monospaced'> - PREFERRED_VERSION_linux-yocto_qemux86 = "5.0%" + PREFERRED_VERSION_linux-yocto_qemux86 = "4.12%" </literallayout> Although not recommended, worst case, you can also use the "forcevariable" override, which is the strongest override possible. Here is an example: <literallayout class='monospaced'> - PREFERRED_VERSION_linux-yocto_forcevariable = "5.0%" + PREFERRED_VERSION_linux-yocto_forcevariable = "4.12%" </literallayout> <note> The <filename>_forcevariable</filename> override is @@ -13722,9 +13722,6 @@ a secure shell.</para></listitem> <listitem><para><emphasis><filename>svn://</filename> -</emphasis> Fetches files from a Subversion (<filename>svn</filename>) revision control repository.</para></listitem> - <listitem><para><emphasis><filename>npm://</filename> -</emphasis> Fetches JavaScript - modules from a registry. - </para></listitem> </itemizedlist> </para> diff --git a/poky/documentation/sdk-manual/sdk-extensible.xml b/poky/documentation/sdk-manual/sdk-extensible.xml index bd5278493f..f7c5c00b8b 100644 --- a/poky/documentation/sdk-manual/sdk-extensible.xml +++ b/poky/documentation/sdk-manual/sdk-extensible.xml @@ -825,9 +825,7 @@ versioning schemes, extract code into or out of the <filename>devtool</filename> <ulink url='&YOCTO_DOCS_REF_URL;#devtool-the-workspace-layer-structure'>workspace</ulink>, - and work with any source file forms that the - <ulink url='&YOCTO_DOCS_BB_URL;#bb-fetchers'>fetchers</ulink> - support. + and work with any source file forms that the fetchers support. </para> <para> diff --git a/poky/documentation/sdk-manual/sdk-manual.xml b/poky/documentation/sdk-manual/sdk-manual.xml index 7edd2c46aa..9ce4a5b03d 100644 --- a/poky/documentation/sdk-manual/sdk-manual.xml +++ b/poky/documentation/sdk-manual/sdk-manual.xml @@ -63,13 +63,8 @@ </revision> <revision> <revnumber>2.7</revnumber> - <date>May 2019</date> - <revremark>Released with the Yocto Project 2.7 Release.</revremark> - </revision> - <revision> - <revnumber>2.8</revnumber> <date>&REL_MONTH_YEAR;</date> - <revremark>Released with the Yocto Project 2.8 Release.</revremark> + <revremark>Released with the Yocto Project 2.7 Release.</revremark> </revision> </revhistory> diff --git a/poky/documentation/toaster-manual/toaster-manual.xml b/poky/documentation/toaster-manual/toaster-manual.xml index b31659ffb5..42dc6a33eb 100644 --- a/poky/documentation/toaster-manual/toaster-manual.xml +++ b/poky/documentation/toaster-manual/toaster-manual.xml @@ -73,13 +73,8 @@ </revision> <revision> <revnumber>2.7</revnumber> - <date>May 2019</date> - <revremark>Released with the Yocto Project 2.7 Release.</revremark> - </revision> - <revision> - <revnumber>2.8</revnumber> <date>&REL_MONTH_YEAR;</date> - <revremark>Released with the Yocto Project 2.8 Release.</revremark> + <revremark>Released with the Yocto Project 2.7 Release.</revremark> </revision> </revhistory> diff --git a/poky/documentation/tools/mega-manual.sed b/poky/documentation/tools/mega-manual.sed index 9c4f4e2ede..79bbeef575 100644 --- a/poky/documentation/tools/mega-manual.sed +++ b/poky/documentation/tools/mega-manual.sed @@ -1,36 +1,36 @@ # Processes bitbake-user-manual (<word>-<word>-<word> style). # This style is for manual three-word folders, which currently is only the BitBake User Manual. # We used to have the "yocto-project-qs" and "poky-ref-manual" folders but no longer do. -# s@"ulink" href="http://www.yoctoproject.org/docs/2.8/[a-z]*-[a-z]*-[a-z]*/[a-z]*-[a-z]*-[a-z]*.html#@"link" href="#@g -s@"ulink" href="http://www.yoctoproject.org/docs/2.8/bitbake-user-manual/bitbake-user-manual.html#@"link" href="#@g +# s@"ulink" href="http://www.yoctoproject.org/docs/2.7/[a-z]*-[a-z]*-[a-z]*/[a-z]*-[a-z]*-[a-z]*.html#@"link" href="#@g +s@"ulink" href="http://www.yoctoproject.org/docs/2.7/bitbake-user-manual/bitbake-user-manual.html#@"link" href="#@g # Processes all other manuals (<word>-<word> style). # This style is for manual folders that use two word, which is the standard now (e.g. "ref-manual"). # Here is the one-liner: -# s@"ulink" href="http://www.yoctoproject.org/docs/2.8/[a-z]*-[a-z]*/[a-z]*-[a-z]*.html#@"link" href="#@g +# s@"ulink" href="http://www.yoctoproject.org/docs/2.7/[a-z]*-[a-z]*/[a-z]*-[a-z]*.html#@"link" href="#@g -s@"ulink" href="http://www.yoctoproject.org/docs/2.8/sdk-manual/sdk-manual.html#@"link" href="#@g -s@"ulink" href="http://www.yoctoproject.org/docs/2.8/bsp-guide/bsp-guide.html#@"link" href="#@g -s@"ulink" href="http://www.yoctoproject.org/docs/2.8/dev-manual/dev-manual.html#@"link" href="#@g -s@"ulink" href="http://www.yoctoproject.org/docs/2.8/overview-manual/overview-manual.html#@"link" href="#@g -s@"ulink" href="http://www.yoctoproject.org/docs/2.8/brief-yoctoprojectqs/brief-yoctoprojectqs.html#@"link" href="#@g -s@"ulink" href="http://www.yoctoproject.org/docs/2.8/kernel-dev/kernel-dev.html#@"link" href="#@g -s@"ulink" href="http://www.yoctoproject.org/docs/2.8/profile-manual/profile-manual.html#@"link" href="#@g -s@"ulink" href="http://www.yoctoproject.org/docs/2.8/ref-manual/ref-manual.html#@"link" href="#@g -s@"ulink" href="http://www.yoctoproject.org/docs/2.8/toaster-manual/toaster-manual.html#@"link" href="#@g +s@"ulink" href="http://www.yoctoproject.org/docs/2.7/sdk-manual/sdk-manual.html#@"link" href="#@g +s@"ulink" href="http://www.yoctoproject.org/docs/2.7/bsp-guide/bsp-guide.html#@"link" href="#@g +s@"ulink" href="http://www.yoctoproject.org/docs/2.7/dev-manual/dev-manual.html#@"link" href="#@g +s@"ulink" href="http://www.yoctoproject.org/docs/2.7/overview-manual/overview-manual.html#@"link" href="#@g +s@"ulink" href="http://www.yoctoproject.org/docs/2.7/brief-yoctoprojectqs/brief-yoctoprojectqs.html#@"link" href="#@g +s@"ulink" href="http://www.yoctoproject.org/docs/2.7/kernel-dev/kernel-dev.html#@"link" href="#@g +s@"ulink" href="http://www.yoctoproject.org/docs/2.7/profile-manual/profile-manual.html#@"link" href="#@g +s@"ulink" href="http://www.yoctoproject.org/docs/2.7/ref-manual/ref-manual.html#@"link" href="#@g +s@"ulink" href="http://www.yoctoproject.org/docs/2.7/toaster-manual/toaster-manual.html#@"link" href="#@g # Process cases where just an external manual is referenced without an id anchor -s@<a class="ulink" href="http://www.yoctoproject.org/docs/2.8/brief-yoctoprojectqs/brief-yoctoprojectqs.html" target="_top">Yocto Project Quick Build</a>@Yocto Project Quick Build@g -s@<a class="ulink" href="http://www.yoctoproject.org/docs/2.8/bitbake-user-manual/bitbake-user-manual.html" target="_top">BitBake User Manual</a>@BitBake User Manual@g -s@<a class="ulink" href="http://www.yoctoproject.org/docs/2.8/dev-manual/dev-manual.html" target="_top">Yocto Project Development Tasks Manual</a>@Yocto Project Development Tasks Manual@g -s@<a class="ulink" href="http://www.yoctoproject.org/docs/2.8/overview-manual/overview-manual.html" target="_top">Yocto Project Overview and Concepts Manual</a>@Yocto project Overview and Concepts Manual@g -s@<a class="ulink" href="http://www.yoctoproject.org/docs/2.8/sdk-manual/sdk-manual.html" target="_top">Yocto Project Application Development and the Extensible Software Development Kit (eSDK)</a>@Yocto Project Application Development and the Extensible Software Development Kit (eSDK)@g -s@<a class="ulink" href="http://www.yoctoproject.org/docs/2.8/bsp-guide/bsp-guide.html" target="_top">Yocto Project Board Support Package (BSP) Developer's Guide</a>@Yocto Project Board Support Package (BSP) Developer's Guide@g -s@<a class="ulink" href="http://www.yoctoproject.org/docs/2.8/profile-manual/profile-manual.html" target="_top">Yocto Project Profiling and Tracing Manual</a>@Yocto Project Profiling and Tracing Manual@g -s@<a class="ulink" href="http://www.yoctoproject.org/docs/2.8/kernel-dev/kernel-dev.html" target="_top">Yocto Project Linux Kernel Development Manual</a>@Yocto Project Linux Kernel Development Manual@g -s@<a class="ulink" href="http://www.yoctoproject.org/docs/2.8/ref-manual/ref-manual.html" target="_top">Yocto Project Reference Manual</a>@Yocto Project Reference Manual@g -s@<a class="ulink" href="http://www.yoctoproject.org/docs/2.8/toaster-manual/toaster-manual.html" target="_top">Toaster User Manual</a>@Toaster User Manual@g +s@<a class="ulink" href="http://www.yoctoproject.org/docs/2.7/brief-yoctoprojectqs/brief-yoctoprojectqs.html" target="_top">Yocto Project Quick Build</a>@Yocto Project Quick Build@g +s@<a class="ulink" href="http://www.yoctoproject.org/docs/2.7/bitbake-user-manual/bitbake-user-manual.html" target="_top">BitBake User Manual</a>@BitBake User Manual@g +s@<a class="ulink" href="http://www.yoctoproject.org/docs/2.7/dev-manual/dev-manual.html" target="_top">Yocto Project Development Tasks Manual</a>@Yocto Project Development Tasks Manual@g +s@<a class="ulink" href="http://www.yoctoproject.org/docs/2.7/overview-manual/overview-manual.html" target="_top">Yocto Project Overview and Concepts Manual</a>@Yocto project Overview and Concepts Manual@g +s@<a class="ulink" href="http://www.yoctoproject.org/docs/2.7/sdk-manual/sdk-manual.html" target="_top">Yocto Project Application Development and the Extensible Software Development Kit (eSDK)</a>@Yocto Project Application Development and the Extensible Software Development Kit (eSDK)@g +s@<a class="ulink" href="http://www.yoctoproject.org/docs/2.7/bsp-guide/bsp-guide.html" target="_top">Yocto Project Board Support Package (BSP) Developer's Guide</a>@Yocto Project Board Support Package (BSP) Developer's Guide@g +s@<a class="ulink" href="http://www.yoctoproject.org/docs/2.7/profile-manual/profile-manual.html" target="_top">Yocto Project Profiling and Tracing Manual</a>@Yocto Project Profiling and Tracing Manual@g +s@<a class="ulink" href="http://www.yoctoproject.org/docs/2.7/kernel-dev/kernel-dev.html" target="_top">Yocto Project Linux Kernel Development Manual</a>@Yocto Project Linux Kernel Development Manual@g +s@<a class="ulink" href="http://www.yoctoproject.org/docs/2.7/ref-manual/ref-manual.html" target="_top">Yocto Project Reference Manual</a>@Yocto Project Reference Manual@g +s@<a class="ulink" href="http://www.yoctoproject.org/docs/2.7/toaster-manual/toaster-manual.html" target="_top">Toaster User Manual</a>@Toaster User Manual@g # Process a single, rouge occurrence of a linked reference to the Mega-Manual. -s@<a class="ulink" href="http://www.yoctoproject.org/docs/2.8/mega-manual/mega-manual.html" target="_top">Yocto Project Mega-Manual</a>@Yocto Project Mega-Manual@g +s@<a class="ulink" href="http://www.yoctoproject.org/docs/2.7/mega-manual/mega-manual.html" target="_top">Yocto Project Mega-Manual</a>@Yocto Project Mega-Manual@g |