-
Notifications
You must be signed in to change notification settings - Fork 14
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
ProcessorFamily missing latest values #70
Comments
Hi @jrgerber , let me know if I can take this one. |
Hi @jrgerber , I was wondering about the hex values of the missing values. Seems like 3.4.0 spec has different values for some of the ones that are in this issue. Am I looking at the same table? (table 23) |
Yep, 7.5.2 Processor Information — Processor Family, Table 23. 100h-1FFh 256-511 These values are available for assignment, except for the following: I'm looking and see what you mean, this is confusing, it looks like more is wrong: 0xFE => ProcessorFamily::SeeProcessorFamily2, 0x100 => ProcessorFamily::ARMv7, 0x101 => ProcessorFamily::ARMv8, 0x102 => ProcessorFamily::SH3, 0x103 => ProcessorFamily::SH4, 0x104 => ProcessorFamily::ARM, 0x105 => ProcessorFamily::StrongARM, 0x106 => ProcessorFamily::Cyrix6x86, 0x107 => ProcessorFamily::MediaGX, 0x108 => ProcessorFamily::MII, 0x109 => ProcessorFamily::WinChip, 0x10A => ProcessorFamily::DSP, 0x10B => ProcessorFamily::VideoProcessor, 0x10C => ProcessorFamily::RISCVRV32, 0x10D => ProcessorFamily::RISCVRV64, 0x10E => ProcessorFamily::RISCVRV128,I think what went wrong is I didn't notice the non-contiguous numbering in this section and automatically numbered them starting at 0x100 contiguously. |
The following values are DMTF 3.4.0 values but are missing:
The text was updated successfully, but these errors were encountered: