linux-kernel - [PATCH 0/4] dmi: Rework to get IPMI autoloading from DMI tables

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-id: <1454107394-8914-1-git-send-email-minyard@acm.org>
Date:	Fri, 29 Jan 2016 16:43:10 -0600
From:	minyard@....org
To:	openipmi-developer@...ts.sourceforge.net,
	linux-kernel@...r.kernel.org
Cc:	Jean Delvare <jdelvare@...e.de>, Andy Lutomirski <luto@...nel.org>
Subject: [PATCH 0/4] dmi: Rework to get IPMI autoloading from DMI tables

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