From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Subject: Re: A new driver for Broadcom bcm5706 Date: Fri, 20 May 2005 17:09:38 -0400 Message-ID: <20050520210938.GA23714@havoc.gtf.org> References: <1116609329.31523.16.camel@rh4> <20050520194220.GA18259@havoc.gtf.org> <428E4DE2.1020002@pobox.com> <428E5185.1070602@candelatech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Michael Chan , davem@davemloft.net, netdev@oss.sgi.com, ffan@broadcom.com, lusinsky@broadcom.com Return-path: To: Ben Greear Content-Disposition: inline In-Reply-To: <428E5185.1070602@candelatech.com> Sender: netdev-bounce@oss.sgi.com Errors-to: netdev-bounce@oss.sgi.com List-Id: netdev.vger.kernel.org On Fri, May 20, 2005 at 02:07:17PM -0700, Ben Greear wrote: > Jeff Garzik wrote: > > > >Note that I only consider a very few of these items, highlighted below, > >to be merge-stoppers. The rest are minor things that can be fixed up at > >leisure. > > Out of curiousity: Is the intended goal to replace tg3 with > this new driver eventually? No, different hardware. > I dig having the chipset manufacturer > solidly behind the driver, like e1000! Clearly you have been asleep :) Broadcom has been contributing actively to tg3. Jeff