From 74e594185d4421e862806c29fc0519dd337f1229 Mon Sep 17 00:00:00 2001 From: Frans Pop Date: Sun, 19 Mar 2006 13:43:49 +0000 Subject: Update of original English docs --- fi/boot-installer/mips.xml | 16 +++++------ fi/boot-installer/mipsel.xml | 8 +++--- fi/hardware/hardware-supported.xml | 36 ++++++++++++++++--------- fi/hardware/installation-media.xml | 6 +++-- fi/hardware/supported-peripherals.xml | 8 +++--- fi/hardware/supported/mips.xml | 26 +++++++++++++----- fi/hardware/supported/mipsel.xml | 22 ++++++++++----- fi/install-methods/install-tftp.xml | 10 +++---- fi/install-methods/tftp/bootp.xml | 4 +-- fi/partitioning/partition/hppa.xml | 6 ++--- fi/partitioning/partition/i386.xml | 4 +-- fi/partitioning/partition/mips.xml | 6 ++--- fi/using-d-i/modules/clock-setup.xml | 2 +- fi/using-d-i/modules/mips/arcboot-installer.xml | 4 +-- fi/using-d-i/modules/pkgsel.xml | 2 +- fi/using-d-i/modules/tzsetup.xml | 2 +- fi/using-d-i/modules/user-setup.xml | 2 +- nl/boot-installer/mips.xml | 16 +++++------ nl/boot-installer/mipsel.xml | 8 +++--- nl/hardware/hardware-supported.xml | 36 ++++++++++++++++--------- nl/hardware/installation-media.xml | 6 +++-- nl/hardware/supported-peripherals.xml | 8 +++--- nl/hardware/supported/mips.xml | 26 +++++++++++++----- nl/hardware/supported/mipsel.xml | 22 ++++++++++----- nl/install-methods/install-tftp.xml | 10 +++---- nl/install-methods/tftp/bootp.xml | 4 +-- nl/partitioning/partition/hppa.xml | 6 ++--- nl/partitioning/partition/i386.xml | 4 +-- nl/partitioning/partition/mips.xml | 6 ++--- nl/using-d-i/modules/clock-setup.xml | 2 +- nl/using-d-i/modules/mips/arcboot-installer.xml | 4 +-- nl/using-d-i/modules/pkgsel.xml | 2 +- nl/using-d-i/modules/tzsetup.xml | 2 +- nl/using-d-i/modules/user-setup.xml | 2 +- 34 files changed, 200 insertions(+), 128 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 @@ - + Booting with TFTP - SGI Indys TFTP Booting + SGI TFTP Booting After entering the command monitor use @@ -14,7 +14,7 @@ After entering the command monitor use bootp(): -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 netaddr environment variable. Type @@ -29,10 +29,10 @@ in the command monitor to do this. - Broadcom BCM91250A TFTP Booting + Broadcom BCM91250A and BCM91480B TFTP Booting -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. Boot Parameters - SGI Indys TFTP Booting + SGI TFTP Booting -On SGI Indys you can append boot parameters to the +On SGI machines you can append boot parameters to the bootp(): command in the command monitor. @@ -86,7 +86,7 @@ bootp(): append="root=/dev/sda1" - Broadcom BCM91250A TFTP Booting + Broadcom BCM91250A and BCM91480B TFTP Booting 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 @@ - + Booting with TFTP @@ -39,10 +39,10 @@ they have no serial port. - Broadcom BCM91250A TFTP Booting + Broadcom BCM91250A and BCM91480B TFTP Booting -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 args variable. - Broadcom BCM91250A TFTP Booting + Broadcom BCM91250A and BCM91480B TFTP Booting 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 @@ - + Supported Hardware @@ -137,19 +137,25 @@ variations of each architecture known as flavors. - MIPS (big endian) + MIPS (big endian) mips - SGI Indy/Indigo 2 + SGI IP22 (Indy/Indigo 2) r4k-ip22 r5k-ip22 + + SGI IP32 (O2) + r5k-ip32 Broadcom BCM91250A (SWARM) sb1-bcm91250a + + Broadcom BCM91480B (BigSur) + sb1a-bcm91480b - MIPS (little endian) + MIPS (little endian) mipsel Cobalt cobalt @@ -161,6 +167,9 @@ variations of each architecture known as flavors. Broadcom BCM91250A (SWARM) sb1-bcm91250a + + Broadcom BCM91480B (BigSur) + sb1a-bcm91480b @@ -234,19 +243,20 @@ with X.Org version &x11ver;. -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 compatibility listing for -the BCM91250A is available. + +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 compatibility +listing for Broadcom evaluaton boards is available. 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 compatibility listing 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 compatibility +listing for Broadcom evaluaton boards is available. 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 @@ - + Installation Media @@ -90,7 +90,9 @@ capability. If your CD-ROM drive has a jumper labeled To start the install, simply choose the System installation 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. 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 @@ - + Peripherals and Other Hardware @@ -30,12 +30,14 @@ DASD or over the network using NFS, HTTP or FTP. 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. 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. 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 @@ - + CPU, Main Boards, and Video Support -Debian on &arch-title; currently supports two subarchitectures: +Debian on &arch-title; supports the following platforms: @@ -17,8 +17,19 @@ refers to the SGI Indy, the Indigo 2 and Challenge S are meant as well. -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. + + + + +Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board +from Broadcom based on the dual-core SB1 1250 CPU. + + + + +Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board +from Broadcom based on the quad-core SB1A 1480 CPU. @@ -37,8 +48,11 @@ debian-&arch-listname; mailing list. 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. 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 @@ - + CPU, Main Boards, and Video Support -Debian on &arch-title; currently supports three subarchitectures: +Debian on &arch-title; supports the following platforms: @@ -22,8 +22,14 @@ Microserver. -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. + + + + +Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board +from Broadcom based on the quad-core SB1A 1480 CPU. @@ -104,8 +110,10 @@ SSH. -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. @@ -144,7 +152,7 @@ bits per second). -Both Cobalt and Broadcom BCM91250A use 115200 bps. +Both Cobalt and Broadcom BCM91250A/BCM91480B use 115200 bps. 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 @@ - + Preparing Files for TFTP Net Booting @@ -125,7 +125,7 @@ server: # echo 1 > /proc/sys/net/ipv4/ip_no_pmtu_disc -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. - SGI Indys TFTP Booting + SGI TFTP Booting -On SGI Indys you can rely on the bootpd to supply +On SGI machines you can rely on the bootpd to supply the name of the TFTP file. It is given either as the bf= in /etc/bootptab or as the filename= option in @@ -321,7 +321,7 @@ the filename= option in - Broadcom BCM91250A TFTP Booting + Broadcom BCM91250A and BCM91480B TFTP Booting 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 @@ - + @@ -50,7 +50,7 @@ option specifies the file a client should retrieve via TFTP; see for more details. -On SGI Indys you can just enter the command monitor and type +On SGI machines you can just enter the command monitor and type printenv. The value of the eaddr variable is the machine's MAC address. 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 @@ - + Partitioning for &arch-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 /boot, since that is the directory where the Linux kernel(s) will be stored. /boot needs to be big enough -to hold whatever kernels you might wish load; 8–16MB is generally -sufficient. +to hold whatever kernels (and backups) you might wish to load; 25–50MB +is generally sufficient. 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 @@ - + Partitioning for &arch-title; @@ -80,7 +80,7 @@ within the translated representation of the -The recommended way of accomplishing this is to create a small (5–10MB +The recommended way of accomplishing this is to create a small (25–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 @@ - + Partitioning for &arch-title; -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 @@ - + Configuring the Clock 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 @@ - + <command>arcboot</command>-installer -The boot loader on SGI Indys is arcboot. +The boot loader on SGI machines is arcboot. 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 /etc/arcboot.conf. 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 @@ - + Selecting and Installing Software 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 @@ - + Configuring Your Time Zone 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 @@ - + Setting Up Users And Passwords diff --git a/nl/boot-installer/mips.xml b/nl/boot-installer/mips.xml index f237aa957..f628be2c9 100644 --- a/nl/boot-installer/mips.xml +++ b/nl/boot-installer/mips.xml @@ -1,11 +1,11 @@ - + Booting with TFTP - SGI Indys TFTP Booting + SGI TFTP Booting After entering the command monitor use @@ -14,7 +14,7 @@ After entering the command monitor use bootp(): -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 netaddr environment variable. Type @@ -29,10 +29,10 @@ in the command monitor to do this. - Broadcom BCM91250A TFTP Booting + Broadcom BCM91250A and BCM91480B TFTP Booting -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. Boot Parameters - SGI Indys TFTP Booting + SGI TFTP Booting -On SGI Indys you can append boot parameters to the +On SGI machines you can append boot parameters to the bootp(): command in the command monitor. @@ -86,7 +86,7 @@ bootp(): append="root=/dev/sda1" - Broadcom BCM91250A TFTP Booting + Broadcom BCM91250A and BCM91480B TFTP Booting You cannot pass any boot parameters directly from the CFE prompt. Instead, diff --git a/nl/boot-installer/mipsel.xml b/nl/boot-installer/mipsel.xml index a059ba7ce..69245e3fd 100644 --- a/nl/boot-installer/mipsel.xml +++ b/nl/boot-installer/mipsel.xml @@ -1,5 +1,5 @@ - + Booting with TFTP @@ -39,10 +39,10 @@ they have no serial port. - Broadcom BCM91250A TFTP Booting + Broadcom BCM91250A and BCM91480B TFTP Booting -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 args variable. - Broadcom BCM91250A TFTP Booting + Broadcom BCM91250A and BCM91480B TFTP Booting You cannot pass any boot parameters directly from the CFE prompt. Instead, diff --git a/nl/hardware/hardware-supported.xml b/nl/hardware/hardware-supported.xml index d1c337635..34698abae 100644 --- a/nl/hardware/hardware-supported.xml +++ b/nl/hardware/hardware-supported.xml @@ -1,5 +1,5 @@ - + Supported Hardware @@ -137,19 +137,25 @@ variations of each architecture known as flavors. - MIPS (big endian) + MIPS (big endian) mips - SGI Indy/Indigo 2 + SGI IP22 (Indy/Indigo 2) r4k-ip22 r5k-ip22 + + SGI IP32 (O2) + r5k-ip32 Broadcom BCM91250A (SWARM) sb1-bcm91250a + + Broadcom BCM91480B (BigSur) + sb1a-bcm91480b - MIPS (little endian) + MIPS (little endian) mipsel Cobalt cobalt @@ -161,6 +167,9 @@ variations of each architecture known as flavors. Broadcom BCM91250A (SWARM) sb1-bcm91250a + + Broadcom BCM91480B (BigSur) + sb1a-bcm91480b @@ -234,19 +243,20 @@ with X.Org version &x11ver;. -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 compatibility listing for -the BCM91250A is available. + +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 compatibility +listing for Broadcom evaluaton boards is available. 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 compatibility listing 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 compatibility +listing for Broadcom evaluaton boards is available. diff --git a/nl/hardware/installation-media.xml b/nl/hardware/installation-media.xml index d9b182897..b80060bf7 100644 --- a/nl/hardware/installation-media.xml +++ b/nl/hardware/installation-media.xml @@ -1,5 +1,5 @@ - + Installation Media @@ -90,7 +90,9 @@ capability. If your CD-ROM drive has a jumper labeled To start the install, simply choose the System installation 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. diff --git a/nl/hardware/supported-peripherals.xml b/nl/hardware/supported-peripherals.xml index f3ab5db99..8792dca6d 100644 --- a/nl/hardware/supported-peripherals.xml +++ b/nl/hardware/supported-peripherals.xml @@ -1,5 +1,5 @@ - + Peripherals and Other Hardware @@ -30,12 +30,14 @@ DASD or over the network using NFS, HTTP or FTP. 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. 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. diff --git a/nl/hardware/supported/mips.xml b/nl/hardware/supported/mips.xml index 9dd0e3716..f07639933 100644 --- a/nl/hardware/supported/mips.xml +++ b/nl/hardware/supported/mips.xml @@ -1,11 +1,11 @@ - + CPU, Main Boards, and Video Support -Debian on &arch-title; currently supports two subarchitectures: +Debian on &arch-title; supports the following platforms: @@ -17,8 +17,19 @@ refers to the SGI Indy, the Indigo 2 and Challenge S are meant as well. -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. + + + + +Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board +from Broadcom based on the dual-core SB1 1250 CPU. + + + + +Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board +from Broadcom based on the quad-core SB1A 1480 CPU. @@ -37,8 +48,11 @@ debian-&arch-listname; mailing list. 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. diff --git a/nl/hardware/supported/mipsel.xml b/nl/hardware/supported/mipsel.xml index 823f18eb9..97bfa182f 100644 --- a/nl/hardware/supported/mipsel.xml +++ b/nl/hardware/supported/mipsel.xml @@ -1,11 +1,11 @@ - + CPU, Main Boards, and Video Support -Debian on &arch-title; currently supports three subarchitectures: +Debian on &arch-title; supports the following platforms: @@ -22,8 +22,14 @@ Microserver. -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. + + + + +Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board +from Broadcom based on the quad-core SB1A 1480 CPU. @@ -104,8 +110,10 @@ SSH. -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. @@ -144,7 +152,7 @@ bits per second). -Both Cobalt and Broadcom BCM91250A use 115200 bps. +Both Cobalt and Broadcom BCM91250A/BCM91480B use 115200 bps. diff --git a/nl/install-methods/install-tftp.xml b/nl/install-methods/install-tftp.xml index b3f577937..5f4291999 100644 --- a/nl/install-methods/install-tftp.xml +++ b/nl/install-methods/install-tftp.xml @@ -1,5 +1,5 @@ - + Preparing Files for TFTP Net Booting @@ -125,7 +125,7 @@ server: # echo 1 > /proc/sys/net/ipv4/ip_no_pmtu_disc -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. - SGI Indys TFTP Booting + SGI TFTP Booting -On SGI Indys you can rely on the bootpd to supply +On SGI machines you can rely on the bootpd to supply the name of the TFTP file. It is given either as the bf= in /etc/bootptab or as the filename= option in @@ -321,7 +321,7 @@ the filename= option in - Broadcom BCM91250A TFTP Booting + Broadcom BCM91250A and BCM91480B TFTP Booting You don't have to configure DHCP in a special way because you'll pass the diff --git a/nl/install-methods/tftp/bootp.xml b/nl/install-methods/tftp/bootp.xml index b6683f0ad..51c33ed7f 100644 --- a/nl/install-methods/tftp/bootp.xml +++ b/nl/install-methods/tftp/bootp.xml @@ -1,5 +1,5 @@ - + @@ -50,7 +50,7 @@ option specifies the file a client should retrieve via TFTP; see for more details. -On SGI Indys you can just enter the command monitor and type +On SGI machines you can just enter the command monitor and type printenv. The value of the eaddr variable is the machine's MAC address. diff --git a/nl/partitioning/partition/hppa.xml b/nl/partitioning/partition/hppa.xml index 521a5e848..e93a8bb7f 100644 --- a/nl/partitioning/partition/hppa.xml +++ b/nl/partitioning/partition/hppa.xml @@ -1,5 +1,5 @@ - + Partitioning for &arch-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 /boot, since that is the directory where the Linux kernel(s) will be stored. /boot needs to be big enough -to hold whatever kernels you might wish load; 8–16MB is generally -sufficient. +to hold whatever kernels (and backups) you might wish to load; 25–50MB +is generally sufficient. diff --git a/nl/partitioning/partition/i386.xml b/nl/partitioning/partition/i386.xml index fced09dca..c7864c635 100644 --- a/nl/partitioning/partition/i386.xml +++ b/nl/partitioning/partition/i386.xml @@ -1,5 +1,5 @@ - + Partitioning for &arch-title; @@ -80,7 +80,7 @@ within the translated representation of the -The recommended way of accomplishing this is to create a small (5–10MB +The recommended way of accomplishing this is to create a small (25–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/nl/partitioning/partition/mips.xml b/nl/partitioning/partition/mips.xml index fa135ab9b..edd4d7176 100644 --- a/nl/partitioning/partition/mips.xml +++ b/nl/partitioning/partition/mips.xml @@ -1,13 +1,13 @@ - + Partitioning for &arch-title; -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/nl/using-d-i/modules/clock-setup.xml b/nl/using-d-i/modules/clock-setup.xml index 70d40b8c0..22e8dd023 100644 --- a/nl/using-d-i/modules/clock-setup.xml +++ b/nl/using-d-i/modules/clock-setup.xml @@ -1,5 +1,5 @@ - + De interne klok configureren diff --git a/nl/using-d-i/modules/mips/arcboot-installer.xml b/nl/using-d-i/modules/mips/arcboot-installer.xml index 13eba925e..2e522562e 100644 --- a/nl/using-d-i/modules/mips/arcboot-installer.xml +++ b/nl/using-d-i/modules/mips/arcboot-installer.xml @@ -1,11 +1,11 @@ - + <command>arcboot</command>-installer -The boot loader on SGI Indys is arcboot. +The boot loader on SGI machines is arcboot. 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 /etc/arcboot.conf. Each diff --git a/nl/using-d-i/modules/pkgsel.xml b/nl/using-d-i/modules/pkgsel.xml index 6cd341a59..31299ea87 100644 --- a/nl/using-d-i/modules/pkgsel.xml +++ b/nl/using-d-i/modules/pkgsel.xml @@ -1,5 +1,5 @@ - + Selecting and Installing Software diff --git a/nl/using-d-i/modules/tzsetup.xml b/nl/using-d-i/modules/tzsetup.xml index bf902603c..b2126f724 100644 --- a/nl/using-d-i/modules/tzsetup.xml +++ b/nl/using-d-i/modules/tzsetup.xml @@ -1,5 +1,5 @@ - + Uw tijdzone instellen diff --git a/nl/using-d-i/modules/user-setup.xml b/nl/using-d-i/modules/user-setup.xml index 6fc71ea5a..d04a32aab 100644 --- a/nl/using-d-i/modules/user-setup.xml +++ b/nl/using-d-i/modules/user-setup.xml @@ -1,5 +1,5 @@ - + Gebruikers en wachtwoorden instellen -- cgit v1.2.3