From: Johnny Billquist <bqt@update.uu.se>
To: Clem Cole <clemc@ccc.com>, Mutiny <mutiny.mutiny@rediffmail.com>
Cc: "tuhs@minnie.tuhs.org" <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Old mainframe I/O speed
Date: Wed, 27 Jun 2018 20:43:56 +0200 [thread overview]
Message-ID: <37241c8b-dc57-e720-dd63-aaff8dcb9bd3@update.uu.se> (raw)
In-Reply-To: <CAC20D2MMQKg6wnTCtM9WsVtt+BuCf2a0Jfhkk5NpZtq1Hx25Jw@mail.gmail.com>
On 2018-06-27 15:59, Clem Cole wrote:
> Don't you love Wikipedia. As it has been said by others follow the
> money (or in this case the law suites)....
Well, in all fairness, what you are now claiming is that Intel ripped
off DEC IP when designing PCI. That is not the same thing as claiming
that DEC designed PCI themselves.
I have not really looked into details on TURBOchannel compared to PCI to
say if they are related in some way, but they are definitely not
identical. So PCI did originate within Intel, and the Wikipedia article
is correct (and even if you point fingers at Wikipedia for various
issues about money and whatnot, you most of the time do have source
references that can be checked, and which are not fabricated by Wikipedia.)
And yes, Intel certainly ripped off DEC IP a couple of times, so I would
not be surprised if this turns out to be another example. But DEC did
not design PCI.
Johnny
> ᐧ
>
> On Sun, Jun 24, 2018 at 3:50 AM, Mutiny <mutiny.mutiny@rediffmail.com
> <mailto:mutiny.mutiny@rediffmail.com>> wrote:
>
> >From: Johnny Billquist <bqt@update.uu.se <mailto:bqt@update.uu.se>>
> >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.
>
> Work on PCI began at Intel's Architecture Development Lab c. 1990.
> https://en.wikipedia.org/wiki/Conventional_PCI#History
> <https://en.wikipedia.org/wiki/Conventional_PCI#History>
>
>
--
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
prev parent reply other threads:[~2018-06-27 18:44 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 ` [TUHS] Old mainframe I/O speed Johnny Billquist
2018-06-23 15:35 ` 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 ` 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=37241c8b-dc57-e720-dd63-aaff8dcb9bd3@update.uu.se \
--to=bqt@update.uu.se \
--cc=clemc@ccc.com \
--cc=mutiny.mutiny@rediffmail.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).