2007/477: Drivers registering devids

[Jerry Gilliam]

>
>One concern I have in general, is relying on driver.conf values to
>perform this function.
>

driver.conf works for the proposed mechanism as early in boot
the system reads in all available conf files to discover properties
such as ddi-forceattach and ddi-vhci-class.


>driver.conf seems like a hack to expose things to the framework, whereas
>normal driver.conf would be for non-global tunables for the driver (e.g.
>per instance configurables, etc.)
>

driver.conf has always been a mixed bag:  part driver implementation
(as here);  global driver administration;  and per-instance
device administration.


-jg