module load order causing failure
by jsb1 from LinuxQuestions.org on (#5QVQ3)
I have an issue, where a kernel driver module I'm working on is calling an ACPI method. This method is accessing IPMI operation region, which will fail if the driver for the IPMI controller isn't loaded yet... so, during boot, my module gets loaded, and it fails, and almost immediately afterward the IPMI driver is loaded. If I then unload and reload my driver, it will work.
But my driver does not DEPEND on IPMI... it just happens to depend on it in this system, because the ACPI method I'm running uses an IPMI Op Region (though it likely does not do so on some systems). So my driver could work just fine on other systems that don't even have IPMI. The ACPI method I'm running is a _DSM that's under a PCI device in an ?SDT ACPI table, FWIW.
Is there any way to make this just work right, without having to add special udev rules or scripts just for this system? I'm not sure what the right solution would be.
But my driver does not DEPEND on IPMI... it just happens to depend on it in this system, because the ACPI method I'm running uses an IPMI Op Region (though it likely does not do so on some systems). So my driver could work just fine on other systems that don't even have IPMI. The ACPI method I'm running is a _DSM that's under a PCI device in an ?SDT ACPI table, FWIW.
Is there any way to make this just work right, without having to add special udev rules or scripts just for this system? I'm not sure what the right solution would be.