Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.mel.connect.com.au!news.mel.aone.net.au!imci4!newsfeed.internetmci.com!howland.erols.net!news-peer.gsl.net!news.gsl.net!news-res.gsl.net!news.gsl.net!portc01.blue.aol.com!newsstand.cit.cornell.edu!news.acsu.buffalo.edu!news.drenet.dnd.ca!crc-news.doc.ca!nott!bcarh189.bnr.ca!nrchh45.rich.nt.com!ferret.ocunix.on.ca!resurrect From: "Jordan K. Hubbard" <jkh@FreeBSD.org> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Skeleton for network device drivers Date: Sat, 21 Sep 1996 21:35:33 -0700 Organization: Walnut Creek CDROM Lines: 15 Message-ID: <R.3244C215.1CFBAE39@FreeBSD.org> References: <51ru2l$rm@sanson.dit.upm.es> NNTP-Posting-Host: time.cdrom.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 3.0 (X11; I; FreeBSD 2.2-CURRENT i386) To: Javier Martin Rueda <jmrueda@diatel.upm.es> CC: davidg@freebsd.org Reposting article removed by rogue canceller. Javier Martin Rueda wrote: > > Is there a skeleton for network device drivers? I plan > to write one for Intel Etherexpress Pro, and till now > I've just used some other card's driver as a guide, > but it would be nice if there was something where you > could just "fill in the blanks" with code specific to > the particular hardware you are programming. This has been talked about several times, but to my knowledge no one has actaully done it yet. Everyone is in agreement that it would be a Good Thing to have such a generic driver skeleton, however! :) -- - Jordan Hubbard President, FreeBSD Project