In addition to statically compiling and having a user-client, would it be possible to use a second kernel module? Eg, we have the "real" device driver, and we have a module which consists of nothing but firmware arrays. When the device is probed, both modules are loaded (the driver moduke would "somehow" depend on the firmware module). The driver then figures out what device(s) is present, and copies the appropriate firmware array to malloced memory in the driver. It then "somehow" releases the firmware module, and that module is unloaded, saving memory. If a similar device was added to the system, the firmware module would "somehow" get re-loaded, and the new instance of the device would copy the firmware, as above.. As you can see by the "somehows", I'm a little fuzzy on the details. Is a scheme like this possible in Darwin? Drew _______________________________________________ darwin-kernel mailing list | darwin-kernel@lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-kernel Do not post admin requests to the list. They will be ignored.