9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: W B Hacker <wbh@conducive.org>
To: lucio@proxima.alt.za,
	Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] /sys/include/ip.h 5c(1)
Date: Fri,  9 Oct 2009 13:59:45 +0800	[thread overview]
Message-ID: <4ACED151.8060901@conducive.org> (raw)
In-Reply-To: <28594535398d30fed785852671a1879a@proxima.alt.za>

lucio@proxima.alt.za wrote:
>>> but by 1990 with microchannel &c. things were much more closed off.
>> i thought only one company ever really made microchannel,
>> and even they weren't terribly in earnest in the end,
>> except on non-PC things like RS6000.
>
> IBM tried to recover control over the PC market by introducing MCA,
> bargaining that public sentiment would swing in their favour.

They might have had that in mind as a secondary reason - but I doubt even that.

The majority within IBM never wanted into that part of the market in the first
place, as it was seen as cannibalizing not only 3XXX terminal sales, but the
entire, highly profitable, big-iron+interface+network+services infrastructure
behind said terminals.

A more immediate need was for something better than ISA bus to meet the needs of
their mid-range servers - some of which would eventually grow - at least per the
manuals - to accomodate expansion trays with slots for over fifty cards (PCI at
that) - more than  double the actually usable max for ISA bus signalling,
moreover over a longer physical plan.

>  They
> could not have been more mistaken, one could easily call this the
> "Betamax error".  As soon as the other PC manufacturers of note (HP,
> Intel, Wang Labs, I forget who else)

Prime movers were HP and Compaq. Earliest small-fry (in those days) to deliver
to 'whomever' wanted a MB was Asus.

Novell Netware servers built on EISA to take advantage of duplexed fast SCSI
controllers and fiber-optic server-to-router TCNS 100 MBps (Arcnet)
interconnects plus 100 MBps TCNS over-coax to the ISA-bus workstations were in
their day rather serious ass-kickers - most especially with Microway add-in
'Number Smasher' CPU+FPU cards.

As is often the case, the link was - and remains - the bottleneck.

> released EISA

.. which, while far more welcome in the field, had slot-count / round-trip
timing limitations that made it technically inferior to MCA, and by a largish
margin, if one wanted a really high slot-count.

 > (which was quickly
> replaced by PCI),

Ditto, absent a 'bridge' chipset that was for a long time largely a DEC
controlled item AND NOT cheap.

Go see how many 'consumer' MB you can find with more than four
all-usable-at-once PCI slots. Hardly common even in 'server grade' MB.

Thankfully much has moved into on-planar silicon long-since, so less need.

> IBM's efforts were nullified.
>
> ++L
>
>

IBM is in many ways an anarchistic loose confederation of competing Divisions.

At sum, they are technically agnostic enough to simply 'follow the money'.

Feudal Microsoft, OTOH, want the money to follow *them*.

;-)

Bill



  reply	other threads:[~2009-10-09  5:59 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<13426df10910080904l5dc8f3d0sc88ec19f28939a99@mail.gmail.com>
2009-10-08 16:17 ` erik quanstrom
2009-10-08 20:55   ` C H Forsyth
2009-10-09  4:00     ` lucio
2009-10-09  5:59       ` W B Hacker [this message]
     [not found] <<4ACED151.8060901@conducive.org>
2009-10-09 15:12 ` erik quanstrom
2009-10-09 18:25   ` lucio
     [not found] <<a17983cabc815054d953faf2696761f2@vitanuova.com>
2009-10-08 22:42 ` erik quanstrom
2009-10-08 23:11   ` Steve Simon
     [not found] <<18f3fced1ebb90eb9c977b47bbcce424@vitanuova.com>
2009-10-06 22:16 ` erik quanstrom
     [not found] <<13426df10910061136w616f7cf9m2b566606663a9f50@mail.gmail.com>
2009-10-06 18:48 ` erik quanstrom
     [not found] <<13426df10910061021g3b033abbia134769baee934d3@mail.gmail.com>
2009-10-06 18:06 ` erik quanstrom
2009-10-06 18:16   ` ron minnich
     [not found] <<85b966411695929ce06c3edd6e3fd77f@plan9.bell-labs.com>
2009-10-06 16:21 ` erik quanstrom
2009-10-06 16:55   ` geoff
2009-10-06 17:21     ` ron minnich
2009-10-06 18:16       ` W B Hacker
2009-10-06 18:36         ` ron minnich
2009-10-06 18:50           ` W B Hacker
2009-10-06 19:13             ` Lyndon Nerenberg - VE6BBM/VE7TFX
2009-10-06 20:03               ` ron minnich
2009-10-06 20:58                 ` Wes Kussmaul
2009-10-06 21:15       ` Aharon Robbins
2009-10-06 21:32         ` ron minnich
2009-10-07 21:07           ` Aharon Robbins
2009-10-06 21:51         ` C H Forsyth
2009-10-07  0:19           ` Dave Eckhardt
2009-10-07  0:24             ` ron minnich
2009-10-07  1:59               ` W B Hacker
2009-10-08 16:04                 ` ron minnich
2009-10-07  7:59         ` Richard Miller
2009-10-08  7:35           ` Skip Tavakkolian
2009-10-08 10:44             ` Richard Miller
     [not found] <<e7fdc0d20910050644x50fc7ad2hc943a075648fdabd@mail.gmail.com>
2009-10-05 13:50 ` erik quanstrom
2009-10-06  5:44   ` Rodriguez Faszanatas
2009-10-06 16:16     ` geoff
2009-10-06 17:18       ` Steve Simon
2009-10-07  6:24       ` Rodriguez Faszanatas
2009-10-10  1:23         ` Ethan Grammatikidis
     [not found] <<e7fdc0d20910050205l7bfaa624m33a32f7a5269ff9a@mail.gmail.com>
2009-10-05 13:16 ` erik quanstrom
2009-10-05 13:44   ` Rodriguez Faszanatas
2009-10-05  9:05 Rodriguez Faszanatas

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=4ACED151.8060901@conducive.org \
    --to=wbh@conducive.org \
    --cc=9fans@9fans.net \
    --cc=lucio@proxima.alt.za \
    /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).