From: Clem Cole <clemc@ccc.com>
To: Mutiny <mutiny.mutiny@rediffmail.com>
Cc: "tuhs@minnie.tuhs.org" <tuhs@minnie.tuhs.org>,
Johnny Billquist <bqt@update.uu.se>
Subject: Re: [TUHS] Old mainframe I/O speed (was: core)
Date: Wed, 27 Jun 2018 09:59:43 -0400 [thread overview]
Message-ID: <CAC20D2MMQKg6wnTCtM9WsVtt+BuCf2a0Jfhkk5NpZtq1Hx25Jw@mail.gmail.com> (raw)
In-Reply-To: <1529749991.S.4934.17164.f4-234-225.1529826641.32118@webmail.rediffmail.com>
[-- Attachment #1: Type: text/plain, Size: 590 bytes --]
Don't you love Wikipedia. As it has been said by others follow the money
(or in this case the law suites)....
ᐧ
On Sun, Jun 24, 2018 at 3:50 AM, Mutiny <mutiny.mutiny@rediffmail.com>
wrote:
> >From: Johnny Billquist <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
>
[-- Attachment #2: Type: text/html, Size: 1519 bytes --]
next prev parent reply other threads:[~2018-06-27 14:00 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[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-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 [this message]
2018-06-27 18:43 ` [TUHS] Old mainframe I/O speed Johnny Billquist
2018-06-24 18:49 [TUHS] Old mainframe I/O speed (was: core) Norman Wilson
-- strict thread matches above, loose matches on Subject: below --
2018-06-24 18:49 Norman Wilson
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-22 13:11 Noel Chiappa
2018-06-22 17:49 ` Erik E. Fair
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
2018-06-23 6:08 ` Dave Horsfall
2018-06-23 17:02 ` ron minnich
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=CAC20D2MMQKg6wnTCtM9WsVtt+BuCf2a0Jfhkk5NpZtq1Hx25Jw@mail.gmail.com \
--to=clemc@ccc.com \
--cc=bqt@update.uu.se \
--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).