summaryrefslogtreecommitdiffstats
path: root/documentation/dev-manual/dev-manual-model.xml
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2012-01-06 16:25:30 -0600
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-01-30 16:05:51 +0000
commit2ca5c8c03e3a039129e59905cffe0a7ddb94c3c8 (patch)
treedd82137c33403107273f334221d91ab4ae5b14ed /documentation/dev-manual/dev-manual-model.xml
parentfa056279ea9325ecfcdc8daf9efd486c6dd91555 (diff)
downloadpoky-2ca5c8c03e3a039129e59905cffe0a7ddb94c3c8.tar.gz
documentation/bsp-guide: Updates for 1.1.1 Release
Decision made to treat every release like a major release. This caused a scrub through the manual for the string "1.1" and "6.0" and changed to "1.1.1" and "6.0.1". Also the release date changed to 17 February. (From yocto-docs rev: 8438b152ba13dab079b3918fecc418be5ddc19c0) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/dev-manual/dev-manual-model.xml')
-rw-r--r--documentation/dev-manual/dev-manual-model.xml12
1 files changed, 6 insertions, 6 deletions
diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml
index bb36fd2bd6..9735cfb9f4 100644
--- a/documentation/dev-manual/dev-manual-model.xml
+++ b/documentation/dev-manual/dev-manual-model.xml
@@ -553,12 +553,12 @@ WRITER NOTE: The areas to get the kernel and root filesystem are located in the
553 (QEMU or real hardware), the area you get the image from differs. 553 (QEMU or real hardware), the area you get the image from differs.
554 <itemizedlist> 554 <itemizedlist>
555 <listitem><para>Download the image from 555 <listitem><para>Download the image from
556 <ulink url='http://www.yoctoproject.org/downloads/yocto-1.1/machines/'> 556 <ulink url='http://www.yoctoproject.org/downloads/yocto-1.1.1/machines/'>
557 <filename>machines</filename></ulink> if your target architecture is supported 557 <filename>machines</filename></ulink> if your target architecture is supported
558 and you are going to develop and test your application on actual hardware. 558 and you are going to develop and test your application on actual hardware.
559 </para></listitem> 559 </para></listitem>
560 <listitem><para>Download the image from the 560 <listitem><para>Download the image from the
561 <ulink url='http://www.yoctoproject.org/downloads/yocto-1.1/machines/qemu/'> 561 <ulink url='http://www.yoctoproject.org/downloads/yocto-1.1.1/machines/qemu/'>
562 <filename>machines/qemu</filename></ulink> if your target architecture is supported 562 <filename>machines/qemu</filename></ulink> if your target architecture is supported
563 and you are going to develop and test your application using the QEMU 563 and you are going to develop and test your application using the QEMU
564 emulator.</para></listitem> 564 emulator.</para></listitem>
@@ -630,14 +630,14 @@ WRITER NOTE: The areas to get the kernel and root filesystem are located in the
630 <orderedlist> 630 <orderedlist>
631 <listitem><para><emphasis>Install the cross-development toolchain for your target hardware:</emphasis> 631 <listitem><para><emphasis>Install the cross-development toolchain for your target hardware:</emphasis>
632 For information on how to install the toolchain, see the 632 For information on how to install the toolchain, see the
633 "<ulink url='http://www.yoctoproject/docs/1.1/adt-manual/adt-manual.html#using-an-existing-toolchain-tarball'>Using a Cross-Toolchain Tarball</ulink>" section in 633 "<ulink url='http://www.yoctoproject/docs/1.1.1/adt-manual/adt-manual.html#using-an-existing-toolchain-tarball'>Using a Cross-Toolchain Tarball</ulink>" section in
634 <ulink url='http://www.yoctoproject/docs/1.1/adt-manual/adt-manual.html'>The Yocto Project 634 <ulink url='http://www.yoctoproject/docs/1.1.1/adt-manual/adt-manual.html'>The Yocto Project
635 Application Development (ADT) User's Manual</ulink>.</para></listitem> 635 Application Development (ADT) User's Manual</ulink>.</para></listitem>
636 <listitem><para><emphasis>Download the Target Image:</emphasis> The Yocto Project supports 636 <listitem><para><emphasis>Download the Target Image:</emphasis> The Yocto Project supports
637 several target architectures and has many pre-built kernel images and root filesystem 637 several target architectures and has many pre-built kernel images and root filesystem
638 images.</para> 638 images.</para>
639 <para>If you are going to develop your application on hardware, go to the 639 <para>If you are going to develop your application on hardware, go to the
640 <ulink url='http://www.yoctoproject.org/downloads/yocto-1.1/machines/'> 640 <ulink url='http://www.yoctoproject.org/downloads/yocto-1.1.1/machines/'>
641 <filename>machines</filename></ulink> download area and choose a target machine area 641 <filename>machines</filename></ulink> download area and choose a target machine area
642 from which to download the kernel image and root filesystem. 642 from which to download the kernel image and root filesystem.
643 This download area could have several files in it that support development using 643 This download area could have several files in it that support development using
@@ -647,7 +647,7 @@ WRITER NOTE: The areas to get the kernel and root filesystem are located in the
647 Be sure to get the files you need for your particular development process.</para> 647 Be sure to get the files you need for your particular development process.</para>
648 <para>If you are going to develop your application and then run and test it using the QEMU 648 <para>If you are going to develop your application and then run and test it using the QEMU
649 emulator, go to the 649 emulator, go to the
650 <ulink url='http://www.yoctoproject.org/downloads/yocto-1.1/machines/qemu/'> 650 <ulink url='http://www.yoctoproject.org/downloads/yocto-1.1.1/machines/qemu/'>
651 <filename>machines/qemu</filename></ulink> download area. 651 <filename>machines/qemu</filename></ulink> download area.
652 From this area, go down into the directory for your target architecture 652 From this area, go down into the directory for your target architecture
653 (e.g. <filename>qemux86_64</filename> for an 653 (e.g. <filename>qemux86_64</filename> for an