Date: Wed, 03 Jan 2007 20:34:03 -0700 (MST) From: "M. Warner Losh" <imp@bsdimp.com> To: uspoerlein@gmail.com Cc: arch@FreeBSD.org Subject: Re: usb modems and com devices into GENERIC Message-ID: <20070103.203403.63053841.imp@bsdimp.com> In-Reply-To: <20070103205841.GB85200@roadrunner.q.local> References: <20070101.113801.818271922.imp@bsdimp.com> <20070103205841.GB85200@roadrunner.q.local>
index | next in thread | previous in thread | raw e-mail
In message: <20070103205841.GB85200@roadrunner.q.local>
Ulrich Spoerlein <uspoerlein@gmail.com> writes:
: M. Warner Losh wrote:
: > I'd like to place the following in GENERIC. We're getting more and
: > more questions about these devices that we wouldn't be getting if we
: > had them compiled in by default. The really imporant ones are marked
: > with a '*' below
: >
: > device ucom # *
: > device umodem # *
: > device umct
: > device uark
: > device ubsa
: > device ubser
: > device uftdi # *
: > device uplcom # *
: > device uvisor
: > device uvscom
: >
: > the cost isn's so much, and we can filter them out from the
: > installation kernel if size is an issue.
: >
: > Comments?
:
: Hi Warner,
:
: why not do it the other way round? Keep them out of GENERIC, but have
: loader(8) load some of the most used modules (snd_driver!) per default.
:
: That way, people can easily disable these (without needing to
: recompile).
:
: I mean, what point is there in the whole KLD infrastructure, if we are
: going to add every device into GENERIC anyway?
Because the meta-data necessary to know which module to load doesn't
presently exist in a standardized enough form to make this a viable
option. Each driver does its own thing to match the cards, and
there's no easy way to know that any given usb device needs module
foo.
Warner
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070103.203403.63053841.imp>