On Wed, 2007-08-22 at 11:39 -0700, Jerry Gilliam wrote:
>
> >
> >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.
I didn't know about ddi-vhci-class, but the ddi-forceattach is another
example of stuff that is going into driver.conf, that I'd rather have
more centrally managed.
>
>
> >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.
Ah, but this is less driver implementation and more *framework* related.
I mind less that drivers register a property in attach(), than that we
rely on the actual driver.conf to be read by the framework and used
before driver attach.
-- Garrett
>
>
> -jg
>
