How does hardinfo get the name of the cpu?

[ggonek1m]

After I run hardinfo, the Processor displays Uknown

[lpereira]

That's weird! HardInfo reads from /proc/cpuinfo, which is populated by Linux. If you could attach the contents of /proc/cpuinfo here, it would be helpful to address this issue

…

On Mon, Nov 7, 2022, at 10:17 PM, ggonek1m wrote: After I run hardinfo, the Processor displays Uknown — Reply to this email directly, view it on GitHub <#679>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAADVGO27S3VOHUX53KJE53WHHWBFANCNFSM6AAAAAARZ6GZ2Y>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[ggonek1m]

cat /proc/cpuinfo
processor : 0
BogoMIPS : 100.00
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid
CPU implementer : 0x70
CPU architecture: 8
CPU variant : 0x1
CPU part : 0x663
CPU revision : 3

processor : 1
BogoMIPS : 100.00
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid
CPU implementer : 0x70
CPU architecture: 8
CPU variant : 0x1
CPU part : 0x663
CPU revision : 3

processor : 2
BogoMIPS : 100.00
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid
CPU implementer : 0x70
CPU architecture: 8
CPU variant : 0x1
CPU part : 0x663
CPU revision : 3

[ggonek1m]

lscpu
Architecture: aarch64
CPU op-mode(s): 64-bit
Byte Order: Little Endian
CPU(s): 128
On-line CPU(s) list: 0-127
Vendor ID: Phytium
BIOS Vendor ID: PHYTIUM
Model name: FTC663
BIOS Model name: S2500 NULL CPU @ 2.1GHz
BIOS CPU family: 257
Model: 3
Thread(s) per core: 1
Core(s) per socket: 64
Socket(s): 2
Stepping: 0x1
BogoMIPS: 100.00
Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid
Caches (sum of all):
L1d: 4 MiB (128 instances)
L1i: 4 MiB (128 instances)
L2: 64 MiB (32 instances)
L3: 128 MiB (2 instances)
NUMA:
NUMA node(s): 16
NUMA node0 CPU(s): 0-7
NUMA node1 CPU(s): 8-15
NUMA node2 CPU(s): 16-23
NUMA node3 CPU(s): 24-31
NUMA node4 CPU(s): 32-39
NUMA node5 CPU(s): 40-47
NUMA node6 CPU(s): 48-55
NUMA node7 CPU(s): 56-63
NUMA node8 CPU(s): 64-71
NUMA node9 CPU(s): 72-79
NUMA node10 CPU(s): 80-87
NUMA node11 CPU(s): 88-95
NUMA node12 CPU(s): 96-103
NUMA node13 CPU(s): 104-111
NUMA node14 CPU(s): 112-119
NUMA node15 CPU(s): 120-127
Vulnerabilities:
Itlb multihit: Not affected
L1tf: Not affected
Mds: Not affected
Meltdown: Mitigation; PTI
Spec store bypass: Vulnerable
Spectre v1: Mitigation; __user pointer sanitization
Spectre v2: Vulnerable
Srbds: Not affected
Tsx async abort: Not affected

[ggonek1m]

If I want to use other methods to obtain the CPU information, such as dmicode or lscpu, do I modify it in computer. c

[lpereira]

Modify things in modules/devices/arm/processor.c. There might be tables embedded in this file that help figure out the processor name. A good thing to do is make it read from a JSON file in ~/.config/hardinfo, and then make it updatable from the updater (for instance, see how cpu_flags.json is handled in the x86 version at modules/devices/x86/x86_data.c and how it's declared in modules/devices.c so it can be updated). If you put the table in data/cpuflags.json, the updater will pick it up automatically once I set it up.

…

On Wed, Nov 9, 2022, at 2:23 AM, ggonek1m wrote: If I want to use other methods to obtain the CPU information, such as dmicode or lscpu, do I modify it in computer. c — Reply to this email directly, view it on GitHub <#679 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAADVGJ2FZKJEKS345HKKJ3WHMDJXANCNFSM6AAAAAARZ6GZ2Y>. You are receiving this because you commented.Message ID: ***@***.***>