From: David Daney <ddaney@caviumnetworks.com>
To: Robert Millan <rmh@gnu.org>
Cc: Aurelien Jarno <aurelien@aurel32.net>,
Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org
Subject: Re: [PATCH] Enable AT_PLATFORM for Loongson 2F CPU
Date: Mon, 08 Nov 2010 11:13:46 -0800 [thread overview]
Message-ID: <4CD84BEA.6010607@caviumnetworks.com> (raw)
In-Reply-To: <1289133059.1547.0@thorin>
On 11/07/2010 04:30 AM, Robert Millan wrote:
> El 04/11/10 19:43:08, en/na Robert Millan va escriure:
>> David Daney a écrit :
>>> You are claiming that all loongson2 are loongson-2f. Is that
>>> really true? Or are there other types of loongson2 that are not
>>> loongson-2f?
>>
>> I'll figure out how to distinguish them and send a new patch.
>
> I looked at details about CPU identification, and this
> seems to be broken.
>
> See the the notes about PRId in pages 72 and 66, respectively:
> http://dev.lemote.com/files/resource/documents/Loongson/ls2f/Loongson2FUserGuide.pdf
>
> In both 2E and 2F, the implementation field is the same (0x63).
>
> Revision field is the same too, according to docs, and it can't
> be used anyway (no garantee of consistency).
I seems weird to me that you cannot get this information from the PRId
register. Perhaps the documentation is defective.
The Chinese version of the Loongson2E user guide seems to say something
about the two lower nibbles of the PRId, but being a non-chinese reader,
I have no idea if it would be relevant.
I would think that the low order bits of the register can reliably
differentiate these two parts.
David Daney
>
> I'm sending a new patch that uses machtype instead. Yes, I know
> it's a bit of a kludge, but it really seems to be the only way.
>
>> Well I appreciate consistency with GCC flag names,
>
> Actually, I missread GCC flag (it's dashless). I'm using
> "loongson2f" as David requested.
>
next prev parent reply other threads:[~2010-11-08 19:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 12:18 [PATCH] Enable AT_PLATFORM for Loongson 2F CPU Robert Millan
2010-11-04 16:44 ` David Daney
2010-11-04 17:33 ` Aurelien Jarno
2010-11-04 18:43 ` Robert Millan
2010-11-04 19:11 ` David Daney
2010-11-04 19:29 ` Ralf Baechle
2010-11-07 12:30 ` Robert Millan
2010-11-08 19:13 ` David Daney [this message]
2010-11-08 22:27 ` Robert Millan
2010-11-08 22:50 ` David Daney
2010-11-08 23:02 ` Robert Millan
2010-11-09 9:48 ` wu zhangjin
2010-11-09 12:24 ` Robert Millan
2010-11-09 15:40 ` Ralf Baechle
2010-11-11 14:47 ` Robert Millan
2010-11-15 23:50 ` Robert Millan
2010-11-15 23:59 ` David Daney
2010-11-22 12:44 ` Robert Millan
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=4CD84BEA.6010607@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=aurelien@aurel32.net \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=rmh@gnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.