Date: Sat, 18 Oct 2008 08:51:29 -0500 From: Brooks Davis <brooks@freebsd.org> To: Hans Petter Selasky <hselasky@c2i.net> Cc: "Sam Leffler \(FreeBSD Project\)" <sam@freebsd.org>, Brooks Davis <brooks@freebsd.org>, current@freebsd.org, Alfred Perlstein <alfred@freebsd.org> Subject: Re: (forw) Re: USB4BSD - release candidate 2 - coming to FreeBSD this week. Message-ID: <20081018135128.GA44082@lor.one-eyed-alien.net> In-Reply-To: <200810180930.33078.hselasky@c2i.net> References: <20081015173319.GB46393@elvis.mu.org> <200810152124.12637.hselasky@c2i.net> <20081016092343.GB24852@lor.one-eyed-alien.net> <200810180930.33078.hselasky@c2i.net>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Sat, Oct 18, 2008 at 09:30:32AM +0200, Hans Petter Selasky wrote: > On Thursday 16 October 2008, Brooks Davis wrote: > > On Wed, Oct 15, 2008 at 09:24:11PM +0200, Hans Petter Selasky wrote: > > > > 4. I'm interested to understand why these container modules exist > > > > instead of individual drivers. > > > > > > They exist to make loading USB drivers easier. It is simpler to > > > load "usb2_serial" than to emperically search for a specific serial port > > > driver. In the future the "usb2_serial" module will load the correct > > > driver for you. > > > > If you want a stub usb2_serial module that loads all serial drivers, > > that migh be useful, but we do not have an (e.g.) if_ethernet module > > for a reason. The individual drivers MUST continue to exist and be > > independently configurable so embedded systems can choose what they > > need and exclude what they don't. > > > > -- Brooks > > Hi Brooks, > > That's no problem. Is the following list of module names acceptable? While I do kind of like them, I'd tend to lean toward not including the device classes in the names as that is a) tradtional and b) an easier transition for people with existing custom kernels. -- Brooks > --HPS @ eurobsdcon2008 > > usb2_bluetooth > usb2_bluetooth_fw > usb2_controller > usb2_controller_at91dci > usb2_controller_ehci > usb2_controller_musb > usb2_controller_ohci > usb2_controller_uhci > usb2_controller_uss820dci > usb2_core > usb2_ethernet > usb2_ethernet_aue > usb2_ethernet_axe > usb2_ethernet_cdce > usb2_ethernet_cue > usb2_ethernet_dav > usb2_ethernet_kue > usb2_ethernet_rue > usb2_image > usb2_image_scanner > usb2_input > usb2_input_hid > usb2_input_kbd > usb2_input_ms > usb2_misc > usb2_misc_dbp > usb2_misc_fm > usb2_ndis > usb2_quirk > usb2_serial > usb2_serial_ark > usb2_serial_bsa > usb2_serial_bser > usb2_serial_chcom > usb2_serial_cycom > usb2_serial_foma > usb2_serial_ftdi > usb2_serial_gensa > usb2_serial_ipaq > usb2_serial_lpt > usb2_serial_mct > usb2_serial_modem > usb2_serial_moscom > usb2_serial_plcom > usb2_serial_visor > usb2_serial_vscom > usb2_sound > usb2_storage > usb2_storage_ata > usb2_storage_fs > usb2_storage_mass > usb2_storage_rio > usb2_template > usb2_wlan > usb2_wlan_ral > usb2_wlan_rum > usb2_wlan_zyd [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iD8DBQFI+engXY6L6fI4GtQRAj4qAJ92X0rKor8nFlNWKDjlz9POSvPS0QCfRkEc dwMbLvUFylJlBdptROICXIA= =perf -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081018135128.GA44082>