From 4d1bbfe822d3a3110f649386db70e10109f2bb63 Mon Sep 17 00:00:00 2001 From: Martin Michlmayr Date: Sat, 14 Dec 2013 10:21:07 +0000 Subject: Remove information about Cobalt devices --- en/boot-installer/mipsel.xml | 47 +---------------------------------- en/hardware/hardware-supported.xml | 6 ++--- en/hardware/supported-peripherals.xml | 5 ---- en/hardware/supported/mipsel.xml | 23 ----------------- 4 files changed, 3 insertions(+), 78 deletions(-) (limited to 'en') diff --git a/en/boot-installer/mipsel.xml b/en/boot-installer/mipsel.xml index 96d7d4c59..6615c38ad 100644 --- a/en/boot-installer/mipsel.xml +++ b/en/boot-installer/mipsel.xml @@ -3,52 +3,7 @@ Booting with TFTP - - Cobalt TFTP Booting - - -Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to -install an NFS server and put the installer files in -/nfsroot. When you boot your Cobalt, you have to -press the left and the right cursor buttons at the same time and the -machine will boot via the network from NFS. It will then display several -options on the display. There are the following two installation methods: - - - - -Via SSH (default): In this case, the installer will configure the network -via DHCP and start an SSH server. It will then display a random password -and other login information (such as the IP address) on the Cobalt LCD. -When you connect to the machine with an SSH client you can start with -the installation. - - - - -Via serial console: Using a null modem cable, you can connect to the serial -port of your Cobalt machine (using 115200 bps) and perform the installation -this way. - - - - - - +&boot-installer-intro-net.xml; - Boot Parameters - - - Cobalt TFTP Booting - - -You cannot pass any boot parameters directly. Instead, you have to edit -the /nfsroot/default.colo file on the NFS server and -add your parameters to the args variable. - - - - - diff --git a/en/hardware/hardware-supported.xml b/en/hardware/hardware-supported.xml index 7b2f1941a..487ad2cd4 100644 --- a/en/hardware/hardware-supported.xml +++ b/en/hardware/hardware-supported.xml @@ -105,10 +105,8 @@ variations of each architecture known as flavors. - MIPS (little endian) - mipsel - Cobalt - cobalt + MIPS (little endian) + mipsel MIPS Malta (32 bit) 4kc-malta diff --git a/en/hardware/supported-peripherals.xml b/en/hardware/supported-peripherals.xml index e69492bf9..4a75b35d2 100644 --- a/en/hardware/supported-peripherals.xml +++ b/en/hardware/supported-peripherals.xml @@ -24,10 +24,5 @@ Package installations from XPRAM and tape are not supported by this system. All packages that you want to install need to be available on a DASD or over the network using NFS, HTTP or FTP. - - -The Cobalt RaQ has no support for additional devices but the Qube has one -PCI slot. - diff --git a/en/hardware/supported/mipsel.xml b/en/hardware/supported/mipsel.xml index a4c8a80a9..68a212a70 100644 --- a/en/hardware/supported/mipsel.xml +++ b/en/hardware/supported/mipsel.xml @@ -10,12 +10,6 @@ -Cobalt Microserver: only MIPS based Cobalt machines are covered here. This -includes the Cobalt RaQ, Qube2 and RaQ2, and the Gateway Microserver. - - - - MIPS Malta: this platform is emulated by QEMU and is therefore a nice way to test and run &debian; on MIPS if you don't have the hardware. @@ -31,21 +25,4 @@ debian-&arch-listname; mailing list. - CPU/Machine types - - - -All MIPS based Cobalt machines are supported with the exception of the -Qube 2700 (Qube 1). - - - - - Supported console options - - -Cobalt machines use 115200 bps. - - - -- cgit v1.2.3