mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Shem Multinymous" <multinymous@gmail.com>
To: "linux kernel mailing list" <linux-kernel@vger.kernel.org>
Cc: "Bjorn Helgaas" <bjorn.helgaas@hp.com>,
	"Matt Domsch" <Matt_Domsch@dell.com>,
	"Brown, Len" <len.brown@intel.com>,
	"Henrique de Moraes Holschuh" <hmh@debian.org>
Subject: [PATCH] DMI: Decode and save OEM String information
Date: Thu, 27 Jul 2006 16:47:00 +0300	[thread overview]
Message-ID: <41840b750607270647w5a05ad00r613dbaf42bf04771@mail.gmail.com> (raw)

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 {

             reply	other threads:[~2006-07-27 13:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-27 13:47 Shem Multinymous [this message]
2006-07-27 16:10 ` Bjorn Helgaas
2006-07-27 16:42   ` Shem Multinymous
2006-07-28  3:27     ` Bjorn Helgaas
2006-07-28 12:49       ` Henrique de Moraes Holschuh
2006-07-28 18:37         ` Bjorn Helgaas
2006-07-28 20:52           ` Shem Multinymous
2006-07-28 21:08             ` Bjorn Helgaas
2006-07-28 22:07               ` Shem Multinymous
2006-07-29 12:55 ` Shem Multinymous
2006-07-29 16:29   ` Carl-Daniel U. Hailfinger
2006-07-29 17:09     ` Shem Multinymous
2006-08-02 12:19     ` Pavel Machek
2006-08-02 10:39 ` Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=41840b750607270647w5a05ad00r613dbaf42bf04771@mail.gmail.com \
    --to=multinymous@gmail.com \
    --cc=Matt_Domsch@dell.com \
    --cc=bjorn.helgaas@hp.com \
    --cc=hmh@debian.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®