[BACK]Return to mvme88k.html CVS log [TXT][DIR] Up to [local] / www

Diff for /www/mvme88k.html between version 1.32 and 1.33

version 1.32, 2003/08/05 13:53:02 version 1.33, 2003/08/10 21:20:15
Line 69 
Line 69 
 egcs revealed a lot of problems in the mvme88k support in gcc, which  egcs revealed a lot of problems in the mvme88k support in gcc, which
 could not be fixed in time for mvme88k to be a supported OpenBSD 2.5  could not be fixed in time for mvme88k to be a supported OpenBSD 2.5
 release.  release.
 As of today, these problems are still not entirely fixed.  
 </p>  </p>
   
 <p>  <p>
Line 85 
Line 84 
 <h3><font color="#0000e0"><strong>Current status:</strong></font></h3>  <h3><font color="#0000e0"><strong>Current status:</strong></font></h3>
   
 <p>  <p>
 Recent work on the toolchain eventually produced a working compiler, as long  Recent work on the toolchain eventually produced a working compiler, although
 as optimization is not enabled; work is in progress towards getting reliable  optimization is not yet totally reliable. Unfortunately, a few kernel bugs
 optimization as well. Unfortunately, numerous kernel stability problems make  prevent the system from being very stable at the moment.
 this effort progress very slowly at the moment.  
 </p>  </p>
   
 <hr>  <hr>
Line 98 
Line 96 
   
 <p>  <p>
 <ul>  <ul>
   <li>Fix remaining gcc mvme88k code generation bugs and get optimization    <li>Fix remaining gcc mvme88k code generation bugs when optimization is used.
       working.  
   <li>Improve the kernels overall stability by debugging and fixing issues.    <li>Improve the kernels overall stability by debugging and fixing issues.
   <li>Improve MVME197 support reliability.    <li>Repair MVME188 and MVME197 support.
   <li>Work on unsupported cards (MVME327, MVME374...).    <li>Work on unsupported cards (MVME327, MVME374...).
   <li>Write code for new binutils (and gdb!!), switch to ELF and, later,    <li>Write code for new binutils (and gdb!!), switch to ELF and, later,
       shared libraries.        shared libraries.
Line 120 
Line 117 
 <ul>  <ul>
 <li><strong>MVME187</strong> (single processor 88100)<br>  <li><strong>MVME187</strong> (single processor 88100)<br>
 All the on-board devices are supported, except for the parallel port.  All the on-board devices are supported, except for the parallel port.
 <li><strong>MVME188</strong> (one to four 88100 processors)<br>  <li><strong>Motorola 8120</strong>
 Contrary to the other MVME processor boards, this board has no on-board  This system is based on an MVME187 with no VMEBus, and is supported as well
 devices; it just acts as a container for an <i>HyperModule</i> which provides  as the regular MVME187.
 1, 2 or 4 processors, and associated Cache/Memory Management Units  
 (<i>CMMU</i>).  
 All existing HyperModule models should be supported, but this has only been  
 tested so far on 1P64 (1 cpu, 4 cmmu) and 2P256 (2 cpu, 4 cmmu) modules.  
 External cards specific to the MVME188 family provide memory and serial ports.  
 <li><strong>MVME197</strong> (single or dual processor 88110)<br>  
 The MVME197 boards come in different flavours, differing by the number of  
 processors (1 or 2) and the optional presence of an external cache controller.  
 All existing configurations should be supported, but this has only been tested  
 on a MVME197LE (no external cache controller) board.  
 Support for this board is still very experimental and has issues.  
 </ul>  </ul>
 </p>  </p>
   
Line 146 
Line 132 
 <li><strong>Serial ports</strong>  <li><strong>Serial ports</strong>
   <ul>    <ul>
   <li>MVME187 on-board Cirrus Logic CL2400 serial ports (tty00-tty03)    <li>MVME187 on-board Cirrus Logic CL2400 serial ports (tty00-tty03)
   <li>MVME188 SYSCON DUART serial ports (ttya, ttyb)  <!--  <li>MVME188 SYSCON DUART serial ports (ttya, ttyb) -->
   </ul>    </ul>
 <li><strong>Ethernet adapters</strong>  <li><strong>Ethernet adapters</strong>
   <ul>    <ul>
   <li>MVME187 and MVME197 on-board Intel i82586 interface    <li>MVME187 <!-- and MVME197 -->on-board Intel i82586 interface
   </ul>    </ul>
 <li><strong>SCSI controllers</strong>  <li><strong>SCSI controllers</strong>
   <ul>    <ul>
   <li>MVME187 and MVME197 on-board NCR 53c7xx controller    <li>MVME187 <!-- and MVME197 -->on-board NCR 53c7xx controller
   </ul>    </ul>
 </ul>  </ul>
 </p>  </p>
Line 171 
Line 157 
 </ul>  </ul>
 </p>  </p>
   
   <p>
   <h4>Unsupported processor boards</h4>
   <p>
   
   <p>
   Although these boards have been more or less supported in the past, their
   support is currently non-functional in the latest snapshot.
   <ul>
   <li><strong>MVME188</strong> (one to four 88100 processors)<br>
   Contrary to the other MVME processor boards, this board has no on-board
   devices; it just acts as a container for an <i>HyperModule</i> which provides
   1, 2 or 4 processors, and associated Cache/Memory Management Units
   (<i>CMMU</i>).
   All existing HyperModule models should be supported, but this has only been
   tested so far on 1P64 (1 cpu, 4 cmmu) and 2P256 (2 cpu, 4 cmmu) modules.
   External cards specific to the MVME188 family provide memory and serial ports.
   <li><strong>MVME197</strong> (single or dual processor 88110)<br>
   The MVME197 boards come in different flavours, differing by the number of
   processors (1 or 2) and the optional presence of an external cache controller.
   All existing configurations should be supported, but this has only been tested
   on a MVME197LE (no external cache controller) board.
   Support for this board is still very experimental and has issues.
   </ul>
   </p>
   
 <hr>  <hr>
 <a name="install"></a>  <a name="install"></a>
 <h3><font color="#0000e0">  <h3><font color="#0000e0">
Line 178 
Line 189 
 </font></h3>  </font></h3>
   
 <p>  <p>
 Due to the compiler problems, no snapshots have been generated since a long  Snapshots are made available from time to time, in
 time. There was a 2.4-current snapshot on the ftp mirrors for some time, which  <a href="ftp://ftp.openbsd.org/pub/OpenBSD/snapshots/mvme88k">this location</a>
 supports only MVME187 cards and can be used as a very crude basis to rebuild  as well as in a few
 a complete system, for the adventurous hacker. If you want to get it, ask  <a href="ftp.html">mirrors</a>.
 <a href="mailto:miod@openbsd.org">miod</a>. Access to an  Here are the
 <a href="mvme68k.html">OpenBSD/mvme68k</a> system greatly helps, as both  <a href="ftp://ftp.openbsd.org/pub/OpenBSD/snapshots/mvme88k/INSTALL.mvme88k">
 systems are very similar.  OpenBSD/mvme88k snapshot installation instructions
   </a> as well.
 </p>  </p>
   
   
 <p>  
 Due to the recent toolchain improvements, a new snapshot is expected soon.  
 Stay tuned!  
 </p>  
   
 <hr>  <hr>
 <a name="details"></a>  <a name="details"></a>
 <h3><font color="#0000e0"><strong>Hardware details:</strong></font></h3>  <h3><font color="#0000e0"><strong>Hardware details:</strong></font></h3>
Line 217 
Line 223 
 </p>  </p>
   
 <p>  <p>
 This is a dmesg of an MVME188 system.  This is a boot log of an MVME187 system.
 <pre>  <pre>
 Model: Motorola MVME188 25Mhz  MVME187 board configuration #A: 1 CPUs 2 CMMUs
 MVME188 board configuration #5: 2 CPUs 4 CMMUs  CPU0 is attached with 2 MC88200 CMMUs
 CPU0 is attached with 2 MC88204 CMMUs  
 CPU1 is attached with 2 MC88204 CMMUs  
 CPU0 is master CPU  CPU0 is master CPU
 [ using 146999 bytes of bsd a.out symbol table ]  [ using 163088 bytes of bsd a.out symbol table ]
 ddb enabled  
 Copyright (c) 1982, 1986, 1989, 1991, 1993  Copyright (c) 1982, 1986, 1989, 1991, 1993
         The Regents of the University of California.  All rights reserved.          The Regents of the University of California.  All rights reserved.
 Copyright (c) 1995-2001 OpenBSD. All rights reserved.  http://www.OpenBSD.org  Copyright (c) 1995-2003 OpenBSD. All rights reserved.  http://www.OpenBSD.org
   
 OpenBSD 2.9-current (GENERIC) #59: Thu Jun 14 01:18:03 GMT 2001  OpenBSD 3.3-current (GENERIC) #86: Sun Aug 10 03:49:48 GMT 2003
     miod@arzon:/src/current/src/sys/arch/mvme88k/compile/GENERIC      miod@arzon:/usr/src/sys/arch/mvme88k/compile/GENERIC
 real mem  = 33550336  Model: Motorola MVME187, 33MHz
 avail mem = 28381184 (6929 pages)  real mem  = 67108864
 using 435 buffers containing 1781760 bytes of memory  avail mem = 59138048 (14438 pages)
 mainbus0 (root) machine type MVME188  using 844 buffers containing 3457024 bytes of memory
   mainbus0 (root) machine type MVME187
 bugtty0 at mainbus0 addr 0xfff45000: bugtty  bugtty0 at mainbus0 addr 0xfff45000: bugtty
 syscon0 at mainbus0 addr 0xfff00000: rev 1  pcctwo0 at mainbus0 addr 0xfff00000: rev 0
 clock0 at syscon0 ipl 5: VME188  clock0 at pcctwo0 ipl 5: VME1x7
 sclock0 at syscon0 ipl 5: VME188  sclock0 at pcctwo0 ipl 5: VME1x7
 nvram0 at syscon0 offset 0x80000: MK48T02 len 2048  memc0 at pcctwo0 offset 0x43000: MEMC040 rev 1
 dart0 at syscon0 offset 0x82000 ipl 3 console (ttya)  memc1 at pcctwo0 offset 0x43100: MCECC rev 0
 vme0 at syscon0 offset 0x85000: system controller  nvram0 at pcctwo0 offset 0xc0000: MK48T08 len 8192
   cl0 at pcctwo0 offset 0x45000 ipl 3 console
   vme0 at pcctwo0 offset 0x40000: vector base 0x80, system controller
   vme0: using BUG parameters
   vme0: 1phys 0x04000000-0xefff0000 to VME 0x04000000-0xefff0000
   vme0: 2phys 0xff000000-0xff7f0000 to VME 0xff000000-0xff7f0000
   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  vmes0 at vme0
 vs0 at vmes0 addr 0xffff9000 vaddr 0x2e59000 vec 0x80 ipl 2: target 7  vs0 at vmes0 addr 0xffff9000 vaddr 0x551b000 vec 0x80 ipl 2: target 7
 scsibus0 at vs0: 8 targets  scsibus0 at vs0: 8 targets
 sd0 at scsibus0 targ 1 lun 0: &lt;FUJITSU, M2624F-512, M405&gt; SCSI1 0/direct fixed  sd0 at scsibus0 targ 0 lun 0: &lt;COMPAQPC, DCAS-32160, S6CA&gt; SCSI2 0/direct fixed
 sd0: 496MB, 1429 cyl, 11 head, 64 sec, 512 bytes/sec, 1015812 sec total  sd0: 2006MB, 8188 cyl, 3 head, 167 sec, 512 bytes/sec, 4110000 sec total
 vs1 at vmes0 addr 0xffff9800 vaddr 0x2e5a800 vec 0x82 ipl 2: target 7  
 scsibus1 at vs1: 8 targets  
 ve0 at vmes0 addr 0xffff1200 vaddr 0x2e5b200 vec 0x74 ipl 1  
 ve0: address 00:00:77:83:9f:cc  
 ve0: 128 receive buffers, 32 transmit buffers  
 vmel0 at vme0  vmel0 at vme0
   ie0 at pcctwo0 offset 0x46000 ipl 1: address 08:00:3e:21:7c:74
 boot device: sd0  boot device: sd0
 root on sd0a  root on sd0a
 rootdev=0x400 rrootdev=0x800 rawdev=0x802  rootdev=0x400 rrootdev=0x800 rawdev=0x802
   Automatic boot in progress: starting file system checks.
   /dev/rsd0a: 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 -&gt; 1
   kern.splassert: 0 -&gt; 2
   starting network
   add net default: gateway odyssee
   starting system logger
   starting rpc daemons: portmap ypbind rdate timed.
   savecore: no core dump
   checking quotas: done.
   building ps databases: kvm dev.
   clearing /tmp
   starting pre-securelevel daemons:.
   setting kernel security level: kern.securelevel: 0 -&gt; 1
   creating runtime link editor directory cache.
   starting network daemons: inetd sshd.
   starting local daemons:.
   standard daemons: cron.
   Sun Aug 10 20:22:04 GMT 2003
   
   OpenBSD/mvme88k (arzon) (console)
   
   login:
 </pre>  </pre>
   
 <hr>  <hr>
Legend:
Removed from v.1.32  
changed lines
  Added in v.1.33