From owner-freebsd-current@FreeBSD.ORG Sat Oct 18 08:28:31 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 911271065694; Sat, 18 Oct 2008 08:28:31 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe12.tele2.se [212.247.155.97]) by mx1.freebsd.org (Postfix) with ESMTP id 9AF908FC13; Sat, 18 Oct 2008 08:28:30 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=KbpOe3bC1BgA:10 a=E9KEX5fJTvYA:10 a=9EOqclcOrCvqfm+fhAoUTA==:17 a=ZsmV1RlNNToml8ng4DkA:9 a=m4tMTGDNSBEAQxbT_UVFoeLrUbsA:4 a=LY0hPdMaydYA:10 Received: from [130.79.3.186] (account mc467741@c2i.net [130.79.3.186] verified) by mailfe12.swip.net (CommuniGate Pro SMTP 5.2.6) with ESMTPA id 946314219; Sat, 18 Oct 2008 09:28:26 +0200 From: Hans Petter Selasky To: Brooks Davis Date: Sat, 18 Oct 2008 09:30:32 +0200 User-Agent: KMail/1.9.7 References: <20081015173319.GB46393@elvis.mu.org> <200810152124.12637.hselasky@c2i.net> <20081016092343.GB24852@lor.one-eyed-alien.net> In-Reply-To: <20081016092343.GB24852@lor.one-eyed-alien.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200810180930.33078.hselasky@c2i.net> Cc: "Sam Leffler \(FreeBSD Project\)" , Alfred Perlstein , current@freebsd.org Subject: Re: (forw) Re: USB4BSD - release candidate 2 - coming to FreeBSD this week. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Oct 2008 08:28:31 -0000 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? --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