From: Clem Cole <clemc@ccc.com>
To: "Erik E. Fair" <fair-tuhs@netbsd.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Old mainframe I/O speed (was: core)
Date: Fri, 22 Jun 2018 09:32:17 -0400 [thread overview]
Message-ID: <CAC20D2NSjx3iD86S2g9zykP=EawMDTT2+741hVCrkPPfpbWGkA@mail.gmail.com> (raw)
In-Reply-To: <27914.1529645559@cesium.clock.org>
[-- Attachment #1: Type: text/plain, Size: 1880 bytes --]
On Fri, Jun 22, 2018 at 1:32 AM, Erik E. Fair <fair-tuhs@netbsd.org> wrote:
> The VAX 8800 was also the advent of the DEC BI bus attempt to lock
> third-party I/O devices out of the VAX market and prevent "unauthorized"
> competition with their own overpriced and underperforming I/O devices.
>
Interesting story on the BI. My friend, Dave Cane who had been #2 on the
780 and lead the 750 project was the primary force behind the BI and
developed by the team in the laboratory products division (LDP). The
whole idea behind BI was, BI was supposed to be (i.e. designed as) an
'open' bus and DEC was originally going to license the driver chips to a
number of 3rd parties (I believe Western Digital, Mostek, TI). The whole
idea was to create a 3rd party market for I/O devices for LDP. By making
sure everyone use the same interface chips, their was a reasonable belief
that the boards would not break bus protocol and have some of the issues
that they had had with Omibus and Unibus.
But ... once the BI was completed and actually put into the 8800 and the
main line system, DEC central marketing made it private and locked up.
Dave quit (his resignation letter was sent out on the engining mailing
list -- KO and GB were not happy -- and one of the thing he sites is the
fact that he thought taking the BI private was going to be bad).
FYI: Masscomp was formed shortly there after (my mostly ex-LDP, 750 and VMS
folks) and Dave used MultiBus and later VMEbus for the I/O (but he did a
private SMI like split transaction memory bus).
One of the other BI people, who's name now escapes me, although I can see
his face in my mind, maybe I'll think of it later), would go on to do the
PCI for Alpha a couple of years later. As I said, DEC did manage to get
that one public, after the BI was made private as Erik points out.
ᐧ
[-- Attachment #2: Type: text/html, Size: 3155 bytes --]
next prev parent reply other threads:[~2018-06-22 13:33 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 15:25 [TUHS] core Noel Chiappa
2018-06-15 23:05 ` Dave Horsfall
2018-06-15 23:22 ` Lyndon Nerenberg
2018-06-16 6:36 ` Dave Horsfall
2018-06-16 19:07 ` Clem Cole
2018-06-18 9:25 ` Tim Bradshaw
2018-06-19 20:45 ` Peter Jeremy
2018-06-19 22:55 ` David Arnold
2018-06-20 5:04 ` Peter Jeremy
2018-06-20 5:41 ` Warner Losh
2018-06-20 8:10 ` [TUHS] Old mainframe I/O speed (was: core) Greg 'groggy' Lehey
2018-06-20 16:33 ` Paul Winalski
2018-06-21 3:05 ` Peter Jeremy
2018-06-21 14:00 ` Paul Winalski
2018-06-21 14:49 ` Arrigo Triulzi
2018-06-21 20:39 ` Paul Winalski
2018-06-22 5:32 ` Erik E. Fair
2018-06-22 13:32 ` Clem Cole [this message]
2018-06-23 6:08 ` Dave Horsfall
2018-06-23 17:02 ` ron minnich
2018-06-22 13:11 Noel Chiappa
2018-06-22 17:49 ` Erik E. Fair
[not found] <mailman.1.1529690481.3725.tuhs@minnie.tuhs.org>
2018-06-23 10:32 ` Johnny Billquist
2018-06-23 11:39 ` Clem cole
2018-06-24 7:50 ` Mutiny
2018-06-27 13:59 ` Clem Cole
2018-06-24 3:14 Norman Wilson
2018-06-24 13:03 ` Paul Winalski
2018-06-24 14:41 ` Lawrence Stewart
2018-06-24 15:47 ` Arthur Krewat
2018-06-24 18:49 Norman Wilson
2018-06-24 18:49 Norman Wilson
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='CAC20D2NSjx3iD86S2g9zykP=EawMDTT2+741hVCrkPPfpbWGkA@mail.gmail.com' \
--to=clemc@ccc.com \
--cc=fair-tuhs@netbsd.org \
--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).