summaryrefslogtreecommitdiff
path: root/distrib
diff options
context:
space:
mode:
authorMiod Vallat <miod@cvs.openbsd.org>2010-07-10 19:38:40 +0000
committerMiod Vallat <miod@cvs.openbsd.org>2010-07-10 19:38:40 +0000
commit9e79d03bb491479a93a11dc0b6ddae5ded2fcbd7 (patch)
treeab9374bab69a00a82277150ef4e39cb0e4b57bd9 /distrib
parent9a9eb00f7b2ba1a461a4f0e474e2d8431e727018 (diff)
sun4e bits
Diffstat (limited to 'distrib')
-rw-r--r--distrib/notes/sparc/hardware14
-rw-r--r--distrib/notes/sparc/install28
-rw-r--r--distrib/notes/sparc/prep10
3 files changed, 23 insertions, 29 deletions
diff --git a/distrib/notes/sparc/hardware b/distrib/notes/sparc/hardware
index fdb5f1aa999..5419c5bd4e2 100644
--- a/distrib/notes/sparc/hardware
+++ b/distrib/notes/sparc/hardware
@@ -1,4 +1,4 @@
-dnl $OpenBSD: hardware,v 1.76 2010/02/23 15:52:33 jasper Exp $
+dnl $OpenBSD: hardware,v 1.77 2010/07/10 19:38:36 miod Exp $
OpenBSD/MACHINE OSREV runs on the following classes of machines:
* sun4: the VME series
- 4/100: Original SPARC with VME. Many hardware bugs.
@@ -17,6 +17,10 @@ OpenBSD/MACHINE OSREV runs on the following classes of machines:
- IPX: SS2 in a cube, with cgsix graphics builtin
- ELC: SS2-performance built into a B&W monitor
+ * sun4e:
+ - SPARCengine 1E: a 6U VME cross between a sun4 and a sun4c,
+ similar to a Sun 4/300 with an OpenPROM interface.
+
* sun4m:
- 600MP: The original Sun4m machine. This is an mbus machine with
SBus and VME busses.
@@ -153,10 +157,10 @@ Supported devices {:-include-:}:
- SBus 10/100MBit hme Ethernet cards (hme) [*]
- SBus 10/100MBit SunSwift SUNW,fas Ethernet+SCSI cards (hme) [*]
- SBus Quad 10/100MBit hme and qfe Ethernet cards (hme) [*]
- [*] Not supported in sun4c-class machines due to PROM limitations.
+ [*] Not supported in sun4c and sun4e machines due to PROM limitations.
* SCSI controllers:
- - on-board SCSI controller (sun4c, sun4m, and 4/300) (esp)
+ - on-board SCSI controller (sun4c, sun4e, sun4m, and 4/300) (esp)
- SBus SCSI controllers (including 3rd party compatible boards) (esp)
- SBus cards containing both AMD Lance le and esp SCSI (esp)
- SBus SUNW,fas Ethernet+SCSI cards (esp) [*]
@@ -164,7 +168,7 @@ Supported devices {:-include-:}:
- 4/110 "SCSI weird" on-board controller (polled DMA) (sw)
- QSP/ISP SCSI controllers (i.e. "PTI,ptisp", "ptisp", "SUNW,isp"
and "QLGC,isp") (isp)
- [*] Not supported in sun4c-class machines due to PROM limitations.
+ [*] Not supported in sun4c and sun4e machines due to PROM limitations.
* SMD and other disk controllers:
- Xylogics 7053 VME SMD disk controller (xd)
@@ -333,4 +337,4 @@ Hardware that we do NOT currently support, but get many questions about:
* SBus FDDI cards
The supplied GENERIC kernel is the best attempt at a configuration that
-works on the widest range of machines (sun4, sun4c, and sun4m).
+works on the widest range of machines (sun4, sun4c, sun4e and sun4m).
diff --git a/distrib/notes/sparc/install b/distrib/notes/sparc/install
index 99663bce385..82d598e310f 100644
--- a/distrib/notes/sparc/install
+++ b/distrib/notes/sparc/install
@@ -1,4 +1,4 @@
-dnl $OpenBSD: install,v 1.70 2010/03/16 17:23:09 miod Exp $
+dnl $OpenBSD: install,v 1.71 2010/07/10 19:38:37 miod Exp $
OpenBSDInstallPrelude({:-SMD disks-:})
There are several ways to install OpenBSD onto a disk. The normal way
@@ -423,25 +423,15 @@ Normally, this file is a symbolic link to an appropriate second-stage
boot program, which should be located in a place where the TFTP daemon
can find it (remember, many TFTP daemons run in a chroot'ed environment).
-You can find the boot program in `/usr/mdec/boot' in the OpenBSD/MACHINE
-distribution. Unfortunately, it is necessary to install this file
-differently for sun4 and sun4c clients: the sun4 version needs to have its
-`a.out' header stripped off (otherwise the machine will crash), while the
-sun4c version must retain it (otherwise the PROM will complain).
-
-Here's an example to illustrate this whole mess:
-
- server# cd /<client-root-dir>/usr/mdec
- if client is a sun4:
- server# set SKIP=1
- server# set KARCH=SUN4
- else
- server# set SKIP=0
- server# set KARCH=SUN4C
- server{:-#-:} dd if=boot of=/tftpboot/boot.MACHINE.OpenBSD.$KARCH skip=$SKIP bs=32
- server# cd /tftpboot
- server{:-#-:} ln -s boot.MACHINE.OpenBSD.$KARCH 8273900B.$KARCH
+As an exception to the above rule, sun4e systems make a request for
+`/tftpboot/IP_IN_HEX.SUN4E', i.e. the TFTP filename is in a subdirectory.
+You can find the boot program as `boot.net' in the OpenBSD/MACHINE
+distribution. Unfortunately, many, if not all, sun4e PROM have a bug and
+fail to load a file which size is a multiple of 512 bytes. If you are
+trying to netboot a sun4e system, simply append some bytes to the
+file, like this:
+ dd if=/dev/zero bs=32b count=1 >> boot.net
After the boot program has been loaded into memory and given control by
the PROM, it starts locating the machine's remote root directory through
diff --git a/distrib/notes/sparc/prep b/distrib/notes/sparc/prep
index 31127a4e347..db0b5295553 100644
--- a/distrib/notes/sparc/prep
+++ b/distrib/notes/sparc/prep
@@ -46,16 +46,16 @@ prevent accidents if you change the SCSI bus configuration or a drive
is down.
Your OpenBOOT ROM may need some setup. If you are running OpenBSD on
-a sun4c, or sun4m system, the ROM must be set to "new" command mode.
-If your sun4c or sun4m machine comes up and gives you a `>' prompt
-instead of `ok', type:
+a sun4c, sun4e or sun4m system, the ROM must be set to "new" command
+mode. If your machine comes up and gives you a `>' prompt instead of
+`ok', type:
- >n
+ > n
ok setenv sunmon-compat? false
ok
This is needed because OpenBSD relies on the behaviour of the "new" command
-mode. OpenBSD will not boot correctly on sun4c or sun4m systems that
+mode. OpenBSD will not boot correctly on sun4c, sun4e or sun4m systems that
are not running in "new" command mode. The sun4 systems such as the 4/110,
4/200, and 4/300 system do not have a "new" command mode, and will work
fine as-is.