[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150127113520.GG3320@codeblueprint.co.uk>
Date: Tue, 27 Jan 2015 11:35:20 +0000
From: Matt Fleming <matt@...eblueprint.co.uk>
To: Ivan Khoronzhuk <ivan.khoronzhuk@...aro.org>
Cc: linux-kernel@...r.kernel.org, ard.biesheuvel@...aro.org,
dmidecode-devel@...gnu.org, grant.likely@...aro.org,
leif.lindholm@...aro.org, matt.fleming@...el.com
Subject: Re: [Patch v2 0/2] firmware: dmi-sysfs: add SMBIOS entry point area
raw attribute
On Mon, 26 Jan, at 03:28:36PM, Ivan Khoronzhuk wrote:
> Some utils, like dmidecode and smbios, needs to access SMBIOS entry
> table area in order to get information like SMBIOS version, size, etc.
> Currently it's done via /dev/mem. But for situation when /dev/mem
> usage is disabled, the utils have to use dmi sysfs instead, which
> doesn't represent SMBIOS entry. So this patch series adds SMBIOS
> area to dmi sysfs in order to allow utils in question to work
> correctly with dmi sysfs.
>
> v1: https://lkml.org/lkml/2015/1/23/643
>
> v2..v1:
> firmware: dmi_scan: add symbol to get SMBIOS entry area
> - used additional static var to hold SMBIOS raw table size
> - changed format of get_smbios_entry_area symbol
> returned pointer on const smbios table
>
> firmware: dmi-sysfs: add SMBIOS entry point area attribute
> - adopted to updated get_smbios_entry_area symbol
> - removed redundant array to save smbios table
>
> Ivan Khoronzhuk (2):
> firmware: dmi_scan: add symbol to get SMBIOS entry area
> firmware: dmi-sysfs: add SMBIOS entry point area attribute
>
> drivers/firmware/dmi-sysfs.c | 42 ++++++++++++++++++++++++++++++++++++++++++
> drivers/firmware/dmi_scan.c | 26 ++++++++++++++++++++++++++
> include/linux/dmi.h | 3 +++
> 3 files changed, 71 insertions(+)
Unless anyone beats me to it, I'll pickup these two patches.
--
Matt Fleming, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists