From: Dean Prichard <dpx@acl.lanl.gov>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] u9fs
Date: Wed, 20 Mar 2002 01:10:56 -0700 [thread overview]
Message-ID: <20020320010427.Q47462-100000@fbsd.acl.lanl.gov> (raw)
In-Reply-To: <20020320071024.C956A19A68@mail.cse.psu.edu>
We ported etherga620.c to the fileserver kernel a while back,
if there is interest it's at:
http://www.acl.lanl.gov/plan9/fs-acenic/
On Tue, 19 Mar 2002, Geoff Collyer wrote:
> Date: Tue, 19 Mar 2002 23:10:18 -0800
> From: Geoff Collyer <geoff@collyer.net>
> Reply-To: 9fans@cse.psu.edu
> To: 9fans@cse.psu.edu
> Subject: Re: [9fans] u9fs
>
> > I agree but support for drivers is a concern.
>
> I've just succeeded in porting a gigabit ethernet driver from the cpu
> kernel to the fs kernel using a bit of scaffolding and a very few
> changes to the original driver. I believe that this can be extended
> to all the other ethernet drivers and maybe some non-ethernet drivers
> and I intend to take a whack at it. (Thus my recent interest in
> ether8139.c.) I also believe that similar scaffolding can ease
> porting of ethernet drivers into 9load, which you really need to make
> a given model of ethernet card useful.
>
next prev parent reply other threads:[~2002-03-20 8:10 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-20 7:10 Geoff Collyer
2002-03-20 7:23 ` Lucio De Re
2002-03-20 8:10 ` Dean Prichard [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-03-30 11:36 arisawa
2008-03-30 12:25 ` arisawa
2003-10-09 14:24 [9fans] U9FS Lucio De Re
2003-02-18 16:38 [9fans] u9fs Ronald G. Minnich
2003-02-18 16:42 ` Russ Cox
2003-02-18 17:12 ` Ronald G. Minnich
2003-02-18 17:18 ` Russ Cox
2003-02-18 16:49 ` nigel
2003-01-28 15:50 Russ Cox
2003-01-31 15:35 ` Axel Belinfante
2003-01-31 16:07 ` Nigel Roles
2003-01-31 16:39 ` Russ Cox
2003-01-31 18:23 ` Axel Belinfante
2003-01-31 18:45 ` Russ Cox
2003-01-31 22:54 ` Axel Belinfante
2002-12-09 8:09 Russ Cox
2002-12-09 7:51 YAMANASHI Takeshi
2002-12-05 17:49 David Swasey
2002-05-05 23:24 [9fans] Bug report Russ Cox
2002-05-05 23:33 ` arisawa
2002-05-05 23:39 ` [9fans] u9fs arisawa
2002-03-24 6:42 Russ Cox
2002-03-23 18:45 nigel
2002-03-23 18:12 Russ Cox
2002-03-24 5:44 ` Martin C.Atkins
2002-03-26 10:45 ` Christopher Nielsen
2002-03-23 10:43 nigel
2002-03-22 13:42 Jean Mehat
2002-03-21 16:19 Russ Cox
2002-03-23 0:40 ` Christopher Nielsen
2002-03-20 22:00 forsyth
2002-03-20 19:31 Russ Cox
2002-03-20 19:31 markp
2002-03-20 19:05 Russ Cox
2002-03-20 19:42 ` skipt
2002-03-21 11:02 ` Peter Canning
2002-03-20 18:40 markp
2002-03-20 9:27 Fco.J.Ballesteros
2002-03-20 7:01 forsyth
2002-03-20 5:15 Russ Cox
2002-03-19 22:33 Russ Cox
2002-03-19 17:19 Russ Cox
2002-03-19 16:39 forsyth
2002-03-19 16:18 anothy
2002-03-19 16:46 ` Dharani Vilwanathan
2002-03-19 22:00 ` Dharani Vilwanathan
2002-03-19 14:03 [9fans] long long warning nigel
2002-03-19 16:07 ` [9fans] u9fs Dharani Vilwanathan
2002-03-19 16:15 ` William Josephson
2002-03-20 4:46 ` Steve Kotsopoulos
2001-01-07 6:08 rob pike
2001-01-07 5:54 rob pike
2001-01-07 6:00 ` Boyd Roberts
2000-07-07 16:16 ianb
2000-07-07 14:46 Ish Rattan
2000-07-07 15:26 ` Steve Kotsopoulos
1999-04-23 11:05 [9fans] U9FS
1999-04-22 16:31 Russ
1999-04-22 8:32
1999-03-18 11:30 Jean
1999-03-17 23:47 Ed
1999-03-17 19:48 Markus
1999-03-17 19:16 Scott
1999-03-17 16:26
1999-03-17 15:07
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=20020320010427.Q47462-100000@fbsd.acl.lanl.gov \
--to=dpx@acl.lanl.gov \
--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).