-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Filled SMBIOS part in DTB file #423
Comments
Sorry for the delay for this "simple" thing, we are on it. A first upstream-aiming patch set can be found at https://github.com/siemens/u-boot/commits/jan/iot2050. An open question is which fields we must have in addition to this:
|
@jan-kiszka For the fields, I think we have to refer to the standard x86 IPCs and try to use the same field when possible. And most fields are sourcing from the scratchpad iot2050-info, so I am working a sysinfo driver for iot2050 so that the required data could be easily passed into the dmitable. Will send out the patch for reviewing and upstreaming once done, (now blocked by a sync data abort exception issue ...) |
Will that driver cover static elements from a DT input like above as well? In any case, the driver alone does not answer what we fill on, only how. |
It will, the sysinfo uclass in u-boot allows you to add the static elements in the DT, together with the dynamic elements from somewhere such as the eeprom to feed to the dmitable. I've tried that in my dirty branch, it worked. see smbios.txt, esp. the example. |
FWIW, we finally have some driver and integration that should address this, see https://github.com/siemens/u-boot/commits/jan/iot2050. It's a preview and also still needs to be run via upstream, but feedback on the chosen (or missing) fields is welcome. Here some example:
|
As UEFI for arm64 is available by u-boot, for the purpose of unified platform retrieval for different architectures, DMI tables should be available for IOT2050/ARM64 device as in the x86_64 devices.
If it is possible, please add as many as of them.
Thanks in advance.
The text was updated successfully, but these errors were encountered: