Update of original English docs

17 files changed, 100 insertions, 64 deletions

diff --git a/fi/boot-installer/mips.xml b/fi/boot-installer/mips.xml
index f237aa957..f628be2c9 100644
--- a/fi/boot-installer/mips.xml
+++ b/fi/boot-installer/mips.xml
@@ -1,11 +1,11 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 24663 untranslated -->
+<!-- original version: 35613 untranslated -->
 
 
   <sect2 arch="mips" id="boot-tftp"><title>Booting with TFTP</title>
 
    <sect3>
-   <title>SGI Indys TFTP Booting</title>
+   <title>SGI TFTP Booting</title>
 <para>
 
 After entering the command monitor use
@@ -14,7 +14,7 @@ After entering the command monitor use
 bootp():
 </screen></informalexample>
 
-on SGI Indys to boot linux and to begin installation of the Debian
+on SGI machines to boot linux and to begin installation of the Debian
 Software.  In order to make this
 work you may have to unset the <envar>netaddr</envar> environment
 variable. Type
@@ -29,10 +29,10 @@ in the command monitor to do this.
   </sect3>
 
    <sect3>
-   <title>Broadcom BCM91250A TFTP Booting</title>
+   <title>Broadcom BCM91250A and BCM91480B TFTP Booting</title>
 <para>
 
-On the Broadcom BCM91250A evaluation board, you have to load the SiByl boot
+On the Broadcom BCM91250A and BCM91480B evaluation boards, you have to load the SiByl boot
 loader via TFTP which will then load and start the Debian installer.  In
 most cases, you will first obtain an IP address via DHCP but it is also
 possible to configure a static address.  In order to use DHCP, you can
@@ -60,10 +60,10 @@ command, the installer will be loaded automatically.
   <sect2 arch="mips"><title>Boot Parameters</title>
 
    <sect3>
-   <title>SGI Indys TFTP Booting</title>
+   <title>SGI TFTP Booting</title>
 <para>
 
-On SGI Indys you can append boot parameters to the
+On SGI machines you can append boot parameters to the
 <command>bootp():</command> command in the command monitor.
 
 </para><para>
@@ -86,7 +86,7 @@ bootp(): append="root=/dev/sda1"
   </sect3>
 
    <sect3>
-   <title>Broadcom BCM91250A TFTP Booting</title>
+   <title>Broadcom BCM91250A and BCM91480B TFTP Booting</title>
 <para>
 
 You cannot pass any boot parameters directly from the CFE prompt.  Instead,
diff --git a/fi/boot-installer/mipsel.xml b/fi/boot-installer/mipsel.xml
index a059ba7ce..69245e3fd 100644
--- a/fi/boot-installer/mipsel.xml
+++ b/fi/boot-installer/mipsel.xml
@@ -1,5 +1,5 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 35328 untranslated -->
+<!-- original version: 35612 untranslated -->
 
   <sect2 arch="mipsel" id="boot-tftp"><title>Booting with TFTP</title>
 
@@ -39,10 +39,10 @@ they have no serial port.
 
    <sect3>
 <!-- Note to translators: this is the same section as in mips.xml -->
-   <title>Broadcom BCM91250A TFTP Booting</title>
+   <title>Broadcom BCM91250A and BCM91480B TFTP Booting</title>
 <para>
 
-On the Broadcom BCM91250A evaluation board, you have to load the SiByl boot
+On the Broadcom BCM91250A and BCM91480B evaluation boards, you have to load the SiByl boot
 loader via TFTP which will then load and start the Debian installer.  In
 most cases, you will first obtain an IP address via DHCP but it is also
 possible to configure a static address.  In order to use DHCP, you can
@@ -82,7 +82,7 @@ add your parameters to the <replaceable>args</replaceable> variable.
 
    <sect3>
 <!-- Note to translators: this is the same section as in mips.xml -->
-   <title>Broadcom BCM91250A TFTP Booting</title>
+   <title>Broadcom BCM91250A and BCM91480B TFTP Booting</title>
 <para>
 
 You cannot pass any boot parameters directly from the CFE prompt.  Instead,
diff --git a/fi/hardware/hardware-supported.xml b/fi/hardware/hardware-supported.xml
index d1c337635..34698abae 100644
--- a/fi/hardware/hardware-supported.xml
+++ b/fi/hardware/hardware-supported.xml
@@ -1,5 +1,5 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 35330 untranslated -->
+<!-- original version: 35613 untranslated -->
 
  <sect1 id="hardware-supported">
  <title>Supported Hardware</title>
@@ -137,19 +137,25 @@ variations of each architecture known as <quote>flavors</quote>.
 </row>
 
 <row>
-  <entry morerows="2">MIPS (big endian)</entry>
+  <entry morerows="4">MIPS (big endian)</entry>
   <entry morerows="2">mips</entry>
-  <entry morerows="1">SGI Indy/Indigo 2</entry>
+  <entry morerows="1">SGI IP22 (Indy/Indigo 2)</entry>
   <entry>r4k-ip22</entry>
 </row><row>
   <entry>r5k-ip22</entry>
 </row><row>
+  <entry>SGI IP32 (O2)</entry>
+  <entry>r5k-ip32</entry>
+</row><row>
   <entry>Broadcom BCM91250A (SWARM)</entry>
   <entry>sb1-bcm91250a</entry>
+</row><row>
+  <entry>Broadcom BCM91480B (BigSur)</entry>
+  <entry>sb1a-bcm91480b</entry>
 </row>
 
 <row>
-  <entry morerows="3">MIPS (little endian)</entry>
+  <entry morerows="4">MIPS (little endian)</entry>
   <entry morerows="3">mipsel</entry>
   <entry>Cobalt</entry>
   <entry>cobalt</entry>
@@ -161,6 +167,9 @@ variations of each architecture known as <quote>flavors</quote>.
 </row><row>
   <entry>Broadcom BCM91250A (SWARM)</entry>
   <entry>sb1-bcm91250a</entry>
+</row><row>
+  <entry>Broadcom BCM91480B (BigSur)</entry>
+  <entry>sb1a-bcm91480b</entry>
 </row>
 
 <row>
@@ -234,19 +243,20 @@ with X.Org version &x11ver;.
 
 </para><para arch="mips">
 
-The X.Org X11 window system is only supported on the SGI Indy.  The
-Broadcom BCM91250A evaluation board has standard 3.3v PCI slots and supports
-VGA emulation or Linux framebuffer on a selected range of graphics cards.
-A <ulink url="&url-bcm91250a-hardware;">compatibility listing</ulink> for
-the BCM91250A is available.
+<!-- FIXME: mention explicit graphics chips and not system names -->
+The X.Org X11 window system is only supported on the SGI Indy and the O2.  The
+Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI
+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 evaluaton boards is available.
 
 </para><para arch="mipsel">
 
 The X.Org X11 window system is supported on some DECstation models.  The
-Broadcom BCM91250A evaluation board has standard 3.3v PCI slots and supports
-VGA emulation or Linux framebuffer on a selected range of graphics cards.
-A <ulink url="&url-bcm91250a-hardware;">compatibility listing</ulink> for
-the BCM91250A is available.
+Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI
+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 evaluaton boards is available.
 
 </para>
 
diff --git a/fi/hardware/installation-media.xml b/fi/hardware/installation-media.xml
index d9b182897..b80060bf7 100644
--- a/fi/hardware/installation-media.xml
+++ b/fi/hardware/installation-media.xml
@@ -1,5 +1,5 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 28997 untranslated -->
+<!-- original version: 35612 untranslated -->
 
  <sect1 id="installation-media">
  <title>Installation Media</title>
@@ -90,7 +90,9 @@ capability. If your CD-ROM drive has a jumper labeled
 To start the install, simply choose the <quote>System installation</quote>
 entry in the firmware.  The Broadcom BCM91250A supports standard IDE devices,
 including CD-ROM drives, but CD images for this platform are currently not
-provided because the firmware doesn't recognize CD drives.
+provided because the firmware doesn't recognize CD drives.  In order to
+install Debian on an Broadcom BCM91480B evaluation board, you need an PCI
+IDE, SATA or SCSI card.
 
 </para><para arch="mipsel">
 
diff --git a/fi/hardware/supported-peripherals.xml b/fi/hardware/supported-peripherals.xml
index f3ab5db99..8792dca6d 100644
--- a/fi/hardware/supported-peripherals.xml
+++ b/fi/hardware/supported-peripherals.xml
@@ -1,5 +1,5 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 29467 untranslated -->
+<!-- original version: 35612 untranslated -->
 
  <sect1 id="supported-peripherals">
  <title>Peripherals and Other Hardware</title>
@@ -30,12 +30,14 @@ DASD or over the network using NFS, HTTP or FTP.
 </para><para arch="mips">
 
 The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64
-bit PCI slots as well as USB connectors.
+bit PCI slots as well as USB connectors.  The Broadcom BCM91480B evaluation
+board features four 64 bit PCI slots.
 
 </para><para arch="mipsel">
 
 The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64
-bit PCI slots as well as USB connectors.  The Cobalt RaQ has no support for
+bit PCI slots as well as USB connectors.  The Broadcom BCM91480B evaluation
+board features four 64 bit PCI slots.  The Cobalt RaQ has no support for
 additional devices but the Qube has one PCI slot.
 
 </para>
diff --git a/fi/hardware/supported/mips.xml b/fi/hardware/supported/mips.xml
index 9dd0e3716..f07639933 100644
--- a/fi/hardware/supported/mips.xml
+++ b/fi/hardware/supported/mips.xml
@@ -1,11 +1,11 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 35330 untranslated -->
+<!-- original version: 35613 untranslated -->
 
 
   <sect2 arch="mips"><title>CPU, Main Boards, and Video Support</title>
 <para>
 
-Debian on &arch-title; currently supports two subarchitectures:
+Debian on &arch-title; supports the following platforms:
 
 <itemizedlist>
 <listitem><para>
@@ -17,8 +17,19 @@ refers to the SGI Indy, the Indigo 2 and Challenge S are meant as well.
 </para></listitem>
 <listitem><para>
 
-Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from
-Broadcom based on their SiByte processor family.
+SGI IP32: this platform is generally known as SGI O2.
+
+</para></listitem>
+<listitem><para>
+
+Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board
+from Broadcom based on the dual-core SB1 1250 CPU.
+
+</para></listitem>
+<listitem><para>
+
+Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board
+from Broadcom based on the quad-core SB1A 1480 CPU.
 
 </para></listitem>
 </itemizedlist>
@@ -37,8 +48,11 @@ debian-&arch-listname; mailing list</ulink>.
 
 On SGI IP22, SGI Indy, Indigo 2 and Challenge S with R4000, R4400, R4600 and R5000
 processors are supported by the Debian installation system on big endian
-MIPS.  The Broadcom BCM91250A evaluation board comes with an SB1250 chip with
-two SB-1 cores which are supported in SMP mode by this installer.
+MIPS.  On SGI IP32, currently only systems based on the R5000 are supported.
+The Broadcom BCM91250A evaluation board comes with an SB1 1250 chip with
+two cores which are supported in SMP mode by this installer.  Similarly,
+the BCM91480B evaluation board contains an SB1A 1480 chip with four cores
+which are supported in SMP mode.
 
 </para><para>
 
diff --git a/fi/hardware/supported/mipsel.xml b/fi/hardware/supported/mipsel.xml
index 823f18eb9..97bfa182f 100644
--- a/fi/hardware/supported/mipsel.xml
+++ b/fi/hardware/supported/mipsel.xml
@@ -1,11 +1,11 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 35330 untranslated -->
+<!-- original version: 35612 untranslated -->
 
 
   <sect2 arch="mipsel"><title>CPU, Main Boards, and Video Support</title>
 <para>
 
-Debian on &arch-title; currently supports three subarchitectures:
+Debian on &arch-title; supports the following platforms:
 
 <itemizedlist>
 <listitem><para>
@@ -22,8 +22,14 @@ Microserver.
 </para></listitem>
 <listitem><para>
 
-Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from
-Broadcom based on their SiByte processor family.
+Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board
+from Broadcom based on the dual-core SB1 1250 CPU.
+
+</para></listitem>
+<listitem><para>
+
+Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board
+from Broadcom based on the quad-core SB1A 1480 CPU.
 
 </para></listitem>
 </itemizedlist>
@@ -104,8 +110,10 @@ SSH.
 
 </para><para>
 
-The Broadcom BCM91250A evaluation board comes with an SB1250 chip with two
-SB-1 cores which are supported in SMP mode by this installer.
+The Broadcom BCM91250A evaluation board comes with an SB1 1250 chip with
+two cores which are supported in SMP mode by this installer.  Similarly,
+the BCM91480B evaluation board contains an SB1A 1480 chip with four cores
+which are supported in SMP mode.
 
 </para>
    </sect3>
@@ -144,7 +152,7 @@ bits per second).
 
 </para><para>
 
-Both Cobalt and Broadcom BCM91250A use 115200 bps.
+Both Cobalt and Broadcom BCM91250A/BCM91480B use 115200 bps.
 
 </para>
    </sect3>
diff --git a/fi/install-methods/install-tftp.xml b/fi/install-methods/install-tftp.xml
index b3f577937..5f4291999 100644
--- a/fi/install-methods/install-tftp.xml
+++ b/fi/install-methods/install-tftp.xml
@@ -1,5 +1,5 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 31138 untranslated -->
+<!-- original version: 35613 untranslated -->
 
  <sect1 condition="supports-tftp" id="install-tftp">
  <title>Preparing Files for TFTP Net Booting</title>
@@ -125,7 +125,7 @@ server:
 # echo 1 &gt; /proc/sys/net/ipv4/ip_no_pmtu_disc
 </screen></informalexample>
 
-to turn off Path MTU discovery, otherwise the Indy's PROM can't
+to turn off Path MTU discovery, otherwise the SGI's PROM can't
 download the kernel. Furthermore, make sure TFTP packets are sent from
 a source port no greater than 32767, or the download will stall after
 the first packet.  Again, it's Linux 2.4.X tripping this bug in the
@@ -308,10 +308,10 @@ for additional system-specific configuration information.
    </sect3>
 
    <sect3 arch="mips">
-   <title>SGI Indys TFTP Booting</title>
+   <title>SGI TFTP Booting</title>
 <para>
 
-On SGI Indys you can rely on the <command>bootpd</command> to supply
+On SGI machines you can rely on the <command>bootpd</command> to supply
 the name of the TFTP file. It is given either as the
 <userinput>bf=</userinput> in <filename>/etc/bootptab</filename> or as
 the <userinput>filename=</userinput> option in
@@ -321,7 +321,7 @@ the <userinput>filename=</userinput> option in
    </sect3>
 
    <sect3 arch="mips">
-   <title>Broadcom BCM91250A TFTP Booting</title>
+   <title>Broadcom BCM91250A and BCM91480B TFTP Booting</title>
 <para>
 
 You don't have to configure DHCP in a special way because you'll pass the
diff --git a/fi/install-methods/tftp/bootp.xml b/fi/install-methods/tftp/bootp.xml
index b6683f0ad..51c33ed7f 100644
--- a/fi/install-methods/tftp/bootp.xml
+++ b/fi/install-methods/tftp/bootp.xml
@@ -1,5 +1,5 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 28997 untranslated -->
+<!-- original version: 35613 untranslated -->
 
 
   <sect2 condition="supports-bootp" id="tftp-bootp">
@@ -50,7 +50,7 @@ option specifies the file a client should retrieve via TFTP; see
 <xref linkend="tftp-images"/> for more details.
 
 <phrase arch="mips">
-On SGI Indys you can just enter the command monitor and type
+On SGI machines you can just enter the command monitor and type
 <userinput>printenv</userinput>.  The value of the
 <userinput>eaddr</userinput> variable is the machine's MAC address.
 </phrase>
diff --git a/fi/partitioning/partition/hppa.xml b/fi/partitioning/partition/hppa.xml
index 521a5e848..e93a8bb7f 100644
--- a/fi/partitioning/partition/hppa.xml
+++ b/fi/partitioning/partition/hppa.xml
@@ -1,5 +1,5 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 28997 untranslated -->
+<!-- original version: 35595 untranslated -->
 
 
   <sect2 arch="hppa"><title>Partitioning for &arch-title;</title>
@@ -15,8 +15,8 @@ within the first 2GB of the disk.  Alternatively you can create a small
 ext2 partition near the start of the disk and mount that on
 <filename>/boot</filename>, since that is the directory where the Linux
 kernel(s) will be stored.  <filename>/boot</filename> needs to be big enough
-to hold whatever kernels you might wish load; 8&ndash;16MB is generally
-sufficient.
+to hold whatever kernels (and backups) you might wish to load; 25&ndash;50MB
+is generally sufficient.
 
 </para>
   </sect2>
diff --git a/fi/partitioning/partition/i386.xml b/fi/partitioning/partition/i386.xml
index fced09dca..c7864c635 100644
--- a/fi/partitioning/partition/i386.xml
+++ b/fi/partitioning/partition/i386.xml
@@ -1,5 +1,5 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 31618 untranslated -->
+<!-- original version: 35590 untranslated -->
 
 
   <sect2 arch="i386"><title>Partitioning for &arch-title;</title>
@@ -80,7 +80,7 @@ within the <emphasis>translated</emphasis> representation of the
 
 </para><para>
 
-The recommended way of accomplishing this is to create a small (5&ndash;10MB
+The recommended way of accomplishing this is to create a small (25&ndash;50MB
 should suffice) partition at the beginning of the disk to be used as
 the boot partition, and then create whatever other partitions you wish
 to have, in the remaining area.  This boot partition
diff --git a/fi/partitioning/partition/mips.xml b/fi/partitioning/partition/mips.xml
index fa135ab9b..edd4d7176 100644
--- a/fi/partitioning/partition/mips.xml
+++ b/fi/partitioning/partition/mips.xml
@@ -1,13 +1,13 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 28672 untranslated -->
+<!-- original version: 35613 untranslated -->
 
 
   <sect2 arch="mips"><title>Partitioning for &arch-title;</title>
 <para>
 
-SGI Indys require an SGI disk label in order to make the system bootable
+SGI machines require an SGI disk label in order to make the system bootable
 from hard disk. It can be created in the fdisk expert menu. The thereby
-created volume header(partition number 9) should be at least 3MB large.
+created volume header (partition number 9) should be at least 3MB large.
 If the volume header created is too small, you can simply delete
 partition number 9 and re-add it with a different size. Note that the
 volume header must start at sector 0.
diff --git a/fi/using-d-i/modules/clock-setup.xml b/fi/using-d-i/modules/clock-setup.xml
index 864b594a8..9c3191536 100644
--- a/fi/using-d-i/modules/clock-setup.xml
+++ b/fi/using-d-i/modules/clock-setup.xml
@@ -1,5 +1,5 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 33814 untranslated -->
+<!-- original version: 35518 untranslated -->
 
    <sect3 id="clock-setup">
    <title>Configuring the Clock</title>
diff --git a/fi/using-d-i/modules/mips/arcboot-installer.xml b/fi/using-d-i/modules/mips/arcboot-installer.xml
index 13eba925e..2e522562e 100644
--- a/fi/using-d-i/modules/mips/arcboot-installer.xml
+++ b/fi/using-d-i/modules/mips/arcboot-installer.xml
@@ -1,11 +1,11 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 24663 untranslated -->
+<!-- original version: 35613 untranslated -->
 
   <sect3 arch="mips">
   <title><command>arcboot</command>-installer</title>
 <para>
 
-The boot loader on SGI Indys is <command>arcboot</command>.
+The boot loader on SGI machines is <command>arcboot</command>.
 It has to be installed on the same hard disk as the kernel (this is done
 automatically by the installer). Arcboot supports different configurations
 which are set up in <filename>/etc/arcboot.conf</filename>. Each
diff --git a/fi/using-d-i/modules/pkgsel.xml b/fi/using-d-i/modules/pkgsel.xml
index c1796aa44..f8bee53c0 100644
--- a/fi/using-d-i/modules/pkgsel.xml
+++ b/fi/using-d-i/modules/pkgsel.xml
@@ -1,5 +1,5 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 33814 untranslated -->
+<!-- original version: 35518 untranslated -->
 
    <sect3 id="pkgsel">
    <title>Selecting and Installing Software</title>
diff --git a/fi/using-d-i/modules/tzsetup.xml b/fi/using-d-i/modules/tzsetup.xml
index 6dcba28b1..16cd7cdd2 100644
--- a/fi/using-d-i/modules/tzsetup.xml
+++ b/fi/using-d-i/modules/tzsetup.xml
@@ -1,5 +1,5 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 33814 untranslated -->
+<!-- original version: 35518 untranslated -->
 
    <sect3 id="tzsetup">
    <title>Configuring Your Time Zone</title>
diff --git a/fi/using-d-i/modules/user-setup.xml b/fi/using-d-i/modules/user-setup.xml
index b2494caad..2f1667001 100644
--- a/fi/using-d-i/modules/user-setup.xml
+++ b/fi/using-d-i/modules/user-setup.xml
@@ -1,5 +1,5 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 33814 untranslated -->
+<!-- original version: 35518 untranslated -->
 
    <sect3 id="user-setup">
    <title>Setting Up Users And Passwords</title>