Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site wdl1.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxj!houxm!vax135!cornell!uw-beaver!tektronix!hplabs!hpda!fortune!wdl1!wunder
From: wunder@wdl1.UUCP
Newsgroups: net.arch
Subject: Re: time for a RISCy bus
Message-ID: <219@wdl1.UUCP>
Date: Thu, 24-Jan-85 01:14:40 EST
Article-I.D.: wdl1.219
Posted: Thu Jan 24 01:14:40 1985
Date-Received: Sun, 27-Jan-85 04:47:02 EST
Sender: notes@wdl1.UUCP
Organization: Ford Aerospace, Western Development Laboratories
Lines: 18
Nf-ID: #R:utzoo:-494000:wdl1:2100002:000:735
Nf-From: wdl1!wunder    Jan 23 20:37:00 1985

One of the sub-buses in Multibus II is a serial "skinny bus".  Since
most (all?) Multibus II traffic is in packets, a CSMA/CD packet
bus works just fine.  I think that the serial bus is called iSSB
for Serial System Bus.  The "fat bus" part is called iPSB.

There was a session on VLSI network interfaces at Spring CompCon 82,
and iNTEL made it very clear that their chip would be able to work
on a variety of CSMA/CD nets (including Ethernet) at different data
rates.  They described a two-wire serial system bus as one possible
application.

VMEbus also has a serial sub-bus defined, but I doubt that anyone
will ever bother to implement it.

w underwood

PS:  Personally, I am getting a little tired of this iBFD naming convention.