The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Johnny Billquist <bqt@update.uu.se>
To: Clem cole <clemc@ccc.com>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Old mainframe I/O speed
Date: Sat, 23 Jun 2018 13:57:51 +0200	[thread overview]
Message-ID: <04190921-6f50-a643-63f7-41f3bfd0b7e5@update.uu.se> (raw)
In-Reply-To: <EDFBE1AB-2288-49ED-AE30-A5DF504C960F@ccc.com>

On 2018-06-23 13:39, Clem cole wrote:
> PCI was a late 1980s DEC design bus design that where released via license ala the Ethernet experience of  the xerox/dec/Intel blue book.  DEC had mostly learned it lesson that interface standards were better shared.  I’ve forgotten now the name of the person who lead the team.  I did not know him very well.  I can picture his face as I said.

It's just that this sounds so much like the TURBOchannel (not Turbobus 
as I wrote previously). That bus exactly matches your description of 
details, timelines and circumstances, while the PCI, to my knowledge 
don't match at all.

And my recollection also matches Wikipedia, which even gives the PCI 
V1.0 spec being released in 1992. (See 
https://en.wikipedia.org/wiki/Conventional_PCI)

Compare to TURBOchannel: https://en.wikipedia.org/wiki/TURBOchannel

   Johnny


> 
> Sent from my PDP-7 Running UNIX V0 expect things to be almost but not quite.
> 
>> On Jun 23, 2018, at 6:32 AM, Johnny Billquist <bqt@update.uu.se> wrote:
>>
>>> On 2018-06-22 20:01, Clem Cole<clemc@ccc.com> wrote:
>>> 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.
>>
>> Clem, I think I saw you say something similar in an earlier post.
>> To me it sounds as if you are saying that DEC did/designed PCI.
>> Are you sure about that? As far as I know, PCI was designed and created by Intel, and the first users were just plain PC machines.
>> Alpha did eventually also get PCI, but it was not where it started, and DEC had no control at all about PCI being public.
>>
>> Might you have been thinking of Turbobus, Futurebus, or some other thing that DEC did? Or do you have some more information about DEC being the creator of PCI?
>>
>>   Johnny
>>
>> -- 
>> Johnny Billquist                  || "I'm on a bus
>>                                   ||  on a psychedelic trip
>> email: bqt@softjar.se             ||  Reading murder books
>> pdp is alive!                     ||  tryin' to stay hip" - B. Idol


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

  reply	other threads:[~2018-06-23 11:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1.1529690481.3725.tuhs@minnie.tuhs.org>
2018-06-23 10:32 ` [TUHS] Old mainframe I/O speed (was: core) Johnny Billquist
2018-06-23 11:39   ` Clem cole
2018-06-23 11:57     ` Johnny Billquist [this message]
2018-06-23 15:35       ` [TUHS] Old mainframe I/O speed Clem cole
2018-06-23 15:38         ` Clem cole
2018-06-24  7:50   ` [TUHS] Old mainframe I/O speed (was: core) Mutiny
2018-06-27 13:59     ` Clem Cole
2018-06-27 18:43       ` [TUHS] Old mainframe I/O speed Johnny Billquist

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=04190921-6f50-a643-63f7-41f3bfd0b7e5@update.uu.se \
    --to=bqt@update.uu.se \
    --cc=clemc@ccc.com \
    --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).