From owner-freebsd-current@FreeBSD.ORG Wed Oct 15 19:22:10 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 3FFF61065690; Wed, 15 Oct 2008 19:22:10 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe03.swip.net [212.247.154.65]) by mx1.freebsd.org (Postfix) with ESMTP id 12DDC8FC12; Wed, 15 Oct 2008 19:22:08 +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=d6BVkb5LuPPVEe4iNQMLyA==:17 a=V-qcvZVEDlrtjqFKwZwA:9 a=vwRClDClVwqBylEuTxQA:7 a=RM3yhSDyi0Z5YCKWscdwokHqeGQA:4 a=50e4U0PicR4A:10 Received: from [62.113.135.6] (account mc467741@c2i.net [62.113.135.6] verified) by mailfe03.swip.net (CommuniGate Pro SMTP 5.2.6) with ESMTPA id 1120333081; Wed, 15 Oct 2008 21:22:07 +0200 From: Hans Petter Selasky To: Alfred Perlstein User-Agent: KMail/1.9.7 References: <20081015173319.GB46393@elvis.mu.org> In-Reply-To: <20081015173319.GB46393@elvis.mu.org> MIME-Version: 1.0 Content-Disposition: inline Date: Wed, 15 Oct 2008 21:24:11 +0200 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200810152124.12637.hselasky@c2i.net> Cc: "Sam Leffler \(FreeBSD Project\)" , 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: Wed, 15 Oct 2008 19:22:10 -0000 Hi, > > 1. libusb_20 appears to be undocumented (the manual page looks to be a > placeholder) and the only example of use (usbconfig) has zero comments. There is some work left to do there. Any help going through the USB library would be appreciated. > > 2. is there any way to list the set of quirks in the usb2_quirk module? > I don't think going back to the source is sufficient as you may only > have a binary to work with. Not at the moment, but I could possibly extend "usbconfig" to list available quirks. I've made a note for this. > > 3. similarly for the driver container modules can one see the set of > drivers bundled? No. You will have to inspect the module "DATA_SET()" information in the kld. > > 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. > I don't see anything in the manual pages > that references the drivers, can one still configure a kernel w/ only > the specific drivers present on a system? (e.g. for embedded use) If so > please fix the manual pages. Yes, of course you can still ungroup the driver modules into smaller parts, simply by moving the source files to another module, or removing the source files for the drivers you don't want. But there are no kernel options that will do that currently. You have to do it by hand until further. > > 5. The man page description of the usb2_template module is unclear to > me. I suspect an example would help. I have made a note for this. > > 6. Many files lack a copyright/license (e.g. modules/*). It is BSD licensed like the rest of the code. --HPS BTW: I will travel to EuroBSDcon2008 tomorrow and will probably not have access to e-mail all the time.