All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Hellstrom <daniel@gaisler.com>
To: sparclinux@vger.kernel.org
Subject: Re: How to recognize a LEON CPU?
Date: Tue, 22 May 2012 06:40:19 +0000	[thread overview]
Message-ID: <4FBB34D3.8030403@gaisler.com> (raw)
In-Reply-To: <20120521162253.GB5733@merkur.ravnborg.org>

On 05/21/2012 06:22 PM, Sam Ravnborg wrote:
> Who is the relevant Gaisler contact person these days for Linux stuff?
> I sometimes uses Daniel, sometimes Konrad.
Please CC both of us. Kristoffer Glembo is no longer active though.

> I can just add both of you - this is no problem.
> As I plan to update the LEON integration it would be good
> to have in place.
>
> Anyway - the real question..
>
> In head_32.S I need very early on to determine the CPU type,
> so I can distingush between LEON and SUN.
> This is due to LEON using a different ASI for mmuregs
> as discussed in another mail.
>
> I assume this can be determinded from PSR.
> If this is correct - then what values shall I use
> to determine if the relevant cpu is LEON or SUN?
The LEON is SPARC compliant and has a registered number, from the manual (http://gaisler.com/products/grlib/grip.pdf section LEON3 and LEON4):

65.2.3 SPARC Implementor's ID
Gaisler Research is assigned number 15 (0xF) as SPARC implementor's identification. This value is
hard-coded into bits 31:28 in the %psr register. The version number for LEON3 is 3, which is hard-
coded in to bits 27:24 of the %psr.


Note that LEON3 and LEON4 have the same version number, they are software compatible.

Daniel

  parent reply	other threads:[~2012-05-22  6:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-21 16:22 How to recognize a LEON CPU? Sam Ravnborg
2012-05-21 21:12 ` David Miller
2012-05-22  6:28 ` Konrad Eisele
2012-05-22  6:40 ` Daniel Hellstrom [this message]
2012-05-22  6:41 ` Daniel Hellstrom

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=4FBB34D3.8030403@gaisler.com \
    --to=daniel@gaisler.com \
    --cc=sparclinux@vger.kernel.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.