Date: Wed, 18 Apr 2007 11:00:32 +1000 From: Alan Garfield <alan@fromorbit.com> To: Yar Tikhiy <yar@comp.chem.msu.su> Cc: freebsd-hackers@freebsd.org Subject: Re: RFI: Ethernet driver ported from Linux Message-ID: <1176858032.4426.3.camel@hiro.auspc.com.au> In-Reply-To: <20070417171622.GB95814@comp.chem.msu.su> References: <1176096815.4064.6.camel@hiro.auspc.com.au> <20070409.222300.-1350498722.imp@bsdimp.com> <20070417171622.GB95814@comp.chem.msu.su>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2007-04-17 at 21:16 +0400, Yar Tikhiy wrote: > > In addition to the other advise, you might also look at if_ed.c. It > > is a little complicated since it talks to real hardware, and that > > hardware is, ummm, a little icky. > > That little thing Alan is writing a driver for should be simpler > and clearer than the ed(4) hw, so Alan's driver will be a source > of knowledge itself when it's complete. :-) It can be a good > companion for if_edsc, as the latter doesn't work with hardware at > all and fails to illustrate some important points due to that. Thanks for your comments. :) I just wish I could figure out what all this rtrequest/arp stuff was about so I could finish it. :) If anyone wants to look at the code just pop me an email. It's based on a GPL driver (although there isn't anything really left of it other than #defines and a few comments, the code is all new) so I don't know how/if I can get it added to FreeBSD HEAD. Anyway, back to figuring out arp. UGH! -A.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1176858032.4426.3.camel>