[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200211142112.649d7237@endymion>
Date: Tue, 11 Feb 2020 14:21:12 +0100
From: Jean Delvare <jdelvare@...e.de>
To: Erwan Velu <erwanaliasr1@...il.com>
Cc: Erwan Velu <e.velu@...teo.com>,
Masahiro Yamada <masahiroy@...nel.org>,
Michal Marek <michal.lkml@...kovi.net>,
Mattias Jacobsson <2pi@....nu>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Andrew Lunn <andrew@...n.ch>,
"Darren Hart (VMware)" <dvhart@...radead.org>,
Changbin Du <changbin.du@...el.com>,
Russell King <rmk+kernel@...linux.org.uk>,
linux-kernel@...r.kernel.org, linux-kbuild@...r.kernel.org
Subject: Re: [PATCH] firmware/dmi: Report DMI Bios & EC firmware release
On Fri, 7 Feb 2020 09:35:47 +0100, Erwan Velu wrote:
> Some vendors like HPe or Dell, encode the release version of their BIOS
> in the "System BIOS {Major|Minor} Release" fields of Type 0.
>
> This information is used to know which bios release actually runs.
> It could be used for some quirks, debugging sessions or inventory tasks.
>
> A typical output for a Dell system running the 65.27 bios is :
> [root@...00 ~]# cat /sys/devices/virtual/dmi/id/bios_release
> 65.27
> [root@...00 ~]#
>
> Servers that have a BMC encode the release version of their firmware in the
> "Embedded Controller Firmware {Major|Minor} Release" fields of Type 0.
>
> This information is used to know which BMC release actually runs.
> It could be used for some quirks, debugging sessions or inventory tasks.
>
> A typical output for a Dell system running the 3.75 bmc release is :
> [root@...00 ~]# cat /sys/devices/virtual/dmi/id/ec_firmware_release
> 3.75
> [root@...00 ~]#
>
> Signed-off-by: Erwan Velu <e.velu@...teo.com>
> ---
> drivers/firmware/dmi-id.c | 6 ++++++
> drivers/firmware/dmi_scan.c | 30 ++++++++++++++++++++++++++++++
> include/linux/mod_devicetable.h | 2 ++
> scripts/mod/file2alias.c | 2 ++
> 4 files changed, 40 insertions(+)
> (...)
Applied, thanks. Note that I went for "efr" as the shortcut string for
DMI_EC_FIRMWARE_RELEASE, which was your first choice and has my
preference.
--
Jean Delvare
SUSE L3 Support
Powered by blists - more mailing lists