From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ether probing and 9load
Date: Thu, 14 Mar 2002 22:12:14 -0500 [thread overview]
Message-ID: <aa0c6b78584083cb00496963f15942c3@plan9.bell-labs.com> (raw)
On Thu Mar 14 17:39:14 EST 2002, andrey@lanl.gov wrote:
> ...
> the question is: is there an easy way to probe for all ethercards[] or
> should we stick with the 'in-house' solution, which is
> strcpy(ctlr->type, "rtl8139"); in etherinit()
> ...
it's trivial to make 9load/plan9 scan for and find pnp devices such
as pci ethernet cards, we've been doing that internally. it's too fraught
with problems to poke around randomly for isa devices. in fact, we used
to do that and it caused such problems we created plan9.ini to get
round it. of course, that was before there were pnp devices (other than
eisa).
next reply other threads:[~2002-03-15 3:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 3:12 jmk [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-14 22:40 andrey mirtchovski
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=aa0c6b78584083cb00496963f15942c3@plan9.bell-labs.com \
--to=jmk@plan9.bell-labs.com \
--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).