From: forsyth@caldo.demon.co.uk forsyth@caldo.demon.co.uk
Subject: [9fans] looking for dec21143 ether driver for 9pc
Date: Tue, 23 Feb 1999 10:15:54 +0000 [thread overview]
Message-ID: <19990223101554.RxEWTZ89uSTvIrHL_AgomTyJBHBspyi-bs0eAOWsL9M@z> (raw)
>>Linux tulip.c and de4x5.c scared me off...
fortunately, for the 2114x jmk did all the hard work as usual,
and a few months ago ngr ported it back to plan9
and added PNIC support (Netgear FA310TX),
which might have been more hard work.
it was done so as to allow the use of the original plan9
drivers as well as (slightly modified) brazil ones.
(the brazil i/o interface is different.)
i've been using the result for several months, at both
10 and 100 mbits -- on the Netgear FA310TX, though, not a 2114x --
and ported back the 3c905 driver as well, which
i've been using for about a month at work,
on both a 10/100 hub and a 10/100 switch. the week before last
i ported the brazil 8390 drivers (for cards i can check).
all we need to do is to boddle the result.
next reply other threads:[~1999-02-23 10:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-23 10:15 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-02-23 4:30 iwane
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=19990223101554.RxEWTZ89uSTvIrHL_AgomTyJBHBspyi-bs0eAOWsL9M@z \
--to=forsyth@caldo.demon.co.uk \
/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).