Update of original English docs

4 files changed, 103 insertions, 111 deletions

diff --git a/nl/hardware/hardware-supported.xml b/nl/hardware/hardware-supported.xml
index 9910dc1a7..73366d3b7 100644
--- a/nl/hardware/hardware-supported.xml
+++ b/nl/hardware/hardware-supported.xml
@@ -1,5 +1,5 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 43032 untranslated -->
+<!-- original version: 43529 untranslated -->
 
  <sect1 id="hardware-supported">
  <title>Supported Hardware</title>
@@ -49,7 +49,7 @@ variations of each architecture known as <quote>flavors</quote>.
 </row>
 
 <row>
-  <entry>AMD64 &amp; Intel EM64t</entry>
+  <entry>AMD64 &amp; Intel EM64T</entry>
   <entry>amd64</entry>
   <entry></entry>
   <entry></entry>
@@ -89,7 +89,7 @@ variations of each architecture known as <quote>flavors</quote>.
 </row>
 
 <row>
-  <entry>Intel ia64-based</entry>
+  <entry>Intel IA-64</entry>
   <entry>ia64</entry>
   <entry></entry>
   <entry></entry>
@@ -150,8 +150,8 @@ variations of each architecture known as <quote>flavors</quote>.
 </row>
 
 <row>
-  <entry morerows="3">IBM/Motorola PowerPC</entry>
-  <entry morerows="3">powerpc</entry>
+  <entry morerows="2">IBM/Motorola PowerPC</entry>
+  <entry morerows="2">powerpc</entry>
   <entry>CHRP</entry>
   <entry>chrp</entry>
 </row><row>
@@ -160,9 +160,6 @@ variations of each architecture known as <quote>flavors</quote>.
 </row><row>
   <entry>PReP</entry>
   <entry>prep</entry>
-</row><row>
-  <entry>APUS</entry>
-  <entry>apus</entry>
 </row>
 
 <row>
@@ -224,7 +221,7 @@ as well.
 &supported-s390.xml;
 &supported-sparc.xml;
 
-  <sect2 id="gfx" arch="not-s390"><title>Graphics Card</title>
+  <sect2 id="gfx" arch="not-s390"><title>Graphics Card Support</title>
 <para arch="x86">
 
 You should be using a VGA-compatible display interface for the console
@@ -259,6 +256,30 @@ slots and support VGA emulation or Linux framebuffer on a selected range
 of graphics cards.  A <ulink url="&url-bcm91250a-hardware;">compatibility
 listing</ulink> for Broadcom evaluation boards is available.
 
+</para><para arch="sparc">
+
+Most graphics options commonly found on Sparc-based machines are supported.
+X.org graphics drivers are available for sunbw2, suncg14, suncg3, suncg6,
+sunleo and suntcx framebuffers, Creator3D and Elite3D cards (sunffb driver),
+PGX24/PGX64 ATI-based video cards (ati driver), and PermediaII-based cards
+(glint driver). To use an Elite3D card with X.org you additionally need to
+install the <classname>afbinit</classname> package, and read the documentation
+included with it on how to activate the card.
+
+</para><para arch="sparc">
+
+It is not uncommon for a Sparc machine to have two graphics cards in a
+default configuration. In such a case there is a possibility that the
+Linux kernel will not direct its output to the card initially used by the
+firmware. The lack of output on the graphical console may then be mistaken
+for a hang (usually the last message seen on console is 'Booting Linux...').
+One possible solution is to physically remove one of the video cards;
+another option is to disable one of the cards using a kernel boot parameter.
+Also, if graphical output is not required or desired, serial console may be
+used as an alternative. On some systems use of serial console can be
+activated automatically by disconnecting the keyboard before booting the
+system.
+
 </para>
   </sect2>
 
@@ -277,7 +298,7 @@ with GNU/Linux, see the
   <title>Multiple Processors</title>
 <para>
 
-Multi-processor support &mdash; also called <quote>symmetric multi-processing</quote>
+Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</quote>
 or SMP &mdash; is available for this architecture.  The standard Debian
 &release; kernel image was compiled with SMP support.  This should not
 prevent installation, since the SMP kernel should boot on non-SMP systems;
@@ -300,8 +321,8 @@ section of the kernel config.
 
 <para>
 
-Multi-processor support &mdash; also called <quote>symmetric
-multi-processing</quote> or SMP &mdash; is available for this architecture.
+Multiprocessor support &mdash; also called <quote>symmetric
+multiprocessing</quote> or SMP &mdash; is available for this architecture.
 The standard Debian &release; kernel image was compiled with
 <firstterm>SMP-alternatives</firstterm> support. This means that the kernel
 will detect the number of processors (or processor cores) and will
@@ -319,8 +340,8 @@ is not compiled with SMP support.
   <title>Multiple Processors</title>
 <para>
 
-Multi-processor support &mdash; also called <quote>symmetric
-multi-processing</quote> or SMP &mdash; is available for this architecture.
+Multiprocessor support &mdash; also called <quote>symmetric
+multiprocessing</quote> or SMP &mdash; is available for this architecture.
 However, the standard Debian &release; kernel image does not support
 SMP.  This should not prevent installation, since the standard,
 non-SMP kernel should boot on SMP systems; the kernel will simply use
@@ -342,8 +363,8 @@ section of the kernel config.
   <title>Multiple Processors</title>
 <para>
 
-Multi-processor support &mdash; also called <quote>symmetric
-multi-processing</quote> or SMP &mdash; is available for this architecture,
+Multiprocessor support &mdash; also called <quote>symmetric
+multiprocessing</quote> or SMP &mdash; is available for this architecture,
 and is supported by a precompiled Debian kernel image. Depending on your
 install media, this SMP-capable kernel may or may not be installed by
 default. This should not prevent installation, since the standard,
@@ -356,6 +377,8 @@ In order to take advantage of multiple processors, you should check to see
 if a kernel package that supports SMP is installed, and if not, choose an
 appropriate kernel package.
 
+</para><para>
+
 You can also build your own customized kernel to support SMP. You can find
 a discussion of how to do this in <xref linkend="kernel-baking"/>.  At this
 time (kernel version &kernelversion;) the way you enable SMP is to select
diff --git a/nl/hardware/supported-peripherals.xml b/nl/hardware/supported-peripherals.xml
index a3c33bea6..c7af3ee08 100644
--- a/nl/hardware/supported-peripherals.xml
+++ b/nl/hardware/supported-peripherals.xml
@@ -1,5 +1,5 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 39614 untranslated -->
+<!-- original version: 43499 untranslated -->
 
  <sect1 id="supported-peripherals">
  <title>Peripherals and Other Hardware</title>
@@ -153,37 +153,4 @@ sort of hardware until it is listed as working in the
 
 </para>
 </sect2>
-
-
-  <sect2 id="Parity-RAM">
-  <title>Fake or <quote>Virtual</quote> Parity RAM</title>
-<para>
-
-If you ask for Parity RAM in a computer store, you'll probably get
-<emphasis>virtual parity</emphasis> memory modules instead of
-<emphasis>true parity</emphasis> ones. Virtual parity SIMMs can often
-(but not always) be distinguished because they only have one more chip
-than an equivalent non-parity SIMM, and that one extra chip is smaller
-than all the others. Virtual-parity SIMMs work exactly like non-parity
-memory.  They can't tell you when you have a single-bit RAM error the
-way true-parity SIMMs do in a motherboard that implements
-parity. Don't ever pay more for a virtual-parity SIMM than a
-non-parity one. Do expect to pay a little more for true-parity SIMMs,
-because you are actually buying one extra bit of memory for every 8
-bits.
-
-</para><para>
-
-If you want complete information on &arch-title; RAM issues, and what
-is the best RAM to buy, see the
-<ulink url="&url-pc-hw-faq;">PC Hardware FAQ</ulink>.
-
-</para><para arch="alpha">
-
-Most, if not all, Alpha systems require true-parity RAM.
-
-</para>
-
-  </sect2>
-
  </sect1>
diff --git a/nl/hardware/supported/i386.xml b/nl/hardware/supported/i386.xml
index 975514a48..b21c7d1ba 100644
--- a/nl/hardware/supported/i386.xml
+++ b/nl/hardware/supported/i386.xml
@@ -1,5 +1,5 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 42036 untranslated -->
+<!-- original version: 43254 untranslated -->
 
 
   <sect2 arch="i386"><title>CPU, Main Boards, and Video Support</title>
@@ -22,7 +22,7 @@ processors like the Athlon XP and Intel P4 Xeon.
 </para>
 <note><para>
 
-If your system has a 64-bit AMD64, Intel EM64t or Intel Core 2 Duo processor,
+If your system has a 64-bit AMD64, Intel EM64T or Intel Core 2 Duo processor,
 you will probably want to use the installer for the amd64 architecture instead
 of the installer for the (32-bit) i386 architecture.
 
diff --git a/nl/hardware/supported/sparc.xml b/nl/hardware/supported/sparc.xml
index d00c6b252..754a221a4 100644
--- a/nl/hardware/supported/sparc.xml
+++ b/nl/hardware/supported/sparc.xml
@@ -1,82 +1,84 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 28997 untranslated -->
+<!-- original version: 43528 untranslated -->
 
-
-  <sect2 arch="sparc" id="sparc-cpus"><title>CPU, Main Boards, and Video Support</title>
+  <sect2 arch="sparc" id="sparc-cpus">
+  <title>CPU and Main Boards Support</title>
 <para>
 
-Currently the <emphasis>&architecture;</emphasis> port supports
-several types of Sparc systems. The most common identifiers for Sparc
-systems are sun4, sun4c, sun4m, sun4d and sun4u. Currently we do not
-support very old sun4 hardware. However, the other systems are
-supported. Sun4d has been tested the least of these, so expect
-possible problems with regard to the kernel stability. Sun4c and
-Sun4m, the most common of the older Sparc hardware, includes such
-systems as SparcStation 1, 1+, IPC, IPX and the SparcStation LX, 5,
-10, and 20, respectively. The UltraSPARC class systems fall under the
-sun4u identifier, and are supported using the sun4u set of install
-images. Some systems that fall under these supported identifiers are
-known to not be supported. Known unsupported systems are the AP1000
-multicomputer and the Tadpole Sparcbook 1. See the
-<ulink url="&url-sparc-linux-faq;">Linux for SPARCProcessors FAQ</ulink>
-for complete information.
+Sparc-based hardware is divided into a number of different subarchitectures,
+identified by one of the following names: sun4, sun4c, sun4d, sun4m, sun4u
+or sun4v. The following list describes what machines they include and what
+level of support may be expected for each of them.
 
 </para>
 
-   <sect3><title>Memory Configuration</title>
-<para>
+<variablelist>
+<varlistentry>
+<term>sun4, sun4c, sun4d</term>
 
-Some older Sun workstations, notably the Sun IPX and Sun IPC have
-memory banks located at fixed locations in physical memory.  Thus if
-the banks are not filled gaps will exist in the physical memory space.
-The Linux installation requires a contiguous memory block into which
-to load the kernel and the initial RAMdisk.  If this is not available a
-<quote>Data Access Exception</quote> will result.
+<listitem><para>
 
-</para><para>
+These subarchitectures include some very old 32-bit machines, which are
+no longer supported. For a complete list please consult the
+<ulink url="http://en.wikipedia.org/wiki/SPARCstation">Wikipedia
+SPARCstation page</ulink>.
+
+</para></listitem>
+</varlistentry>
 
-Thus you must configure the memory so that the lowest memory block is
-contiguous for at least 8Mb.  In the IPX and IPC cited above, memory banks
-are mapped in at 16Mb boundaries.  In effect this means that you must have
-a sufficiently large SIMM in bank zero to hold the kernel and RAMdisk.
-In this case 4Mb is <emphasis>not</emphasis> sufficient.
+<varlistentry>
+<term>sun4m</term>
+
+<listitem><para>
+
+sun4m is the only 32-bit subarchitecture (sparc32) that is currently
+supported. The most popular machines belonging to this class are
+Sparcstation 4, 5, 10 and 20.
 
 </para><para>
 
-Example:
-In a Sun IPX you have a 16Mb SIMM and a 4Mb SIMM.  There are four
-SIMM banks (0,1,2,3). [Bank zero is that furthest away from the SBUS
-connectors]. You must therefore install the 16Mb SIMM in bank 0; it is
-then recommended to install the 4Mb SIMM in bank 2.
+Note that symmetric multiprocessing (SMP) &mdash; the ability to run
+processes on multiple processors &mdash; is not supported on this hardware,
+due to stability problems with such configurations. The available
+uniprocessor (UP) sparc32 kernel will boot fine on multiprocessor
+machines, although it will activate and use only the first CPU.
 
-</para>
-   </sect3>
+</para></listitem>
+</varlistentry>
 
-   <sect3><title>Graphics Configuration</title>
-<para>
+<varlistentry>
+<term>sun4u</term>
 
-Especially in the case of older Sun workstations, it is very common
-for there to be an onboard framebuffer which has been superseded (for
-example the bwtwo on a sun IPC), and an SBUS card containing a later
-probably accelerated buffer is then plugged in to an SBUS slot.
-Under Solaris/SunOS this causes no problems because both cards are
-initialized.
+<listitem><para>
 
-</para><para>
+This subarchitecture includes all 64-bit machines (sparc64) based on
+the UltraSparc processor and its clones. Most of the machines are well
+supported, even though for some you may experience problems booting from
+CD due to firmware or bootloader bugs (this problem may be worked around
+by using netbooting). Use the sparc64 or sparc64-smp kernel in UP and SMP
+configurations respectively.
 
-However with Linux this can cause a problem, in that the boot PROM
-monitor may display its output on this additional card; however the
-linux kernel boot messages may then be directed to the original on
-board framebuffer, leaving <emphasis>no</emphasis> error messages on
-the screen, with the machine apparently stuck loading the RAMdisk.
+</para></listitem>
+</varlistentry>
 
-</para><para>
+<varlistentry>
+<term>sun4v</term>
+
+<listitem><para>
+
+This is the newest addition to the Sparc family, which includes machines
+based on the Niagara multi-core CPUs. At the moment such CPUs are only
+available in T1000 and T2000 servers by Sun, and are well supported. Use
+the sparc64-smp kernel.
+
+</para></listitem>
+</varlistentry>
+</variablelist>
+
+<para>
 
-To avoid this problem, connect the monitor (if required) to the video
-card in the lowest numbered SBUS slot (on motherboard card counts
-as below external slots).  Alternatively it is possible to use a serial
-console.
+Note that Fujitsu's SPARC64 CPUs used in PRIMEPOWER family of servers are not
+supported due to lack of support in the Linux kernel.
 
 </para>
-   </sect3>
   </sect2>