From: uriel@cat-v.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fs kernel ether driver update
Date: Wed, 1 Mar 2006 13:09:39 +0100 [thread overview]
Message-ID: <7303fddbc49bc3ef69e60b41d677c3c8@cat-v.org> (raw)
In-Reply-To: <f121a1be35a4266ec8b20b5892c8e2df@collyer.net>
I'm sure there is a good reason for this, but I was wondering what would
it take for the fs kernel and the standard kernel to shared the drivers source.
Also would be nice if Inferno and standard Plan 9 kernel drivers lived in a single
source tree.
uriel
> I just put up a second file server for testing. This one has a
> built-in SiS ethernet and I was able to exercise it; it seems to be
> fine with the current driver. (I did have to change the boot programs
> to recognise the SiS interface, and those changes have been submitted
> as a patch, and still require one to specify ea= in plan9.ini for SiS
> interfaces.)
>
> I've also exercised an i82557 with a new driver. It seems to be fine,
> so I've copied that driver to
> /n/sources/plan9/sys/src/fs/pc/ether82557.c. Like ether83815.c,
> ether8139.c, etherdp83820.c, and etherigbe.c, this new 82557 driver
> will work unmodified in cpu kernels that have /sys/src/9/pc/compat.h.
>
> There are more driver updates coming as I get the chance to verify
> that the new drivers work correctly.
next prev parent reply other threads:[~2006-03-01 12:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 8:25 geoff
2006-03-01 9:03 ` Federico Benavento
2006-03-01 9:15 ` geoff
2006-03-01 9:17 ` Federico Benavento
2006-03-01 9:20 ` geoff
2006-03-01 12:09 ` uriel [this message]
2006-03-02 6:46 ` geoff
2006-03-02 9:35 ` Charles Forsyth
2006-03-01 10:28 geoff
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=7303fddbc49bc3ef69e60b41d677c3c8@cat-v.org \
--to=uriel@cat-v.org \
--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).