pytorch / pytorch/cpuinfo

soc name unknow for huawei mate40

Open
#191 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
C
Stars
1.2k
Forks
409
PR merge metrics
No merged PRs in 30d

Description

SoC name: Unknown
Microarchitectures:
        4x Cortex-A77
        4x Cortex-A55
Cores:
        0: 1 processor (0), ARM Cortex-A77
        1: 1 processor (1), ARM Cortex-A77
        2: 1 processor (2), ARM Cortex-A77
        3: 1 processor (3), ARM Cortex-A77
        4: 1 processor (4), ARM Cortex-A55
        5: 1 processor (5), ARM Cortex-A55
        6: 1 processor (6), ARM Cortex-A55
        7: 1 processor (7), ARM Cortex-A55
Logical processors (System ID):
        0 (7)
        1 (4)
        2 (5)
        3 (6)
        4 (0)
        5 (1)
        6 (2)
        7 (3)

which should be HiSilicon Kirin 9000E,

And, the SoC name is not correct for huawei mate40 pro 5G:

SoC name: HiSilicon Kirin 
Microarchitectures:
        4x Cortex-A77
        4x Cortex-A55
Cores:
        0: 1 processor (0), ARM Cortex-A77
        1: 1 processor (1), ARM Cortex-A77
        2: 1 processor (2), ARM Cortex-A77
        3: 1 processor (3), ARM Cortex-A77
        4: 1 processor (4), ARM Cortex-A55
        5: 1 processor (5), ARM Cortex-A55
        6: 1 processor (6), ARM Cortex-A55
        7: 1 processor (7), ARM Cortex-A55
Logical processors (System ID):
        0 (7)
        1 (4)
        2 (5)
        3 (6)
        4 (0)
        5 (1)
        6 (2)
        7 (3)

which should be HiSilicon Kirin 9000

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file or test is named in the report. Start by locating the SoC-name detection logic for Huawei Mate 40 devices, then reproduce the reported output and verify that both Kirin 9000E and Kirin 9000 are identified correctly.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
operating-systems
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.