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 . Changes from v1: * Split out the IPMI changes to their own patch. It compiles and works at each step, so no need to mix it up. Should be easier to review now. * Removed the dmi_zalloc() code, as the dmi_alloc already returns zeroed data. * Removed the dummy (no DMI) is_dmi_fwnode() and to_dmi_device() calls as they are only used under CONFIG_DMI. I'm still not sure about the device name and the driver_override setting. I'd prefer something different, but there's no easy way to provide device matching like ACPI and OF can. -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 [email protected] https://lists.sourceforge.net/lists/listinfo/openipmi-developer
