summaryrefslogtreecommitdiffstats
path: root/documentation/adt-manual
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2011-09-13 06:36:29 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-09-13 21:48:37 +0100
commitdab5ffcf465232f77f1155905d9757b8c00da3b0 (patch)
tree9f5db04aa71f0faabe04399f15f2bd6d0c00c329 /documentation/adt-manual
parenta7d58b50b3fb51addfde727a147e0f0abad82136 (diff)
downloadpoky-dab5ffcf465232f77f1155905d9757b8c00da3b0.tar.gz
documentation/adt-manual/adt-prepare.xml: Added note about sato
I discovered that in order to remotely deploy and debug an image from Eclipse you have to have a Sato image. I added text to the note about getting or building the image specifying that requirement. (From yocto-docs rev: 060de7f6082bc3dbfa0f7d4e25b2933f15a61fc0) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/adt-manual')
-rw-r--r--documentation/adt-manual/adt-prepare.xml18
1 files changed, 12 insertions, 6 deletions
diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml
index 93e013c60c..65ca6345ff 100644
--- a/documentation/adt-manual/adt-prepare.xml
+++ b/documentation/adt-manual/adt-prepare.xml
@@ -367,21 +367,27 @@
367 <para> 367 <para>
368 You will need to have a kernel and filesystem image to boot using your 368 You will need to have a kernel and filesystem image to boot using your
369 hardware or the QEMU emulator. 369 hardware or the QEMU emulator.
370 That means you either have to build them or know where to get them. 370 That means you either have to build them or know where to get them.
371 You can find lots of details on how to get or build images and kernels for your 371 You can find a quick example of how to build an image in the
372 architecture in the
373 <ulink url='http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html#building-image'> 372 <ulink url='http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html#building-image'>
374 Building an Image</ulink> section of the 373 Building an Image</ulink> section of
375 <ulink url='http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html'> 374 <ulink url='http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html'>
376 The Yocto Project Quick Start</ulink>. 375 The Yocto Project Quick Start</ulink>.
377 <note> 376 <note><para>
378 The Yocto Project provides basic kernels and filesystem images for several 377 The Yocto Project provides basic kernels and filesystem images for several
379 architectures (<filename>x86</filename>, <filename>x86-64</filename>, 378 architectures (<filename>x86</filename>, <filename>x86-64</filename>,
380 <filename>mips</filename>, <filename>powerpc</filename>, and <filename>arm</filename>) 379 <filename>mips</filename>, <filename>powerpc</filename>, and <filename>arm</filename>)
381 that you can use unaltered in the QEMU emulator. 380 that you can use unaltered in the QEMU emulator.
382 These kernels and filesystem images reside in the Yocto Project release 381 These kernels and filesystem images reside in the Yocto Project release
383 area - <ulink url='http://autobuilder.yoctoproject.org/downloads/yocto-1.1/machines/'></ulink> 382 area - <ulink url='http://autobuilder.yoctoproject.org/downloads/yocto-1.1/machines/'></ulink>
384 and are ideal for experimentation within Yocto Project. 383 and are ideal for experimentation within Yocto Project.</para>
384 <para>If you plan on remotely deploying and debugging your application from within the
385 Eclipse IDE, you must have an image that supports Sato.
386 For information on the image types you can build using the Yocto Project, see
387 <ulink url='http://www.yoctoproject.org/docs/1.1/poky-ref-manual/poky-ref-manual.html#ref-images'>
388 Reference: Images</ulink> in
389 <ulink url='http://www.yoctoproject.org/docs/1.1/poky-ref-manual/poky-ref-manual.html'>
390 The Yocto Project Reference Manual</ulink>.</para>
385 </note> 391 </note>
386 </para> 392 </para>
387</section> 393</section>