On Fri, Nov 12, 2004 at 12:14:18AM -0800, Matthew Dillon wrote:
> Another option which would work for post-boot KLD would be to have
> the module itself open the firmware file and read it in. DragonFly
> has convenient fp_*() functions to make this fairly trivial. Of
> course, this doesn't work if the module is built-in to the kernel
> compile but is that really a show stopper? I don't think it is.
I don't like the idea of drivers loading stuff from the file system
automatically. I've put an item for the generic firmware layer
on my TODO list, right after ALTQ and Citrus :)
Joerg