-
Notifications
You must be signed in to change notification settings - Fork 6
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
standard processor-specific block structure does not match SMBIOS spec #9
Comments
Thanks for catching this, I will correct it in riscv-smbios spec. |
Ping @changab |
Wow, this ticket was opened in 2022 Jan. I am no longer working on RISC-V as I joined AMD. Could you please help to send the PR? |
There seemed to be a newer (and incompatible) definition at https://github.com/riscv-non-isa/riscv-brs/blob/main/smbios.adoc, which one should be used? |
Hi @jiegec, I am not quite clear. Which definition do you refer? Could you please point me to that definition? |
The SMBIOS Type 44 Processor-Specific Data definition seemed different. |
Are you saying the definition of SMBIOS type 44 is different than RISC-V SMBIOS Type44 processor-specific data? |
RISC-V Processor-specific Block Structure in this repo has revision v0.10, but in riscv-brs, the revision is v1.00. |
Ah I see. I think https://github.com/riscv-non-isa/riscv-brs/blob/main/smbios.adoc is newer. I think they created riscv-brs later. |
However, the SMBIOS spec still refers to this repo, which is the older one. |
What is the new URL to put in the SMBIOS spec? |
I think we can archive this repo and add links to the new specification. |
ok, I will send the ECR to SMBIOS WG to update this change. |
@kimonberlin, this is the one: https://github.com/riscv-non-isa/riscv-brs/blob/main/smbios.adoc. Thank you |
The "standard processor-specific block structure" described in section 2.2 does not match the "processor-specific block" defined in section 7.45.1 of SMBIOS 3.5.0.
The fields should be "block length", "processor type", and "processor-specific data".
The text was updated successfully, but these errors were encountered: