summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--documentation/adt-manual/adt-prepare.xml12
-rw-r--r--documentation/ref-manual/ref-variables.xml12
2 files changed, 13 insertions, 11 deletions
diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml
index 343b741e1b..54f48a8507 100644
--- a/documentation/adt-manual/adt-prepare.xml
+++ b/documentation/adt-manual/adt-prepare.xml
@@ -253,9 +253,9 @@
253 <para>Go into that folder and download the toolchain 253 <para>Go into that folder and download the toolchain
254 installer whose name includes the appropriate target 254 installer whose name includes the appropriate target
255 architecture. 255 architecture.
256 For example, if your host development system is an 256 For example, if your host development system is a
257 Intel-based 64-bit system and you are going to use 257 64-bit x86 system and you are going to use
258 your cross-toolchain for an Intel-based 32-bit 258 your cross-toolchain for a 32-bit x86
259 target, go into the <filename>x86_64</filename> 259 target, go into the <filename>x86_64</filename>
260 folder and download the following installer: 260 folder and download the following installer:
261 <literallayout class='monospaced'> 261 <literallayout class='monospaced'>
@@ -263,7 +263,7 @@
263 </literallayout></para></listitem> 263 </literallayout></para></listitem>
264 <listitem><para>Build your own toolchain installer. 264 <listitem><para>Build your own toolchain installer.
265 For cases where you cannot use an installer 265 For cases where you cannot use an installer
266 from the download area, you can build your as 266 from the download area, you can build your own as
267 described in the 267 described in the
268 "<link linkend='optionally-building-a-toolchain-installer'>Optionally Building a Toolchain Installer</link>" 268 "<link linkend='optionally-building-a-toolchain-installer'>Optionally Building a Toolchain Installer</link>"
269 section.</para></listitem> 269 section.</para></listitem>
@@ -273,8 +273,8 @@
273 You must change the permissions on the toolchain installer 273 You must change the permissions on the toolchain installer
274 script so that it is executable.</para> 274 script so that it is executable.</para>
275 <para>The following command shows how to run the installer 275 <para>The following command shows how to run the installer
276 given a toolchain tarball for a 64-bit development host 276 given a toolchain tarball for a 64-bit x86 development host
277 system and a 32-bit target architecture. 277 system and a 32-bit x86 target architecture.
278 The example assumes the toolchain installer is located 278 The example assumes the toolchain installer is located
279 in <filename>~/Downloads/</filename>. 279 in <filename>~/Downloads/</filename>.
280 <literallayout class='monospaced'> 280 <literallayout class='monospaced'>
diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml
index 4b7aa866b0..25a3820712 100644
--- a/documentation/ref-manual/ref-variables.xml
+++ b/documentation/ref-manual/ref-variables.xml
@@ -1935,7 +1935,8 @@ Core layer for images cannot be removed
1935 <glossentry id='var-IMAGE_TYPES'><glossterm>IMAGE_TYPES</glossterm> 1935 <glossentry id='var-IMAGE_TYPES'><glossterm>IMAGE_TYPES</glossterm>
1936 <glossdef> 1936 <glossdef>
1937 <para> 1937 <para>
1938 Specifies the complete list of supported image types: 1938 Specifies the complete list of supported image types
1939 by default:
1939 <literallayout class='monospaced'> 1940 <literallayout class='monospaced'>
1940 jffs2 1941 jffs2
1941 sum.jffs2 1942 sum.jffs2
@@ -2168,12 +2169,13 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
2168 <glossentry id='var-IPK_FEED_URIS'><glossterm>IPK_FEED_URIS</glossterm> 2169 <glossentry id='var-IPK_FEED_URIS'><glossterm>IPK_FEED_URIS</glossterm>
2169 <glossdef> 2170 <glossdef>
2170 <para> 2171 <para>
2171 Helps users set up an additional package feed area on 2172 When the IPK backend is in use and package management
2172 a server for packages you might want to install on a 2173 is enabled on the target, you can use this variable to
2173 target that is running an image. 2174 set up <filename>opkg</filename> in the target image
2175 to point to package feeds on a nominated server.
2174 Once the feed is established, you can perform 2176 Once the feed is established, you can perform
2175 installations or upgrades using the package manager 2177 installations or upgrades using the package manager
2176 at runtime (e.g. <filename>opkg</filename>). 2178 at runtime.
2177 </para> 2179 </para>
2178 </glossdef> 2180 </glossdef>
2179 </glossentry> 2181 </glossentry>