I'd like to axe some drivers

Marius Strobl marius at alchemy.franken.de
Mon Nov 24 22:37:42 UTC 2014


On Thu, Nov 20, 2014 at 03:37:10PM -0700, Warner Losh wrote:
> 
> On Nov 20, 2014, at 3:07 PM, John-Mark Gurney <jmg at funkthat.com> 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




More information about the freebsd-arch mailing list