Date: Wed, 14 Oct 2009 07:53:56 -0400 From: John Baldwin <jhb@freebsd.org> To: "M. Warner Losh" <imp@bsdimp.com> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r198044 - head/sys/arm/conf Message-ID: <200910140753.57264.jhb@freebsd.org> In-Reply-To: <20091013.200741.1973690373.imp@bsdimp.com> References: <200910131904.n9DJ41QC013817@svn.freebsd.org> <200910131510.48144.jhb@freebsd.org> <20091013.200741.1973690373.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 13 October 2009 10:07:41 pm M. Warner Losh wrote: > In message: <200910131510.48144.jhb@freebsd.org> > John Baldwin <jhb@FreeBSD.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200910140753.57264.jhb>