svn commit: r222980 - in head/sys: amd64/conf i386/conf

[Warner Losh]

On Jun 11, 2011, at 7:47 AM, Robert Watson wrote:

> 
> On Sat, 11 Jun 2011, Adrian Chadd wrote:
> 
>> btw, I just posted something similar to this on -arch.
> 
> FWIW, it doesn't have to be pretty, it really just has to work.  It would be nice if the same data could be used by both the boot loader and devd to load driver modules, and if the data were structured so that it could be easily extended.  I.e., /etc/driverdb with individual .xml or .whatever files, one per device driver, laying claim to things.  That way if there's going to be duking out for ownership of the device during early device, it's all worked out then.

Yea, that's not going to happen for 9.  Sorry.  I've been trying to get people interested in the problem of putting the device data in drivers in a standard for for years and there's been nobody that wants to do it.  Having /etc/driverdb is going to be obsolete very quickly and be a nightmare to maintain.

I think our best bet for 9 is to strip GENERIC to the bone and have a 'generic.conf' if you will that loads everything we compile in today.

For 10 we can move to having all the driver data exported in sections in the .ko files so that devd can load them.

We don't need to have them loaded by loader.conf.  All you need for that are the boot devices.  I've run my laptops for years like this.

Warner