linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiaxun Yang <jiaxun.yang@flygoat.com>
To: Manuel Lauss <manuel.lauss@gmail.com>,
	Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	Huacai Chen <chenhc@lemote.com>,
	Linux-MIPS <linux-mips@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Xuefeng Li <lixuefeng@loongson.cn>
Subject: Re: [PATCH] MIPS: Loongson: Add model name to /proc/cpuinfo
Date: Wed, 11 Mar 2020 18:27:48 +0800	[thread overview]
Message-ID: <788597FA-6AD6-4218-886F-35C0916EA3F2@flygoat.com> (raw)
In-Reply-To: <CAOLZvyHEnnpWWhEAWx9RZASVjjQ=6HTREqwY+LK0hm=J4Wd8Xg@mail.gmail.com>



于 2020年3月11日 GMT+08:00 下午5:58:48, Manuel Lauss <manuel.lauss@gmail.com> 写到:
>Hello,
>
>> Model name:            Loongson-3A R3 (Loongson-3A3000) @ 1449MHz
>
>How is this different from the __cpu_name[] array?  Doesn't it serve
>the same purpose?
>E.g. on Alchemy, it lists the correct Model name. (I.e. "Au1000",
>"Au1250", ...)

Hi,

__cpu_name[] will be displayed as "cpu model" in cpuinfo, however
in x86 world, the name line is started with "model name".
Most user applications like lscpu, hwinfo is following x86's rule, we don't have superpower to move all of them.

Also rename "cpu model" will break current ABI, so just create a new array
for it would be a better option.

For why Loongson is doing this, I guess they need a chance to show
their business processor name instead of revision.

Thanks

>
>Manuel

-- 
Jiaxun Yang

  reply	other threads:[~2020-03-11 10:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-11  6:33 [PATCH] MIPS: Loongson: Add model name to /proc/cpuinfo Tiezhu Yang
2020-03-11  6:53 ` 回复:[PATCH] " Jiaxun Yang
2020-03-11  9:28   ` Tiezhu Yang
2020-03-11  7:18 ` [PATCH] " YunQiang Su
2020-03-11  7:41   ` Jiaxun Yang
2020-03-11  9:40   ` Tiezhu Yang
2020-03-12  7:25     ` Tiezhu Yang
2020-03-11  9:58 ` Manuel Lauss
2020-03-11 10:27   ` Jiaxun Yang [this message]
2020-03-20 21:24     ` Maciej W. Rozycki
2020-03-21  1:20       ` YunQiang Su

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=788597FA-6AD6-4218-886F-35C0916EA3F2@flygoat.com \
    --to=jiaxun.yang@flygoat.com \
    --cc=chenhc@lemote.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=lixuefeng@loongson.cn \
    --cc=manuel.lauss@gmail.com \
    --cc=tsbogend@alpha.franken.de \
    --cc=yangtiezhu@loongson.cn \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).