The IPMI driver would not auto-load from DMI tables. So these patches creates a platform device from an IPMI DMI table entry, and then modify the IPMI driver to handle all this.
I followed how ACPI works mostly, with a fwnode and such. But greatly simplified, of course :). I'm no sure if patch 4 is done in the right place. Maybe it would be better in the IPMI driver directory? But it's pretty clean where it is. Also, I wasn't quite sure about the name of the device. If the device was named ipmi_si or ipmi_ssif, the driver override would not be required, but then you really couldn't tell it came from DMI. You could also create a firmware_node like ACPI does, but that might be overkill. -corey ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 _______________________________________________ Openipmi-developer mailing list Openipmi-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openipmi-developer
