Hi, On 5/7/07, James Carlson <[EMAIL PROTECTED]> wrote:
Thomas De Schampheleire writes: > > Right. So, you have your service method just touch the driver to have > > it loaded. > > > Does this mean that the _init functions *will* be called? Those are always called as the module is brought into memory. They're part of the kernel module-loading framework. See the modinstall() function. > You can set up a service that invokes the modload utility to force the > > module to load, but I think you're actually looking for the > > (undocumented) /platform/*/kernel/cpu/ directory. > > > Could you give some more information about what this directory is for and > how it could be of use to me? Not easily. :-/ But see cmi_load_module(), where we load up per-vendor CPU modules, and the existing files under /platform/i86pc/kernel/cpu/.
I should mention that I am using UltraSPARC, and there doesn't seem to be such cmi_* functions there. Are there other equivalents? The ones in x86 do seem interesting, but I wonder whether a CPU can have two cmi modules connected to it? I only want to implement its power management, not the rest of the handling. Thanks, thomas --
James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
_______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
