[PATCH] DMI: Decode and save OEM String information

[Shem Multinymous]

This teachs dmi_decode() how to to save OEM Strings (type 11) information.
OEM Strings are  the only safe way to identify some hardware, e.g., the ThinkPad
embedded controller used by the soon-to-be-submitted tp_smapi driver.

Follows the "System Management BIOS (SMBIOS) Specification"
(http://www.dmtf.org/standards/smbios), and also the userspace
dmidecode.c code.

---
drivers/firmware/dmi_scan.c |   21 +++++++++++++++++++++
include/linux/dmi.h         |    3 ++-
2 files changed, 23 insertions(+), 1 deletions(-)

diff --git a/drivers/firmware/dmi_scan.c b/drivers/firmware/dmi_scan.c
index b9e3886..d1add3f 100644
--- a/drivers/firmware/dmi_scan.c
+++ b/drivers/firmware/dmi_scan.c
@@ -123,6 +123,24 @@ static void __init dmi_save_devices(stru
		dev->type = *d++ & 0x7f;
		dev->name = dmi_string(dm, *d);
		dev->device_data = NULL;
+		list_add(&dev->list, &dmi_devices);
+	}
+}
+
+static void __init dmi_save_oem_strings_devices(struct dmi_header *dm)
+{
+	int i, count = *(u8 *)(dm + 1);
+	struct dmi_device *dev;
+
+	for (i = 1; i <= count; i++) {
+		dev = dmi_alloc(sizeof(*dev));
+		if (!dev) {
+			break;
+		}
+
+		dev->type = DMI_DEV_TYPE_OEM_STRING;
+		dev->name = dmi_string(dm, i);
+		dev->device_data = NULL;

		list_add(&dev->list, &dmi_devices);
	}
@@ -181,6 +199,9 @@ static void __init dmi_decode(struct dmi
	case 10:	/* Onboard Devices Information */
		dmi_save_devices(dm);
		break;
+	case 11:	/* OEM Strings */
+		dmi_save_oem_strings_devices(dm);
+		break;
	case 38:	/* IPMI Device Information */
		dmi_save_ipmi_device(dm);
	}
diff --git a/include/linux/dmi.h b/include/linux/dmi.h
index b2cd207..38dc403 100644
--- a/include/linux/dmi.h
+++ b/include/linux/dmi.h
@@ -27,7 +27,8 @@ enum dmi_device_type {
	DMI_DEV_TYPE_ETHERNET,
	DMI_DEV_TYPE_TOKENRING,
	DMI_DEV_TYPE_SOUND,
-	DMI_DEV_TYPE_IPMI = -1
+	DMI_DEV_TYPE_IPMI = -1,
+	DMI_DEV_TYPE_OEM_STRING = -2
};

struct dmi_header {
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/