From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@minnie.tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [TUHS] System III on 11/34 + rl02
Date: Thu, 25 Oct 2018 06:56:47 -0400 (EDT) [thread overview]
Message-ID: <20181025105647.1929518C0A0@mercury.lcs.mit.edu> (raw)
> From: Jacob Ritorto
> If this is true, I wonder why the install only offers rl01?
Where does it say this? (I didn't search for that.)
> I'm totally in the market for an Able Enable board too! Out of
> zcuriosity, is it totally out of the question to just find the prints
> and do a production run?
Rotsa ruck! They're down the same mine as Jimmy Hoffa!! :-)
But seriously, if you could find them, that would be fantastic. I've managed
to collect (thanks Clem!) a tiny bit of info about them:
http://gunkies.org/wiki/Able_ENABLE
and I _think_ I've worked out how they worked, but more is better. We had a
set of the prints at MIT BITD, but we didn't have the PROM/PLA/PAL/etc
programming info, and one would need that too to reproduce them.
> I sure hope there's a pdp11 sdcard / usb disk solution someday like they
> did for the Commodore 64
So Dave Bridgham and I have been working on a QBUS card with an FPGA that uses
an SD card to hold the bits, and emulates an RK11/RP11/etc controller. We have
a wire-wrap prototype working (the RK11's done, the RP11 should be a short
edit of that), and UNIX boots and runs. Now to turn it into PCB's...
We've planned that the next step will be to do a UNIBUS version, which will
also include ENABLE functionality (although it won't be plug compatible with
an ENABLE, the memory will be on-board).
Now to find the time/energy to make it happen... :-(
Noel
next reply other threads:[~2018-10-25 10:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-25 10:56 Noel Chiappa [this message]
2018-10-26 3:27 ` Jacob Ritorto
-- strict thread matches above, loose matches on Subject: below --
2018-10-24 11:23 Noel Chiappa
2018-10-24 2:59 Jacob Ritorto
2018-10-24 3:21 ` Clem cole
2018-10-25 1:22 ` Jacob Ritorto
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=20181025105647.1929518C0A0@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.edu \
--cc=tuhs@minnie.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).