On Wed, 2007-06-20 at 00:53 -0700, Edward Pilatowicz wrote: > but in your example below, are you delivering firmware in these > misc modules? or are these misc modules essentially modular > plugins for the scsi_vhci driver? (i thought they were the > latter.) > > this arc case was proposing that the promotion of ddi_modopen() > and friends was for the specific purpose of loading hardware > firmware modules, but there would be no reason that driver > writers wouldn't be able to use these interfaces for modularization > purposes as well, in which case it seems that the documentation > for these interfaces should provide some module naming advice > for both scenarios.
indeed. i'd be happer if these two aspects of the case were disentangled. ddi_modopen() has general utility broader than its use to get at firmware images encapsulated in a kernel module, and would promote its stability as-is.
