From: Julian Back <jback@cix.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Weird bug.
Date: Tue, 13 Mar 2001 10:02:45 +0000 [thread overview]
Message-ID: <memo.20010312225321.924A@jback.compulink.co.uk> (raw)
In-Reply-To: <20010312154951.5F453199ED@mail.cse.psu.edu>
In article <20010312154951.5F453199ED@mail.cse.psu.edu>,
jmk@plan9.bell-labs.com () wrote:
> On Mon Mar 12 08:27:55 EST 2001, DAGwyn@null.net wrote:
> > jmk@plan9.bell-labs.com wrote:
> > > Secondly, the SB16 doesn't show up in the iomap output because the
> > > driver doesn't call the routine to register the space it uses.
> > > That's a bug we should fix but shouldn't affect the operation of the
> > > driver (assuming there is no actual clash with another device).
> >
> > Hm, with a PCI-only motherboard, which is about all one can buy
> > these days, the nearest thing to a Plan 9-suppored SoundBlaster
> > seems to be the SoundBlaster-16 PCI, which like everything else
> > for PCI these days is plug-and-play. Is there some way to make
> > this work on Plan 9?
> >
> > Also, does the 3C905C-TM (PCI) work a a Plan 9 Ethernet card?
> >
> > It's getting harder and harder to build an ISA PC..
>
> If it is truly an SB-16 compatible then it's a matter of adding a
> handful of lines to scan the PCI bus for the card to make it work.
> But it can't really be compatible because the DMA must be completely
> different.
AFAIK the SB16-PCI is not SB16 compatible. It's based on an ES1371 chip.
The Linux driver for this card is completely different to the SB16 ISA
driver.
Julian
>
> The 3Com driver in the distribution requires some small fixes
> to work with the 905C, Jean Mehat <jm@ai.univ-paris8.fr> has them.
next prev parent reply other threads:[~2001-03-13 10:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-12 15:49 jmk
2001-03-13 10:02 ` Julian Back [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-11 17:12 jmk
2001-03-12 9:58 ` Douglas A. Gwyn
2001-03-12 21:30 ` Eric Dorman
2001-03-10 5:08 jmk
2001-03-11 6:40 ` Eric Dorman
2001-03-10 0:40 Russ Cox
2001-03-10 3:23 ` Eric Dorman
2001-03-09 23:53 Eric Dorman
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=memo.20010312225321.924A@jback.compulink.co.uk \
--to=jback@cix.co.uk \
--cc=9fans@cse.psu.edu \
/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).