From: Chris Hanson <cmhanson@eschatologist.net>
To: Gregg Levine <gregg.drwho8@gmail.com>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] Historical sources for 68010 + 68451 systems?
Date: Tue, 15 Sep 2020 20:05:46 -0700 [thread overview]
Message-ID: <5B4796B8-4E02-47C0-AD0E-EEBFF4334466@eschatologist.net> (raw)
In-Reply-To: <CAC5iaNEvhZx_GSPww4dNpMohp_tTfUbn=LKPmVy7Raw9Z97i3g@mail.gmail.com>
On Sep 15, 2020, at 4:55 PM, Gregg Levine <gregg.drwho8@gmail.com> wrote:
> Chris I have one of the later ones, a 133 in fact, and I've been
> trying to find what I could run on it. Never mind a case for it, plus
> power supply and stuff.... Can you share, off list of course, where
> you'd gotten it?
Oh, I don’t mind sharing on-list! I just bought the board—and a system controller, and some additional RAM boards, as well as the VME chassis with built-in PSU—on eBay. Lots of sellers are willing to make pretty good deals. There’s barely anything I paid over US$100 for, and I’ve only been collecting the VME stuff for a couple years.
In theory you should be able to use any VME or VXI chassis for most VME hardware. What’s hard to find are manuals for anything not on Bitsavers[1], or software to run on it. At least NetBSD has been ported to the common 68030+ and PowerPC VME boards, and an old version of OpenBSD runs on the common 88K ones. Alas the 133 doesn’t have an MMU so it’s going to be a bit more restricted.
One of the reasons to run MINIX 1.5 on my MVME121 is that it should be nice and fast on a 10MHz system with 8.5MB of RAM (including 4KB of cache), and as a V7 UNIX clone with an ANSI C compiler it’ll be easy to write for and port to. It’ll probably also be nicer than running one of the first few versions of Motorola System V/68 on it too, since I think that’s SVR1…
Your 133 should also be straightforward to port MINIX to as well, since all the hardware’s simple, standard, and documented in the manual (plus data books).
My plan was to start with MINIX 1.5 on Atari ST under Hatari, then just write some device drivers and a boot loader to replace the ST-specific ones.
— Chris
[1] Or Artisan Technology Group’s web site; they sell a ton of used VME hardware, and seem to collect what manuals and data sheets they can and provide them as PDF.
next prev parent reply other threads:[~2020-09-16 3:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 23:28 Chris Hanson
2020-09-15 23:55 ` Gregg Levine
2020-09-16 3:05 ` Chris Hanson [this message]
2020-09-16 5:21 ` Arno Griffioen
2020-09-16 8:53 ` Al Kossow
2020-09-16 23:47 ` Dave Horsfall
2020-09-16 19:53 Nelson H. F. Beebe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5B4796B8-4E02-47C0-AD0E-EEBFF4334466@eschatologist.net \
--to=cmhanson@eschatologist.net \
--cc=gregg.drwho8@gmail.com \
--cc=tuhs@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).