From: Peter Jones <pjones@redhat.com>
To: ultralinux@vger.kernel.org
Subject: Re: tulip under linux sparc?
Date: Wed, 06 Oct 1999 14:53:46 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-93922345621784@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-93909789806109@msgid-missing>
On Tue, 5 Oct 1999, Bob Drzyzgula wrote:
> I think that the issue is that, to be functional at boot time, there
> has to be OBP driver code for the card *either* in the card *or* in
> the system OBP. Sun's stock OBP has driver code for some basic PCI
> cards, but it could not be described as "wide support for most cards".
> Manufacturers that wish to sell in the SPARC/PCI market have the
> option of writing their own OBP driver and putting it in ROM on the
> card in a standard manner; in that case the system OBP will find it
> and can branch to that code at boot time. Adaptec does this with some
> of their SCSI cards, for example. But once a system is up and running,
> the ability of an OS to use the card is a function of the OS. It may
> be the case that Solaris won't use cards that aren't reported by the
> OBP, but Linux can go ahead and probe for cards that the OBP didn't
> recognize. (Did I get this right, Dave?)
Pretty much, yeah. Most PCI cards should work, With a few minor
exceptions, such as _old_ Buslogic scsi boards tend to make my u10 not get
_to_ openboot, some cards do some rather obnoxious things with their DMA,
like ess Maestro's and a couple of other sound cards i've got.
But yeah, there isn't any good reason a vendor can't make a PCI card that
works fine on a sparc and an x86 (and an alpha, and a powerpc). OBP
support just affects doing things from the firmware, like booting the
device.
-- Peter
"Who's scruffy-looking?"
-- Solo
next prev parent reply other threads:[~1999-10-06 14:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-05 4:34 tulip under linux sparc? David S. Miller
1999-10-05 4:35 ` nick
1999-10-05 13:10 ` David Cooley
1999-10-05 13:22 ` David S. Miller
1999-10-05 15:04 ` David Cooley
1999-10-05 15:11 ` David S. Miller
1999-10-05 15:41 ` Bob Drzyzgula
1999-10-06 14:53 ` Peter Jones [this message]
1999-10-10 5:43 ` Steve Dunham
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-93922345621784@msgid-missing \
--to=pjones@redhat.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.