Skip to content
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

Handle RISC-V CPU Manufacturer and Brand using uarch in /proc/cpuinfo #904

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

RogerHardiman
Copy link

In the RISC-V world, CPUs are often designed by companies like SiFive, T-Head and Andes. Use the /proc/cpuinfo 'uarch' values to get the CPU designer and CPU model.

These designs are then licensed to SoC manufacturers who add I/O and GPU features. For example Allwinner (D1) and StarFive (JH7110), and Sophgo (SG2000)

Tested on my VisionFive2 2 RISC-V board

In the RISC-V world, CPUs are often designed by companies like SiFive, T-Head and Andes.
Use the /proc/cpuinfo 'uarch' values to get the CPU designer and CPU model.

These designs are then licensed to SoC manufacturers who add I/O and GPU features.
For example Allwinner (D1) and StarFive (JH7110), and Sophgo (SG2000)
@RogerHardiman
Copy link
Author

output of "npm test" on my StarFive VisionFive 2 SBC, which uses the JH7110 SOC which has the SiFive U74 processor inside.
So the result of CPU is a SiFive U74.
In a future commit I'd add the SOC (StarFive) and the SBC (StarFive Vision Five 2) to things like the Baseboard

┌────────────────────────────────────────────────┐
│ CPU v: 5.22.7 │
└────────────────────────────────────────────────┘
{
manufacturer: 'SiFive',
brand: 'u74-mc',
vendor: '',
family: '',
model: '',
stepping: '',
revision: '',
voltage: '',
speed: 1.5,
speedMin: null,
speedMax: null,
governor: 'ondemand',
cores: 4,
physicalCores: 4,
performanceCores: 4,
efficiencyCores: 0,
processors: 1,
socket: '',
flags: '',
virtualization: false,
cache: { l1d: '', l1i: '', l2: '', l3: '' }
}
Time to complete: 668.121ms

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant