From owner-freebsd-current@FreeBSD.ORG Sat Oct 18 14:05:01 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 109191065698; Sat, 18 Oct 2008 14:05:01 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.9.129]) by mx1.freebsd.org (Postfix) with ESMTP id 88B0E8FC1A; Sat, 18 Oct 2008 14:05:00 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 713BA730A8; Sat, 18 Oct 2008 16:09:04 +0200 (CEST) Date: Sat, 18 Oct 2008 16:09:04 +0200 From: Luigi Rizzo To: Brooks Davis Message-ID: <20081018140904.GA50010@onelab2.iet.unipi.it> References: <20081015173319.GB46393@elvis.mu.org> <200810152124.12637.hselasky@c2i.net> <20081016092343.GB24852@lor.one-eyed-alien.net> <200810180930.33078.hselasky@c2i.net> <20081018135128.GA44082@lor.one-eyed-alien.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081018135128.GA44082@lor.one-eyed-alien.net> User-Agent: Mutt/1.4.2.3i Cc: "Sam Leffler \(FreeBSD Project\)" , current@freebsd.org, Alfred Perlstein , Hans Petter Selasky 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 14:05:01 -0000 On Sat, Oct 18, 2008 at 08:51:29AM -0500, Brooks Davis wrote: > On Sat, Oct 18, 2008 at 09:30:32AM +0200, Hans Petter Selasky wrote: > > On Thursday 16 October 2008, Brooks Davis wrote: ... > > > 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. actually there is already a precedent -- snd_* have a deviceclass prefix, and the prefix is certainly a step forward in making the config files more readable (especially with the cryptic 2/3 letter driver names that we use. With the change to usb2 people will have to add a prefix anyways, so this seems a good chance to start using the deviceclass prefix as well. cheers luigi