Date: Fri, 23 Jul 1999 10:47:50 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> To: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com> Cc: phk@critter.freebsd.dk (Poul-Henning Kamp), mike@smith.net.au (Mike Smith), jeremyp@gsmx07.alcatel.com.au (Peter Jeremy), cvs-all@FreeBSD.ORG, cvs-committers@FreeBSD.ORG, jkh@FreeBSD.ORG Subject: Re: cvs commit: src/release/sysinstall tcpip.c Message-ID: <199907231747.KAA26657@apollo.backplane.com> References: <199907231734.KAA88336@gndrsh.aac.dev.com>
next in thread | previous in thread | raw e-mail | index | archive | help
:>
:> I would advocate the ether_input API. I have never heard of a 3rd
:> party ethernet driver, and considering the number of changes we
:> introduce between 3.x and 4.x anyway, driver compatibility is
:> already pretty much shot anyway, so I think we should fix the
:> API to do it "right" rather than fight for a compatibility which
:> is at best of only marginal advantage to anybody.
:
:What about ET Inc's wan cards, if I recall Dennis screams everytime
:FreeBSD changes the network layer API. Though moving bpf up a layer
:would simplfy things for him in the long run (no reason to ship 2
:driver .o files, one without BPF and one with), he'll still probably
:complain.
:
:These changes would probably effect all network devices...
:
:So there you have it, your never heard of 3rd party driver.
:
:--
:Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.dnsmgr.net
Well, this is for current, right?
I say that if we are going to make changes to the API that will make
writing device drivers easier in the long run, now is the best time
to do it.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199907231747.KAA26657>