From owner-freebsd-net@FreeBSD.ORG Wed Oct 31 16:28:48 2007 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1CCB516A4CB; Wed, 31 Oct 2007 16:28:48 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from fallbackmx02.syd.optusnet.com.au (fallbackmx02.syd.optusnet.com.au [211.29.133.72]) by mx1.freebsd.org (Postfix) with ESMTP id 9A4F613C480; Wed, 31 Oct 2007 16:28:47 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail34.syd.optusnet.com.au (mail34.syd.optusnet.com.au [211.29.133.218]) by fallbackmx02.syd.optusnet.com.au (8.12.11.20060308/8.12.11) with ESMTP id l9VBjmwV015702; Wed, 31 Oct 2007 22:45:48 +1100 Received: from server.vk2pj.dyndns.org (c220-239-20-82.belrs4.nsw.optusnet.com.au [220.239.20.82]) by mail34.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id l9VBilnq005497 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 31 Oct 2007 22:44:48 +1100 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.1/8.14.1) with ESMTP id l9VBilmf041561; Wed, 31 Oct 2007 22:44:47 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.1/8.14.1/Submit) id l9VBil7J041560; Wed, 31 Oct 2007 22:44:47 +1100 (EST) (envelope-from peter) Date: Wed, 31 Oct 2007 22:44:47 +1100 From: Peter Jeremy To: Jack Vogel Message-ID: <20071031114447.GC70883@server.vk2pj.dyndns.org> References: <2a41acea0710291045m6f1d2acw78c26a455ea3894d@mail.gmail.com> <2a41acea0710301001k60442b26uae186209ac484780@mail.gmail.com> <4727F13F.1030607@samsco.org> <20071031081638.GA13564@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="MXxcbiX/Q4+iy5U7" Content-Disposition: inline In-Reply-To: <20071031081638.GA13564@eos.sc1.parodius.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.16 (2007-06-09) Cc: "freebsd-net@freebsd.org" , FreeBSD Current , FreeBSD Stable List Subject: Re: RFC: Evolution of the em driver X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 16:28:48 -0000 --MXxcbiX/Q4+iy5U7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 31, 2007 at 01:16:39AM -0700, Jeremy Chadwick wrote: >For what it's worth, I agree with Scott. I'd rather see a new and >separate driver (presumably igb(4)) than a "hacked up" em(4) driver >trying to handle tons of IC revisions. A good example of the insanity >the latter causes is nve(4) vs. nfe(4). :-) A separate driver is probably cleaner. I'll just make the comment that if a separate driver is written, there needs to be a clear way for an end user to identify what driver is needed/preferred for his chipset. We already have cases like re(4)/rl(4) and sym(4)/ncr(4) where some chips are supported by two drivers - though generally only one driver fully supports the chip. This sort of thing is confusing for end users. --=20 Peter --MXxcbiX/Q4+iy5U7 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHKGqv/opHv/APuIcRArIoAJoCNSMbMIwqTKH+lEbbrb5sC1PjZwCglsd7 HrZHfgxfPlO7uBKfY4e1XkI= =8p9Q -----END PGP SIGNATURE----- --MXxcbiX/Q4+iy5U7--