The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Jon Steinhart <jon@fourwinds.com>
Cc: TUHS main list <TUHS@minnie.tuhs.org>
Subject: Re: [TUHS] Spacewar at Bell Labs [ really paper tape readers and tangentially related things ]
Date: Wed, 15 Jan 2020 09:50:02 -0500	[thread overview]
Message-ID: <CAC20D2M5-Pfxr9VSQ=0AtyYX5x-NEUWzPOC-ZYeSs7AGGw3-fw@mail.gmail.com> (raw)
In-Reply-To: <202001150710.00F7AsFQ1716609@darkstar.fourwinds.com>

[-- Attachment #1: Type: text/plain, Size: 2528 bytes --]

On Wed, Jan 15, 2020 at 2:12 AM Jon Steinhart <jon@fourwinds.com> wrote:

> we tried to use LSI-11s
> but those turned out to be useless because of the way that DEC did the DRAM
> refresh; it wasn't interleaved, they just stopped everything every so many
> ms and refreshed everything.  Non-starter for real-time systems.
>
Be careful as to who you denigrate, my friend. 😂

Very interesting history, IMO.    Yes, DEC sold the LSI-11, but Western
Digital designed it.  DEC (KO specifically) had just put Ray Ball and Ken
O'humundro's CalData out of business for cloning the PDP-11/45 with a
Unibus on his Caldata 500
<http://www.bitsavers.org/pdf/calData/CalData_Brochures_1974.pdf>.   At the
time, WD had developed and started to sell to the systems manufacturers a
new set of bit-slice chips the MCP-1600
<https://en.wikipedia.org/wiki/MCP-1600>, to compete with AMD's 2900 and
Intel 3000 series (plus they were already a chip supplier to DEC for UARTS).
   So WD designs and builds a few LSI-11 as a sales demo of what you could
do with their new bit-slice chip (*i.e. *as those things often go, the
board, bus, and memory was a quick and cheap hack).

It's important to note that the way DEC nailed CalData was the *same
instruction set on the same bus*, WD did their own bus for their demo.
Also, please remember that at the time, WD was in the chip business.   KO's
reaction this time was different.  Instead of suing, DEC got the design and
started to build and sell them.   WD took the board design, wrote a new set
of microcode based on the USCD Pascal-P machine
<https://en.wikipedia.org/wiki/UCSD_Pascal>, then sold that as a 'system'
called the Pascal MicroEngine
<https://en.wikipedia.org/wiki/Pascal_MicroEngine>, but primarily used it
is the sales demo.

I remember seeing one of the WD Pascal-P systems once when we were at Tek
(along with my favorite named workstation, the Modula based Lilith
<https://en.wikipedia.org/wiki/Lilith_(computer)>).  But I do not think the
Pascal-P (nor Lilith) was very successful.   Also, AMD ultimately won the
bit-slice chip business, as most designers at manufacturers like DEC,
Masscomp, FPS, *et al*. designed their new systems or at least the FP/AP
coprocessors with the 2900 series.

BTW: this is also why a few years later when Ken O'Humundro created another
full computer board with a 68000 on it with his new Able  Computer Corp, he
put it on the QBUS which DEC could not lock up because they did not create
it as WD had.

[-- Attachment #2: Type: text/html, Size: 4997 bytes --]

  parent reply	other threads:[~2020-01-15 14:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-15  3:32 [TUHS] Spacewar at Bell Labs Brian Walden
2020-01-15  4:01 ` Jon Steinhart
2020-01-15  4:50   ` Bakul Shah
2020-01-15  6:17 ` Lars Brinkhoff
2020-01-15  6:34   ` Earl Baugh
2020-01-15  7:10     ` [TUHS] Spacewar at Bell Labs [ really paper tape readers and tangentially related things ] Jon Steinhart
2020-01-15  8:05       ` Earl Baugh
2020-01-15 14:50       ` Clem Cole [this message]
2020-01-15 23:40         ` Al Kossow
2020-01-15 12:29     ` [TUHS] Spacewar at Bell Labs John Foust
2020-01-16  0:17       ` [TUHS] tape reading (was Re: Spacewar at Bell Labs) Al Kossow
2020-01-15 16:46 [TUHS] Spacewar at Bell Labs [ really paper tape readers and tangentially related things ] Noel Chiappa
2020-01-15 18:35 ` Clem Cole
2020-01-29 20:25 ` Dave Horsfall
     [not found]   ` <CABH=_VSPTV-rwu202hYuiXViiBG2ReMnshxUAvD9Lb6HqG4tQQ@mail.gmail.com>
     [not found]     ` <CAC20D2Mr1vqpoAELU3a+4cV7W99uh_76ogGQq28wktJM+onDQA@mail.gmail.com>
2020-02-04 20:26       ` Dave Horsfall

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='CAC20D2M5-Pfxr9VSQ=0AtyYX5x-NEUWzPOC-ZYeSs7AGGw3-fw@mail.gmail.com' \
    --to=clemc@ccc.com \
    --cc=TUHS@minnie.tuhs.org \
    --cc=jon@fourwinds.com \
    /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).