From: Raymond Mao <raymondmaoca@gmail.com>
To: u-boot@lists.denx.de
Cc: Raymond Mao <raymond.mao@riscstar.com>,
Raymond Mao <raymondmaoca@gmail.com>,
Tom Rini <trini@konsulko.com>,
Mark Kettenis <kettenis@openbsd.org>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Baocheng Su <baocheng.su@siemens.com>,
Li Hua Qian <huaqian.li@siemens.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
Samuel Holland <samuel.holland@sifive.com>
Subject: [PATCH v6 0/6] Implement all missing SMBIOS types required by distro tooling
Date: Fri, 13 Feb 2026 17:52:45 -0500 [thread overview]
Message-ID: <20260213225254.2544596-1-raymondmaoca@gmail.com> (raw)
From: Raymond Mao <raymond.mao@riscstar.com>
This series finish the last missing puzzle of required SMBIOS types by:
1) Fixing duplicated handles when multiple instances exist in one type;
2) Implementing the rest of required types 9/16/17/19;
3) Adding version control when printing properties for all types.
Type 9/16/17/19 are generally DT-based, the idea is to write these tables
using a hybrid approach:
Explicit DT definitions under existing '/smbios/smbios' take precedence,
with fallback to scan and interpret values from the entire DT.
Moreover, all below APIs:
smbios_get_val_si()
smbios_get_u64_si()
smbios_add_prop_si()
are on top of sysinfo, thus allow vendors to get values from other
subsystems by implementing their own sysinfo driver if needed.
Raymond Mao (6):
smbios: Fix duplicated smbios handles
smbios: add support for dynamic generation of Type 9 system slot
tables
smbios: add support for dynamic generation of Type 16 table
smbios: add support for dynamic generation of Type 17 table
smbios: add support for dynamic generation of Type 19 table
smbios: print the properties only when they exist in a specified
version of spec
arch/arm/dts/smbios_generic.dtsi | 12 +
cmd/smbios.c | 365 +++++++++-
drivers/sysinfo/smbios.c | 5 +
include/smbios.h | 151 ++++
include/smbios_def.h | 250 +++++++
include/sysinfo.h | 4 +
lib/smbios.c | 1151 +++++++++++++++++++++++++++++-
7 files changed, 1905 insertions(+), 33 deletions(-)
--
2.25.1
next reply other threads:[~2026-02-13 22:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 22:52 Raymond Mao [this message]
2026-02-13 22:52 ` [PATCH v6 1/6] smbios: Fix duplicated smbios handles Raymond Mao
2026-02-13 22:52 ` [PATCH v6 2/6] smbios: add support for dynamic generation of Type 9 system slot tables Raymond Mao
2026-02-13 22:52 ` [PATCH v6 3/6] smbios: add support for dynamic generation of Type 16 table Raymond Mao
2026-02-13 22:52 ` [PATCH v6 4/6] smbios: add support for dynamic generation of Type 17 table Raymond Mao
2026-02-13 22:52 ` [PATCH v6 5/6] smbios: add support for dynamic generation of Type 19 table Raymond Mao
2026-02-13 22:52 ` [PATCH v6 6/6] smbios: print the properties only when they exist in a specified version of spec Raymond Mao
2026-02-17 7:14 ` [PATCH v6 0/6] Implement all missing SMBIOS types required by distro tooling Ilias Apalodimas
2026-02-17 14:01 ` Raymond Mao
2026-02-18 16:00 ` Tom Rini
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=20260213225254.2544596-1-raymondmaoca@gmail.com \
--to=raymondmaoca@gmail.com \
--cc=baocheng.su@siemens.com \
--cc=huaqian.li@siemens.com \
--cc=ilias.apalodimas@linaro.org \
--cc=jan.kiszka@siemens.com \
--cc=kettenis@openbsd.org \
--cc=raymond.mao@riscstar.com \
--cc=samuel.holland@sifive.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
/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