From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 18 07:45:02 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0412316A400 for ; Wed, 18 Apr 2007 07:45:02 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.freebsd.org (Postfix) with ESMTP id 600BB13C458 for ; Wed, 18 Apr 2007 07:45:01 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.4/8.13.4) with ESMTP id l3I7itT6038331; Wed, 18 Apr 2007 11:44:55 +0400 (MSD) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.4/8.13.4/Submit) id l3I7itFn038330; Wed, 18 Apr 2007 11:44:55 +0400 (MSD) (envelope-from yar) Date: Wed, 18 Apr 2007 11:44:55 +0400 From: Yar Tikhiy To: Alan Garfield Message-ID: <20070418074455.GD36635@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> <1176858032.4426.3.camel@hiro.auspc.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1176858032.4426.3.camel@hiro.auspc.com.au> User-Agent: Mutt/1.5.9i Cc: freebsd-hackers@freebsd.org Subject: Re: RFI: Ethernet driver ported from Linux X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Apr 2007 07:45:02 -0000 On Wed, Apr 18, 2007 at 11:00:32AM +1000, Alan Garfield wrote: > 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! As a rule, an Ethernet driver needn't worry about ARP by itself because ARP has own separate module in the network stack. Does your driver have a partucular reason to? -- Yar