You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Either in addition to or instead of. The specific id hex can let you determine more specifically which cpu
each dir table is for.
Or, barring that. Its my understanding that you're using the high bytes to determine generation, but we do know
many full IDs from the coreboot project, so something like Zen 3 (Cezanne) for the bytes 0xBC0C0140 could be useful.
Or perhaps both. 0xBC0C0140 Zen 3 (Cezanne) would be most informative.
The text was updated successfully, but these errors were encountered:
Hello,
which specific "Table" do you mean in this case?
I was thinking about implementing something like what you are requesting.
But sadly with my limited understanding, there seems to not be a "simple" single table telling us which CPUs the image supports.
Do you happen to have more knowledge, hints or ideas to help us out here?
Cheers
Either in addition to or instead of. The specific id hex can let you determine more specifically which cpu
each dir table is for.
Or, barring that. Its my understanding that you're using the high bytes to determine generation, but we do know
many full IDs from the coreboot project, so something like
Zen 3 (Cezanne)
for the bytes0xBC0C0140
could be useful.Or perhaps both.
0xBC0C0140 Zen 3 (Cezanne)
would be most informative.The text was updated successfully, but these errors were encountered: