From owner-freebsd-arch@FreeBSD.ORG Mon Nov 24 22:37:42 2014 Return-Path: Delivered-To: arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CBD15697 for ; Mon, 24 Nov 2014 22:37:42 +0000 (UTC) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "alchemy.franken.de", Issuer "alchemy.franken.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 59125DA1 for ; Mon, 24 Nov 2014 22:37:41 +0000 (UTC) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.9/8.14.9/ALCHEMY.FRANKEN.DE) with ESMTP id sAOMbVLD054705 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 24 Nov 2014 23:37:32 +0100 (CET) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.9/8.14.9/Submit) id sAOMbVhX054704; Mon, 24 Nov 2014 23:37:31 +0100 (CET) (envelope-from marius) Date: Mon, 24 Nov 2014 23:37:31 +0100 From: Marius Strobl To: Warner Losh Subject: Re: I'd like to axe some drivers Message-ID: <20141124223731.GA54578@alchemy.franken.de> References: <201411201631.27556.jhb@freebsd.org> <20141120220752.GI24601@funkthat.com> <573D346B-3AB8-4EC7-A03F-1B2B1291A5BC@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <573D346B-3AB8-4EC7-A03F-1B2B1291A5BC@bsdimp.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (alchemy.franken.de [0.0.0.0]); Mon, 24 Nov 2014 23:37:32 +0100 (CET) Cc: arch@freebsd.org, John-Mark Gurney X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Nov 2014 22:37:42 -0000 On Thu, Nov 20, 2014 at 03:37:10PM -0700, Warner Losh wrote: > > On Nov 20, 2014, at 3:07 PM, John-Mark Gurney wrote: > > > I'm fine w/ removing these... Should we do some house cleaning on > > amd64's GENERIC too? > > > > amd64's GENERIC has a lot of ISA or 100Mbit ethernet cards that are > > clearly not going to be used on these machines... > > > > My recommended list to remove: > > ae, bfe, dc, fxp, hme?, pcn, rl, tx, vr, wb, xl, cs, ed, ex, ep, fe, > > sn, xe > > All the PC Card ones (cs, ed, ex, ep, fe, sn, xe) are no brainers to remove > from GENERIC. > > hme is a Sparc-centric card, so can go. > FYI, cas(4) and hme(4) are in the x86 GENERIC kernel config files as the quad-port NIC variants driven by them aren't uncommon to be used with pfSense, which likely is due to the fact that these cards are cheap to get these days and someone writing the following article: http://www.glitchwrks.com/2012/08/03/Quad-Port-PCI-Ethernet-Roundup/ Now why the pfSense project can't have its own kernel config or why modules aren't an alternative I don't really know. Based on some mails I got it seems like the pfSense developers are reluctant to diverging from upstream regarding the former and their users have problems with kernel modules - at least in practice - as pfSense ships without modules and, thus, have to be fetch from FreeBSD install bits, though. Marius