From owner-freebsd-current@FreeBSD.ORG  Sun Sep  5 21:49:49 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 11A4216A4CE; Sun,  5 Sep 2004 21:49:49 +0000 (GMT)
Received: from zaphod.nitro.dk (port324.ds1-khk.adsl.cybercity.dk
	[212.242.113.79])	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 32E0A43D48; Sun,  5 Sep 2004 21:49:48 +0000 (GMT)
	(envelope-from simon@zaphod.nitro.dk)
Received: by zaphod.nitro.dk (Postfix, from userid 3000)
	id 1449E11AB6; Sun,  5 Sep 2004 23:49:44 +0200 (CEST)
Date: Sun, 5 Sep 2004 23:49:43 +0200
From: "Simon L. Nielsen" <simon@FreeBSD.org>
To: freebsd-current@freebsd.org
Message-ID: <20040905214943.GA759@zaphod.nitro.dk>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="vtzGhvizbBRQ85DL"
Content-Disposition: inline
User-Agent: Mutt/1.5.6i
cc: pdeuskar@FreeBSD.org
cc: tackerman@FreeBSD.org
cc: Jonathan Lemon <jlemon@FreeBSD.org>
Subject: Deprication of the gx(4) driver - superseded by em(4) ?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Sep 2004 21:49:49 -0000


--vtzGhvizbBRQ85DL
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hello

As far as I know all devices supported by gx(4) is also supported by
em(4).  The em(4) driver also supports other devices and is actively
maintained, so is there really a need to keep gx(4) around?

I ask now since as far as I know the normal/"correct" policy for
removal of a driver would be to mark it deprecated in one major
release and then remove it in the next one.  So, if we mark it
deprecated in 5.X now before 5.3, it could be removed in 6-CURRENT.

So, am I missing some reason to keep gx(4) around... ?

--=20
Simon L. Nielsen
FreeBSD Documentation Team

--vtzGhvizbBRQ85DL
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (FreeBSD)

iD8DBQFBO4n3h9pcDSc1mlERAhQKAJ4/ix8axGTSqztvRau/nyOhl73A2gCcDBDZ
yIME8SpQ8isBRs0miZS0sYo=
=Q2j3
-----END PGP SIGNATURE-----

--vtzGhvizbBRQ85DL--