linux-kernel - Re: [PATCH v2 0/2] DMI: Scan for DMI table from DTS info

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20251022201953.GA206947-robh@kernel.org>
Date: Wed, 22 Oct 2025 15:19:53 -0500
From: Rob Herring <robh@...nel.org>
To: adriana <adriana@...sta.com>
Cc: krzk@...nel.org, jdelvare@...e.com, frowand.list@...il.com,
	linux-arm-kernel@...ts.infradread.org, linux-kernel@...r.kernel.org,
	devicetree@...r.kernel.org, vasilykh@...sta.com
Subject: Re: [PATCH v2 0/2] DMI: Scan for DMI table from DTS info

On Wed, Oct 22, 2025 at 04:45:25AM -0700, adriana wrote:
> Some bootloaders like U-boot, particularly for the ARM architecture,
> provide SMBIOS/DMI tables at a specific memory address. However, these
> systems often do not boot using a full UEFI environment, which means the
> kernel's standard EFI DMI scanner cannot find these tables.

I thought u-boot is a pretty complete UEFI implementation now. If 
there's standard way for UEFI to provide this, then that's what we 
should be using. I know supporting this has been discussed in context of 
EBBR spec, but no one involved in that has been CC'ed here.
 
> This series adds support for the kernel to find these tables by
> reading properties from the Device Tree /chosen node. The bootloader
> can specify the physical addresses using "linux,smbios-table" and
> "linux,smbios3-table".

/chosen node entries go in chosen.yaml schema in dtschema repository. 
But first, I need to see some agreement this is how we want to support 
this.

Rob