-This port was primarily done by Theo de Raadt in 1995 as a contract to
-Willowglen Singapore. An earlier port to the MVME147 by Chuck Cranor
-based on Paul Mackerras' old DA30 code (and using hardware donated by
-Jonathan Levine at Theo's request) provided a solid development
-platform. Bizzarely, Dale Rahn of Motorola also independently wrote a
-port to the MVME147. For most kernel parts, both their ports were
-analysed but more code was written new by Theo, or based on the hp300
-code. Dale helped significantly during the porting to the 68040
-models and wrote most of the code specific to the MVME167 model.
-Steve Murphee continued work and made the MVME177 work, as well as
-adding support for some VME devices.
+OpenBSD/mvme68k runs on a large subset of Motorola's 680x0-based VME
+motherboard family.
+
-The people working the most on OpenBSD/mvme68k currently consists of
-Steve Murphee, Theo de Raadt, and Dale Rahn. Of course, others are
-very welcome!
+There is currently no maintainer for the mvme68k port.
+
+
+
Table of contents
-The same kernel currently runs on the following pieces of hardware:
-
-
MVME147: 68030
-This works stably.
-
-
Everything supported except the parallel port.
-
I have a driver for the parallel port, but it is not integrated yet.
+
Everything important working.. with these additional notes:
-
SCSI working (4.5MB/sec off a 4.2G Quantum Grand Prix).
-
VME bus support untested
-
parity and ecc not supported
-
flash driver not working
-
IP module driver untested
-
-
+
+
+
History:
-
MVME165: 68040
-What little we know about it makes us think it is doable.
+This port was primarily done by Theo de Raadt in 1995 as a contract to
+Willowglen Singapore. An earlier port to the MVME147 by Chuck Cranor
+based on Paul Mackerras' old DA30 code (and using hardware donated by
+Jonathan Levine at Theo's request) provided a solid development
+platform.
+
-
MVME166: 68040
-This might already work. Anyone want to test it?
+Bizzarely, Dale Rahn, working for Motorola back then, also independently
+wrote a port to the MVME147. For most kernel parts, both their ports were
+analyzed but more code was written from scratch by Theo, or based on the
+hp300 code.
+
-
MVME167C: 68040
-This works stably.
-
-
Works as well as the MVME162 port above, plus these notes:
-
parallel port not supported.
-
+Dale helped significantly during the porting to the 68040
+models and wrote most of the code specific to the MVME167 model.
+Later, Steve Murphee continued work and made the MVME177 work, as well as
+adding support more some VME devices.
+
-
MVME177-001: 68060
-This works stably.
-
-
Works as well as the MVME167 port.
-
+
+
+
Current status:
+
-
+Currently, all the boards listed in the
+supported hardware list section below boot
+multi-user, and support enough of the on-board devices to be generally
+useable.
+
-Additional VME devices that are supported:
-
-
MVME376: VME Lance ethernet
-
MVME328: SCSI controller
-
+OpenBSD/mvme68k is able to run sun3 SunOS binaries via the
+COMPAT_SUNOS kernel option.
+Thus, the MVME177 board is probably the fastest machine capable of running
+SunOS m68k binaries!
+
-
-For all these architectures, both diskless booting using sun-style
-bootparams/nfs and regular full disk booting are supported.
-
-Note: This port has COMPAT_SUNOS support, so it can run SunOS sun3
-binaries. As such, I think that the MVME177 is probably the fastest
-machine capable of running SunOS sun3 binaries....
+As none of the mvme68k boards have graphics devices, and none of the Motorola
+VME frame buffers are currently supported, there are no X-Window servers
+available.
+However, a complete set of X-Window clients and utilities is available,
+allowing OpenBSD/mvme68k machines to behave as X11 font servers, or run
+X-Window clients on remote display.
+
-MVME177 Debugger/Diagnostics Release Version ...
-COLD Start
+
+
+
Hardware details:
-Local Memory Found =02000000 (&33554432)
+
+As VME hardware is quite uncommon in the average retail place,
+this section is here to satisfy the well-founded curiosity about the mvme68k
+hardware.
+
-MPU Clock Speed =50Mhz
+
+This picture is a MVME162 processor board.
+
+
-177-Bug>bo
-Booting from: VME177, Controller 0, Drive 0
-Loading: Operating System
-
-Volume: NBSD
-
-IPL loaded at: $003F0000
->> OpenBSD BOOT [$Revision: 1.8 $]
-using ctrl 0 dev 0
-Booting /OpenBSD @ 0x10000
-8c000+8000+caf8 [8f40+9162] start 0x10020
-[ preserving 73898 bytes of OpenBSD symbol table ]
-Copyright (c) 1982, 1986, 1989, 1991, 1993
- The Regents of the University of California. All rights reserved.
-
-OpenBSD 3.1-current (GENERIC) #17: Thu Apr 18 14:02:28 PDT 2002
- deraadt@mvme68k.openbsd.org:/sys/arch/mvme68k/compile/GENERIC
-Motorola 177-001: 50MHz MC68060 CPU+MMU+FPU, 8k on-chip physical I/D caches
+
+This is a boot log of an MVME177 system.
+
+OpenBSD 3.2-current (GENERIC) #5: Mon Dec 23 01:49:09 GMT 2002
+ miod@bioue.gentiane.org:/usr/src/sys/arch/mvme68k/compile/GENERIC
+Motorola MVME177-011: 60MHz MC68060 CPU+MMU+FPU, 8k on-chip physical I/D caches
real mem = 33554432
-avail mem = 27975680 (6721 pages)
+avail mem = 27525120 (6720 pages)
using 409 buffers containing 1675264 bytes of memory
mainbus0 (root)
pcctwo0 at mainbus0 addr 0xfff00000: rev 0
@@ -149,18 +166,18 @@
vme0: using BUG parameters
vme0: 1phys 0x02000000-0xefff0000 to VME 0x02000000-0xefff0000
vme0: 2phys 0x00000000-0x00000000 to VME 0x00000000-0x00000000
-vme0: 3phys 0x00400000-0x00ff0000 to VME 0x00400000-0x00ff0000
+vme0: 3phys 0x00000000-0x00000000 to VME 0x00000000-0x00000000
vme0: 4phys 0x00000000-0x00000000 to VME 0x00000000-0x00000000
vme0: vme to cpu irq level 1:1
vmes0 at vme0
vmel0 at vme0
-ie0 at pcctwo0 offset 0x46000 ipl 1: address 08:00:3e:23:5c:a2
-siop0 at pcctwo0 offset 0x47000 ipl 2: version 2 target 7
-scsibus0 at siop0: 8 targets
-siop0: target 0 now synchronous, period=100ns, offset=8
-sd0 at scsibus0 targ 0 lun 0: <QUANTUM, FIREBALL1080S, 1Q04> SCSI2 0/direct fixed
-sd0: 1042MB, 3835 cyl, 4 head, 139 sec, 512 bytes/sec, 2134305 sec total
-memc0 at pcctwo0 offset 0x43000: MCECC rev 0
+ie0 at pcctwo0 offset 0x46000 ipl 1: address 08:00:3e:26:3f:69
+ssh0 at pcctwo0 offset 0x47000 ipl 2: version 2 target 7
+scsibus0 at ssh0: 8 targets
+ssh0: target 0 now synchronous, period=100ns, offset=8
+sd0 at scsibus0 targ 0 lun 0: SCSI2 0/direct fixed
+sd0: 2006MB, 8188 cyl, 3 head, 167 sec, 512 bytes/sec, 4110000 sec total
+memc0 at pcctwo0 offset 0x43000: MEMC040 rev 1
nvram0 at pcctwo0 offset 0xc0000: MK48T08 len 8192
sram0 at mainbus0 addr 0xffe00000: len 131072
boot device: sd0
@@ -168,13 +185,19 @@
rootdev=0x400 rrootdev=0x800 rawdev=0x802
Automatic boot in progress: starting file system checks.
/dev/rsd0a: file system is clean; not checking
-/dev/rsd0g: file system is clean; not checking
+/dev/rsd0d: file system is clean; not checking
/dev/rsd0e: file system is clean; not checking
+/dev/rsd0f: file system is clean; not checking
+/dev/rsd0g: file system is clean; not checking
+/dev/rsd0h: file system is clean; not checking
+/dev/rsd0i: file system is clean; not checking
setting tty flags
+ddb.console: 0 -> 1
+kern.splassert: 0 -> 2
starting network
-add host m177: gateway localhost
+add net default: gateway 10.0.1.101
starting system logger
-starting rpc daemons: portmap ypbind amd.
+starting rpc daemons: portmap ypbind rdate timed.
savecore: no core dump
checking quotas: done.
building ps databases: kvm dev.
@@ -186,18 +209,63 @@
starting network daemons: sendmail inetd sshd.
starting local daemons:.
standard daemons: cron.
-Thu Apr 18 14:50:53 PDT 2002
+Thu Dec 26 18:07:08 GMT 2002
-OpenBSD/mvme68k (m177) (ttya)
+OpenBSD/mvme68k (bioue.gentiane.org) (console)
-login:
+login:
![[OpenBSD]](images/smalltitle.gif){kind=small}
