From: "David S. Miller" <davem@dm.cobaltmicro.com>
To: ultralinux@vger.kernel.org
Subject: Re: Ultra AXmp
Date: Mon, 13 Jul 1998 06:38:56 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-90222358531021@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-90222358531013@msgid-missing>
Date: Mon, 13 Jul 1998 02:27:27 -0400
From: Qiru Zhou <qzhou@research.bell-labs.com>
I am not sure what other PC PCI card that I can put there. We have
SGI O2s with PCI slots. But I almost cannot put any PCI card from
retail store, since it is not compatible with O2 or there is simply
no driver for it (you may develop your own, if you really want.).
Whats the problem? I have off the shelf 3com and Tulip PCI ethernet
cards, and off the shelf Adaptec and NCR scsi cards, in my UltraSPARC
PCI systems here. (I've also played around with a Matrox M-II card in
them as well) In fact one of my PCI Ultra's is a router into a test
subnet I have, using a 4-port Tulip card.
Just about any existing Linux PCI driver can be made to work in about
15 minutes of hacking done by one of the developers who work on the
port.
All your "open architecture" claims are false as well, you can get
complete documentation on Sun's bus, cpu, and device programming
interfaces on the PCI Ultra's and timing specs are available as well.
As far as I've seen, any PCI card I've thrown into one of my Ultra's
was found on the bus and would work just fine once I did the driver
porting work. The only part where anything is problematic is where a
card has complex x86 firmware, and this matters really only for a
device which you'd like to boot off of. But all the Ultra/PCI systems
have on board bootable devices with open-firmware on them so it's a
non-issue.
So don't give the PCI Ultra's and the O2's a bad rap just because the
support list Solaris and IRIX have are so small for off the shelf PC
cards. It is not an indication of a sub-standard PCI bus
implementation at all, it's just plain lack of OS support from these
vendors, no more no less.
Later,
David S. Miller
davem@dm.cobaltmicro.com
next prev parent reply other threads:[~1998-07-13 6:38 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-07-11 18:36 Ultra AXmp Bob Drzyzgula
1998-07-12 1:56 ` David S. Miller
1998-07-12 2:21 ` Matthew Jacob
1998-07-12 2:29 ` David S. Miller
1998-07-12 5:02 ` Matthew Jacob
1998-07-12 12:54 ` Douglas Eadline
1998-07-12 23:59 ` Bob Drzyzgula
1998-07-13 6:27 ` Qiru Zhou
1998-07-13 6:38 ` David S. Miller [this message]
1998-07-13 10:40 ` Bob Drzyzgula
1998-07-13 12:09 ` Xavier Beaudouin
1998-07-13 13:59 ` Robert G. Brown
1998-07-13 14:29 ` Robert HYATT
1998-07-13 14:54 ` Matthew Jacob
1998-07-13 14:56 ` Matthew Jacob
1998-07-13 14:59 ` Matti Aarnio
1998-07-13 15:24 ` Robert HYATT
1998-07-13 15:38 ` Robert HYATT
1998-07-13 16:56 ` Robert G. Brown
1998-07-13 17:04 ` Robert G. Brown
1998-07-13 17:13 ` Lawrence D. Lopez
1998-07-13 17:26 ` Mike
1998-07-14 1:44 ` Shannon
1998-07-14 7:00 ` David S. Miller
1998-07-14 18:07 ` Douglas Eadline
1998-07-14 23:23 ` Bob Drzyzgula
1998-07-15 3:31 ` Dave Wreski
1998-07-15 8:07 ` Ward Deng
1998-07-15 11:14 ` Bob Drzyzgula
1998-07-15 11:27 ` David S. Miller
1998-07-15 15:54 ` Robert G. Brown
1998-07-15 17:11 ` Robert G. Brown
1998-07-15 23:22 ` Luis Ponce de Leao
1998-07-21 23:29 ` Ward Deng
1998-07-25 23:34 ` Ward Deng
1998-07-26 0:02 ` Ward Fenton
1998-07-26 0:45 ` Rich Martin
1998-07-26 3:34 ` Bob Drzyzgula
1998-07-26 4:00 ` Ward Deng
1998-07-26 4:29 ` Ward Deng
1998-07-26 12:29 ` Bob Drzyzgula
1998-07-26 13:57 ` Douglas Eadline
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=marc-linux-ultrasparc-90222358531021@msgid-missing \
--to=davem@dm.cobaltmicro.com \
--cc=ultralinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.