Nishimura-San and others,

  Thanks for your encouragements.  I'm looking forward to getting started.
  Like I said I'm currently working on getting my Olivetti working, and 
  after a week's effort I've been successful in cross compiling a NetBSD
  kernel from an Linux/Intel box.  That wasn't straight froward, but 
  I now have a kernel that tries to boot.  I'm going to try to run some
  binaries from the ARC snapshot next.  I think the ethernet is not working
  on my machine.( I found some differences between the M700 and Magnum
  4000)

  I'm still figuring my way out.

  So, do you recommend creating a directory like arch/magnum or putting
  the magnum3000 stuff into arch/newsmips or arch/mips?

  Thanks kindly,

....maki....

>>> I would love to hear more about those docs.  I have a relabled Magnum 
>>> 3000(Bull DPS M-20) and after I get things going on my 
Magnum4000(Olivetti 
>>> M700) I plan to move onto the Magnum 3000s.  Between your docs, sources 
>for 
>>> RISCos, and sources for Plan9 we should have enough to get things going 
on 
>>> the Magnum3000s.
>>
>> They talk about the hardware memory maps.  Likely enough so that you
>> can write drivers and such if you can find the datasheets.
>
>Things are mostly prepared, just start the project.  You have complete
>ELF toolchain with PIC/dynamic link and cross compile environment on
>any handy NetBSD (or other) box.  You have plenty supplies of MI source
>code for most hardwares inside R3000 Magnum.  You may have RISCos 4.x
>driver source code found in /usr/src/uts/.  You even have no need to
>run painfully ackward process of preparing any /usr/lib/ and building
>the entire userland; just pick up NetBSD/newmips snapshot.  So, what
>are you waiting for? :->
>
>Tohru Nishimura
>Nara Institute of Science and Technology
>