From: Jean Delvare <jdelvare@suse.de>
To: Erwan Velu <erwanaliasr1@gmail.com>
Cc: Erwan Velu <e.velu@criteo.com>,
Masahiro Yamada <masahiroy@kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
Mattias Jacobsson <2pi@mok.nu>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Andrew Lunn <andrew@lunn.ch>,
"Darren Hart (VMware)" <dvhart@infradead.org>,
Changbin Du <changbin.du@intel.com>,
Russell King <rmk+kernel@armlinux.org.uk>,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] firmware/dmi: Report DMI Bios & EC firmware release
Date: Tue, 11 Feb 2020 14:21:12 +0100 [thread overview]
Message-ID: <20200211142112.649d7237@endymion> (raw)
In-Reply-To: <20200207083550.360461-1-e.velu@criteo.com>
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@t1700 ~]# cat /sys/devices/virtual/dmi/id/bios_release
> 65.27
> [root@t1700 ~]#
>
> 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@t1700 ~]# cat /sys/devices/virtual/dmi/id/ec_firmware_release
> 3.75
> [root@t1700 ~]#
>
> Signed-off-by: Erwan Velu <e.velu@criteo.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
next prev parent reply other threads:[~2020-02-11 13:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 8:35 [PATCH] firmware/dmi: Report DMI Bios & EC firmware release Erwan Velu
2020-02-11 13:21 ` Jean Delvare [this message]
2020-02-11 13:31 ` Erwan Velu
2020-05-11 17:10 ` Erwan Velu
2020-05-12 7:37 ` Jean Delvare
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=20200211142112.649d7237@endymion \
--to=jdelvare@suse.de \
--cc=2pi@mok.nu \
--cc=andrew@lunn.ch \
--cc=andriy.shevchenko@linux.intel.com \
--cc=changbin.du@intel.com \
--cc=dvhart@infradead.org \
--cc=e.velu@criteo.com \
--cc=erwanaliasr1@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=rmk+kernel@armlinux.org.uk \
/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