efi_loader: Expose SMBIOS table
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 7 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 7 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [U-Boot] [PATCH 0/7] efi_loader: Expose SMBIOS table
Quoted 17 lines · Simon Glass
Hi Alexander,
Quoted 14 lines · Alexander Graf
Quoted 14 lines
Am 08.08.2016 um 23:44 schrieb Simon Glass <[email protected]>:
Hi Alexander,
Quoted 9 lines · Alexander Graf
We generate a few tables on x86 today that really can be used on ARM just the same. One such example is the SMBIOS table, which people use with tools like "dmidecode" to identify which hardware they are running on.
We're slowly growing needs to collect serial numbers from various devices on ARM and SMBIOS seems the natural choice. So this patch set moves the current SMBIOS generation into generic code and adds serial number exposure to it.
Quoted 7 lines
Quoted 4 lines
Quoted 1 line
Shouldn't we use device tree? Why would an ARM device use SMBIOS?
Mostly because SBBR dictates it and every ARM server platform out there provides SMBIOS tables ;).
Also, both describe very different things. At least I have never seen things like "The chassy of this server has 2 power connectors and is blue" in device tree.
So there is no DT binding for this information? Does this mean that U-Boot on ARM needs to pass information through just 'sitting in RAM somewhere' like x86?
I don't think there's a non-EFI way on ARM to pass this through at all, correct. That's nothing new though - things like KASLR also depend on EFI.
Alex