From owner-svn-src-head@FreeBSD.ORG Wed Oct 14 15:00:45 2009 Return-Path: Delivered-To: svn-src-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7B1A4106566B; Wed, 14 Oct 2009 15:00:45 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 4B2358FC12; Wed, 14 Oct 2009 15:00:45 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id C5E1246B06; Wed, 14 Oct 2009 11:00:44 -0400 (EDT) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 1281B8A01B; Wed, 14 Oct 2009 11:00:44 -0400 (EDT) From: John Baldwin To: "M. Warner Losh" Date: Wed, 14 Oct 2009 07:53:56 -0400 User-Agent: KMail/1.9.7 References: <200910131904.n9DJ41QC013817@svn.freebsd.org> <200910131510.48144.jhb@freebsd.org> <20091013.200741.1973690373.imp@bsdimp.com> In-Reply-To: <20091013.200741.1973690373.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200910140753.57264.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Wed, 14 Oct 2009 11:00:44 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00, DATE_IN_PAST_03_06,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r198044 - head/sys/arm/conf X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Oct 2009 15:00:45 -0000 On Tuesday 13 October 2009 10:07:41 pm M. Warner Losh wrote: > In message: <200910131510.48144.jhb@freebsd.org> > John Baldwin writes: > : On Tuesday 13 October 2009 3:04:01 pm John Baldwin wrote: > : > Author: jhb > : > Date: Tue Oct 13 19:04:01 2009 > : > New Revision: 198044 > : > URL: http://svn.freebsd.org/changeset/base/198044 > : > > : > Log: > : > Sync with other GENERIC kernel configs: > : > - Move USB serial drivers earlier to match their placement in other kernel > : > configs. > : > - Add descriptions to various USB drivers. > : > - Move the USB wireless drivers into a new section. > : > - Add ulscom to the list of USB serial drivers. > : > : I do wonder if it is time to have some files like 'sys/conf/std.usb.serial' > : that list all the USB serial drivers so that we only have one list of instead > : of N to ease future maintenance. Similiar arguments could be made > : for 'std.usb.wireless' and 'std.usb.ethernet' perhaps. > > I've tried this in the past... Having multiple attributes in the > filename helps. but std.ethernet likely is a bad idea since that > means it needs to include usb.ethernet and you can't easily exclude > usb. USB seems to be a bus where if the bus works, then all the peripherals generally work unlike PCI where invidiual drivers need to handle DMA addresses properly, endian issues, etc. So, I'm only wondering out loud about the USB case for now since it seems more plausible than some other cases. What I would like to do is avoid having to touch N kernel configs each time a USB driver is added. > I've often thought that it would be cool to tag each device with one > or more attributes so we could easily include all devices with the > attribute, and also be able to report attribute based things... That sounds interesting. I think it means we need to move to more of a module-centric approach though where a module has a name, attributes, a list of files, etc. Possibly a list of variants as well (e.g. so drivers with multiple attachments can only include the attachments for the busses in the base kernel still when the driver is compiled into the kernel). -- John Baldwin