The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: bqt@update.uu.se (Johnny Billquist)
Subject: [TUHS] 11/40E and 11/60
Date: Tue, 28 Oct 2014 23:48:10 +0100	[thread overview]
Message-ID: <54501D2A.30607@update.uu.se> (raw)
In-Reply-To: <CAC20D2NRL7wUpWKpUUN_7w693PLUXefwbR4tRad-HBT72+_iZw@mail.gmail.com>

On 2014-10-28 19:22, Clem Cole wrote:
>
> On Tue, Oct 28, 2014 at 1:46 PM, Johnny Billquist <bqt at update.uu.se
> <mailto:bqt at update.uu.se>> wrote:
>
>     DEC actually made two PDP-11s that were micro programmable. The
>     11/60 and the 11/03 (if I remember right). DEC never had
>     microprogramming for the 11/40, but obviously CMU did that.
>
>
> C.mmp was 11/40E's and C.m* was LSI/11's and both needed them for the
> capabilities support.  I never really got to mess with the WCS units -
> although we learned about them (along with ISPL/ISPS in courses), I did
> hack on the OS and in user space of both systems - which was a wonderful
> experience. It was how I learned about capabilities which I still have
> soft spot.   But around that time, I was also introduced to this strange
> new system language and system and started to get paid better as a
> programmer for a group using it.   I never went back ;-)

Yeah, it was the C.mmp I was thinking of when I said that CMU obviously 
had to have been playing at this.

> BTW: the 780 & 750 had ustore but it was not user documented and the
> tools were internal.   Paul Guilbo wrote much of both and later would
> write the uCode for the Masscomp FPU and APU.   Paul was bitching about
> the great tool(s) they had had at DEC, so one weekend two of us on the
> SW team got sick of his bitching a couple of us hacked up a uCode
> assembler in the same key in Yacc/lex/C (not BLISS ;-).

:-)
As someone else mentioned, the 11/780 had a separate product for user 
written microcode. I think it actually also included a different board 
for the CPU, with more memory for the microcode. So it must have been 
documented externally somehow, somewhere.

The 11/750 was not documented for external use, I think. However, I have 
some vague memory of seeing something about user written microcode for 
it as well.
And of course, Ultrix had a microcode patch for the 11/750, which fixed 
some bugs in a couple of instructions. This microcode patch is still 
included in the NetBSD/vax distribution. :-)

The 86x0 machines always loaded microcode from the FE RL02, and there is 
documentation on that microcode available today, although it was DEC 
internal at the time. And I still happen to have access to an 8650. But 
no time to actually try and play with the microcode. And that machine is 
rather complex as well. That's when things started to get pipelined and 
other stuff that makes things much more difficult to fool around with.

	Johnny

-- 
Johnny Billquist                  || "I'm on a bus
                                   ||  on a psychedelic trip
email: bqt at softjar.se             ||  Reading murder books
pdp is alive!                     ||  tryin' to stay hip" - B. Idol



      parent reply	other threads:[~2014-10-28 22:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.295.1414500157.3356.tuhs@minnie.tuhs.org>
2014-10-28 17:46 ` [TUHS] 11/40E and 11/60 (was: speaking of early C compilers) Johnny Billquist
2014-10-28 17:57   ` Ronald Natalie
2014-10-28 17:58   ` Ronald Natalie
2014-10-28 18:22   ` Clem Cole
2014-10-28 18:39     ` Ronald Natalie
2014-10-28 19:03       ` Clem Cole
2014-10-28 22:54         ` [TUHS] 11/40E and 11/60 Johnny Billquist
2014-10-28 22:48     ` Johnny Billquist [this message]

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=54501D2A.30607@update.uu.se \
    --to=bqt@update.uu.se \
    /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).