-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
/proc/cpuinfo on ARM processors includes Hardware field #881
Comments
That looks a great info to retrieve as in this case So we can't just blindly set At least we can safely set |
I only found one device with AmLogic Serial, and four others only say |
Here's another one:
So atleast two vendors are using this Hardware field. I think we should add support for it. |
I found more samples for you:
|
Thanks for these samples, could you please edit your message so it's easier to see where they begin/end? Was confused for a moment as I was seeing numerous Hardware fields for what I thought was the same file. From what I see, it confirms that setting the I won't be able to implement this soon as I will be on holidays for 7 days starting this Saturday. |
Hmm, each one is in a separate code block. I see white space between each block on the github website. Since you agree I can try to make a PR. |
Oops, it was my mobile client (Octodroid) that didn't visually separate the different sections. Thanks in advance if you submit a PR. |
From RPI4:
|
I worked on this issue in the following branch https://github.com/Lomanic/gopsutil/tree/issue881 (WIP, will have to rewrite history). If you check Because of this I was thinking about assigning |
On most ARM cpus, there is no Vendor or Family or Model fields in /proc/cpuinfo. The data gathered by gopsutil is very minimal:
However, there are some extra fields at the end of cpuinfo not currently parsed including
Hardware
:I would like to add support for this. Should I put the value of Hardware into one of the existing fields, or add a new field?
cc @Lomanic
The text was updated successfully, but these errors were encountered: