diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml b/documentation/yocto-project-qs/yocto-project-qs.xml index c2e019a1aa..c481d5f54f 100644 --- a/documentation/yocto-project-qs/yocto-project-qs.xml +++ b/documentation/yocto-project-qs/yocto-project-qs.xml @@ -176,7 +176,7 @@ The latest release images for the Yocto Project are kept at - . + . Nightly and developmental builds are also maintained. However, for this document a released version of Yocto Project is used. @@ -230,9 +230,9 @@ - $ wget http://www.yoctoproject.org/downloads/poky/poky-laverne-4.0.tar.bz2 - $ tar xjf poky-laverne-4.0.tar.bz2 - $ source poky-laverne-4.0/poky-init-build-env poky-4.0-build + $ wget http://www.yoctoproject.org/downloads/poky/poky-bernard-5.0.tar.bz2 + $ tar xjf poky-bernard-5.0.tar.bz2 + $ source poky-bernard-5.0/poky-init-build-env poky-5.0-build @@ -250,8 +250,8 @@ The first two commands extract the Yocto Project files from the release tarball and place them into a subdirectory of your current directory. The source command creates the - poky-4.0-build directory and executes the cd - command to make poky-4.0-build the working directory. + poky-5.0-build directory and executes the cd + command to make poky-5.0-build the working directory. The resulting build directory contains all the files created during the build. By default the target architecture is qemux86. To change this default, edit the value of the MACHINE variable in the @@ -353,9 +353,10 @@ Installing the Toolchain You can download the pre-built toolchain, which includes the poky-qemu script and - support files, from . + support files, from + . Toolchains are available for 32-bit and 64-bit development systems from the - i586 and x86_64 folders, respectively. + i686 and x86_64 folders, respectively. Each type of development system supports five target architectures. The tarball files are named such that a string representing the host system appears first in the filename and then is immediately followed by a string representing @@ -367,10 +368,10 @@ Where: <host_system> is a string representing your development system: - i586 or x86_64. + i686 or x86_64. <arch> is a string representing the target architecture: - i585, x86_64, powerpc, mips, or arm. + i686, x86_64, powerpc, mips, or arm. <release> is the version of Yocto Project. @@ -381,7 +382,7 @@ - yocto-eglibc-x86_64-i586-toolchain-sdk-0.9.tar.bz2 + yocto-eglibc-x86_64-i686-toolchain-sdk-1.0.tar.bz2 @@ -393,7 +394,7 @@ $ cd / - $ sudo tar -xvjf yocto-eglibc-x86_64-i586-toolchain-sdk-0.9.tar.bz2 + $ sudo tar -xvjf yocto-eglibc-x86_64-i686-toolchain-sdk-1.0.tar.bz2 @@ -403,7 +404,7 @@ You can download the pre-built Linux kernel and the filesystem image suitable for running in the emulator QEMU from - . + . Be sure to use the kernel and filesystem image that matches the architecture you want to simulate. @@ -455,10 +456,10 @@ Where: <arch> is a string representing the target architecture: - i586, x86_64, ppc603e, mips, or armv5te. + i686, x86_64, ppc603e, mips, or armv5te. <if> is a string representing an embedded application binary interface. - Not all setup scripts include this string. + Not all setup scripts include this string. @@ -466,17 +467,16 @@ - $ poky-qemu <qemuarch> <kernel> <image> <fstype> + $ poky-qemu <qemuarch> <kernel> <filesystem_image> Where: <qemuarch> is a string representing the target architecture: qemux86, qemux86-64, qemuppc, qemumips, or qemuarm. - <kernel> is the architecture-specific kernel. + <kernel> is the architecture-specific kernel. - <image> is the .ext3 filesystem image. + <filesystem_image> is the .ext3 filesystem image. - <fstype> is the filesystem type. @@ -486,8 +486,8 @@ - $ source /opt/poky/environment-setup-i586-poky-linux - $ poky-qemu qemui586 zImage-2.6.34-qemux86-0.9 yocto-image-sdk-qemux86-0.9.rootfs.ext3 ext3 + $ source /opt/poky/environment-setup-i686-poky-linux + $ poky-qemu qemux86 zImage-2.6.34-qemux86-1.0.bin yocto-image-sdk-qemux86-1.0.rootfs.ext3