-
Notifications
You must be signed in to change notification settings - Fork 103
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
[ARM/RISC-V] Maybe check /sys/devices/soc0 #295
Comments
Well, on other devices |
Texas Instruments SoCs running with their BSP kernel also seem to expose SoC info via
|
As of this posting it looks like SoC and Technology are not being filled in. I've provided more info below to help get that info added. Let me know if you need me to run anything else.
This is from an Ampere Altra Q64-22
|
Another sbc-bench try to differentiate SoCs / SoC revisions is parsing /sys/devices/soc0. But if doing so checking for
/sys/devices/soc*
might be an even better idea.Most of the time this sysfs entry doesn't exist, sometimes it contains valuable hardware information, sometimes stuff we don't understand and sometimes rather confusing info (examples in this order):
Hmm... having checked sbc-bench's results collection right now with only SpacemiT K1/M1 providing relevant info via this sysfs node it's most probably not worth the efforts.
The text was updated successfully, but these errors were encountered: