Update the manuals to reflect the recent replacement of atom-pc with
genericx86.

Signed-off-by: Darren Hart <[email protected]>
Cc: Ross Burton <[email protected]>
Cc: Paul Eggleton <[email protected]>
Cc: Scott Rifenbark <[email protected]>
Signed-off-by: Darren Hart <[email protected]>
---
 documentation/dev-manual/dev-manual-model.xml             |  2 +-
 documentation/ref-manual/ref-variables.xml                |  2 +-
 documentation/ref-manual/technical-details.xml            |  2 +-
 presentations/automotive-linux-summit-2012/automotive.pin | 10 +++++-----
 4 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/documentation/dev-manual/dev-manual-model.xml 
b/documentation/dev-manual/dev-manual-model.xml
index a59a447..efa50b0 100644
--- a/documentation/dev-manual/dev-manual-model.xml
+++ b/documentation/dev-manual/dev-manual-model.xml
@@ -156,7 +156,7 @@
                     "<ulink url='&YOCTO_DOCS_BSP_URL;#bsp-layers'>BSP 
Layers</ulink>" section in the
                     Yocto Project Board Support Package (BSP) Developer's 
Guide.</para>
                     <note>Four BSPs exist that are part of the
-                    Yocto Project release: <filename>atom-pc</filename>, 
<filename>beagleboard</filename>,
+                    Yocto Project release: <filename>genericx86</filename>, 
<filename>beagleboard</filename>,
                     <filename>mpc8315e</filename>, and 
<filename>routerstationpro</filename>.
                     The recipes and configurations for these four BSPs are 
located and dispersed
                     within the <link linkend='source-directory'>Source 
Directory</link>.
diff --git a/documentation/ref-manual/ref-variables.xml 
b/documentation/ref-manual/ref-variables.xml
index 040c386..a9d1c1d 100644
--- a/documentation/ref-manual/ref-variables.xml
+++ b/documentation/ref-manual/ref-variables.xml
@@ -2784,7 +2784,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = 
"${INC_PR}.3"
      MACHINE ?= "qemuppc"
      MACHINE ?= "qemux86"
      MACHINE ?= "qemux86-64"
-     MACHINE ?= "atom-pc"
+     MACHINE ?= "genericx86"
      MACHINE ?= "beagleboard"
      MACHINE ?= "mpc8315e-rdb"
      MACHINE ?= "routerstationpro"
diff --git a/documentation/ref-manual/technical-details.xml 
b/documentation/ref-manual/technical-details.xml
index cad9458..db368b0 100644
--- a/documentation/ref-manual/technical-details.xml
+++ b/documentation/ref-manual/technical-details.xml
@@ -1885,7 +1885,7 @@
       DEFAULTTUNE = "x86-64-x32"
       baselib = "${@d.getVar('BASE_LIB_tune-' + (d.getVar('DEFAULTTUNE', True) 
\
          or 'INVALID'), True) or 'lib'}"
-      #MACHINE = "atom-pc"
+      #MACHINE = "genericx86"
       #DEFAULTTUNE = "core2-64-x32"
                     </literallayout></para></listitem>
                 <listitem><para>As usual, use BitBake to build an image that 
supports the x32 psABI.
diff --git a/presentations/automotive-linux-summit-2012/automotive.pin 
b/presentations/automotive-linux-summit-2012/automotive.pin
index c5292fb..e6aaaa1 100644
--- a/presentations/automotive-linux-summit-2012/automotive.pin
+++ b/presentations/automotive-linux-summit-2012/automotive.pin
@@ -187,7 +187,7 @@ $ <b>cd poky-denzil-7.0</b></tt>
  …
  #MACHINE ?= "qemuarm"
  #MACHINE ?= "qemumips"
- #MACHINE ?= "atom-pc"
+ #MACHINE ?= "genericx86"
  #MACHINE ?= "beagleboard"</tt>
 # Just a small fragment of the options available.  Defaults are all
 # reasonable and it will successfully build out of the box.
@@ -227,10 +227,10 @@ $ <b>cd poky-denzil-7.0</b></tt>
 -- [corridor.jpg] [center] [duration=33.001926]
 <tt>$ <b>ls tmp/deploy/images/</b>
 …
-core-image-minimal-atom-pc-20120918205848.hddimg
-core-image-minimal-atom-pc-20120918205848.iso
-core-image-minimal-atom-pc-20120918205848.rootfs.cpio.gz
-core-image-minimal-atom-pc-20120918205848.rootfs.ext3
+core-image-minimal-genericx86-20120918205848.hddimg
+core-image-minimal-genericx86-20120918205848.iso
+core-image-minimal-genericx86-20120918205848.rootfs.cpio.gz
+core-image-minimal-genericx86-20120918205848.rootfs.ext3
 </tt>
 # When it finishes building the results are in the deploy directory
 # Here we can see the constructed root file system as a cpio archive,
-- 
1.8.3.1

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Reply via email to