Bug 219645 - Huawei Matebook E Go, whose codename is Gaokun
Summary: Huawei Matebook E Go, whose codename is Gaokun
Status: RESOLVED WILL_NOT_FIX
Alias: None
Product: Linux
Classification: Unclassified
Component: Kernel (show other bugs)
Hardware: ARM Linux
: P3 normal
Assignee: Virtual assignee for kernel bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-12-31 11:49 UTC by Pengyu Luo
Modified: 2025-01-02 12:06 UTC (History)
0 users

See Also:
Kernel Version:
Subsystem:
Regression: No
Bisected commit-id:


Attachments
GaoKun Gen3 motherboard photographed by Tianyu Gao <gty0622@gmail.com> (1.43 MB, image/jpeg)
2024-12-31 11:49 UTC, Pengyu Luo
Details
attachment-9231-0.html (1.83 KB, text/html)
2025-01-01 05:43 UTC, Pengyu Luo
Details
attachment-26585-0.html (3.53 KB, text/html)
2025-01-02 12:06 UTC, Pengyu Luo
Details

Description Pengyu Luo 2024-12-31 11:49:39 UTC
Created attachment 307428 [details]
GaoKun Gen3 motherboard photographed by Tianyu Gao <gty0622@gmail.com>

In this entry, we provide some evidence regarding why the codename of the Huawei Matebook E Go is Gaokun. Furthermore, the Qualcomm Snapdragon sc8280xp-based model is called GaoKun Gen3, or simply Gaokun3. We also speculate that the Qualcomm Snapdragon sc8180x-based model is called GaoKun Gen2, or just Gaokun2.

We can confirm that 'Gaokun' is the codename for the Huawei Matebook E Go, according to this link[1].

Based on the motherboard picture (see the attachment, credit to Tianyu Gao <gty0622@gmail.com>), we can infer that the Qualcomm Snapdragon sc8280xp-based model is called GaoKun Gen3."

In the Windows driver files (not attached for copyright reasons), we can find the strings 'GaoKunGen2' and 'GaoKunGen3'. Since they were released simultaneously, we speculate that the Qualcomm Snapdragon sc8180x-based model is called GaoKun Gen2.

[1] https://web.archive.org/web/20241231114747/https://consumer.huawei.com/en/support/content/en-us15945089/
Comment 1 Pengyu Luo 2025-01-01 05:43:06 UTC
Created attachment 307433 [details]
attachment-9231-0.html

On Tue, Dec 31, 2024 at 10:52 PM <bugzilla-daemon@kernel.org> wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=219645
>
> Artem S. Tashkinov (aros@gmx.com) changed:
>
> What    |Removed                     |Added
>
----------------------------------------------------------------------------
> Status|NEW                         |RESOLVED
> Group|                            |Junk
> Component|man-pages                   |Spam
> Version|unspecified                 |2.5
> Resolution|---                         |INVALID
> Assignee|documentation_man-pages@ker |other_spam@kernel-bugs.kern
> |nel-bugs.osdl.org           |el.org
> Product|Documentation               |Other
>
> --
> You may reply to this email to add a comment.
>
> You are receiving this mail because:
> You reported the bug.

Hi,

I am banned due to posting spam.I am not, I am the author of the series
(see[1])
I was suggested to document the internal name gaokun(see [2]).

[1]
https://lore.kernel.org/linux-arm-msm/20241227171353.404432-1-mitltlatltl@gmail.com
[2]
https://lore.kernel.org/linux-arm-msm/7fc6c727-d3c1-4c6d-a990-8caeb95c43c5@quicinc.com

Best regards,
Pengyu
Comment 2 Artem S. Tashkinov 2025-01-01 13:24:44 UTC
This a bug tracker.

I'm sorry that I closed it and marked it as spam but this bug report doesn't look and feel like a bug report. What's the point of it exactly?
Comment 3 Pengyu Luo 2025-01-02 12:06:24 UTC
Created attachment 307440 [details]
attachment-26585-0.html

Artem S. Tashkinov 2025-01-01 13:24:44 UTC
In this entry https://bugzilla.kernel.org/show_bug.cgi?id=219645
> This a bug tracker.
> I'm sorry that I closed it and marked it as spam but this bug report
doesn't look
> and feel like a bug report. What's the point of it exactly?

Because my account was blocked also, I just saw the entry, it is available
now.
When I tried to log in,

> Posting spam. If you believe your account should be restored, please send
email
> to helpdesk@kernel.org explaining why.

I had already send it.

About your question, code reviewer suggested me to document it on bugzilla.

> Here are some snippets for reference:
> "for 'volatile' documents, please create an entry in the kernel
> bugzilla https://bugzilla.kernel.org and attach a copy of these documents
> to the bugzilla entry. Finally, provide the URL of the bugzilla entry in
> the changelog."
>
>
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/maintainer-tip.rst
> [1]

I am not familiar with bugzilla, I focused on sending patches then I
created my
account after a glance on maintainer-tip, and added an entry in a hurry. I
am not
sure if my action is compliant, if not please tell me, thanks.

Best wishes,
Pengyu


On Tue, Dec 31, 2024 at 10:52 PM <bugzilla-daemon@kernel.org> wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=219645
>
> Artem S. Tashkinov (aros@gmx.com) changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>              Status|NEW                         |RESOLVED
>               Group|                            |Junk
>           Component|man-pages                   |Spam
>             Version|unspecified                 |2.5
>          Resolution|---                         |INVALID
>            Assignee|documentation_man-pages@ker
> |other_spam@kernel-bugs.kern
>                    |nel-bugs.osdl.org           |el.org
>             Product|Documentation               |Other
>
> --
> You may reply to this email to add a comment.
>
> You are receiving this mail because:
> You reported the bug.

Note You need to log in before you can comment on or make changes to this bug.