Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Paul Boddie <paul@boddie.org.uk>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: "Maciej W. Rozycki" <macro@orcam.me.uk>,
	linux-mips@vger.kernel.org,
	Discussions about the Letux Kernel <letux-kernel@openphoenux.org>,
	Andreas Kemnade <akemnade@kernel.org>
Subject: Re: [PATCH] MIPS: cpu-probe: Recognise the XBurst core of the Ingenic X1600
Date: Sun, 25 Oct 2026 14:07:46 +0000	[thread overview]
Message-ID: <74546676961851519601e828c3cbbb30@boddie.org.uk> (raw)
In-Reply-To: <12ECACDC-2C60-4D0B-A124-D08380A2AA00@goldelico.com>

On 2026-10-25 12:14, H. Nikolaus Schaller wrote:
>> Am 25.10.2026 um 12:06 schrieb Paul Boddie <paul@boddie.org.uk>:
>> 
>> From the X1600 Programming Manual:
>> 
>> "2.2 PRID of X1600-CPU
>> Processor ID register (CP0 Register 15, select 0) in XBurst CPUs is a 
>> read-only register being
>> used to identify implementation detail of each SOC's CPU. Please refer 
>> to the programming
>> manual of XBurst CPU for detail of the register. For X1600, its value 
>> is 0x00D0000"
> 
> This seems to be a typo as it has only 7 digits. I have read from the 
> chip:
> 
> PRID table (as known from Programming Manuals)
> jz4780 0x3ee1024f (confirmed 0x3ee1024f on CI20 board)
> x1000 0x2ed1024f  (unconfimed)
> x1600 0x00d00000  (confirmed 0x00d00000 on LX16 board)
> X1830 0x00d00100  (unconfirmed)
> X2000 0x00132000  (read out from LX20 board)
> X2600 0x001320xx  (confirmed 0x00132000 on LX26 board)

Better references might be these:

XBurst®1 CPU Core Programming Manual
Section 2.3.1.8 Processor ID-PRId(CP0 Register 15, Select 0)

XBurst®2 CPU Core Programming Manual
Section 3.3.1.7 Processor ID-PRId(CP0 Register 15, Select 0)

However, they suggest a format which does not seem consistent with that 
used by the XBurst 1 chips.

Paul

  reply	other threads:[~2026-10-25 14:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-23 20:42 [PATCH] MIPS: cpu-probe: Recognise the XBurst core of the Ingenic X1600 Olivier Louvignes
2026-10-24 17:17 ` H. Nikolaus Schaller
2026-10-25  6:00   ` Maciej W. Rozycki
2026-10-25 11:06     ` Paul Boddie
2026-10-25 12:14       ` H. Nikolaus Schaller
2026-10-25 14:07         ` Paul Boddie [this message]
2026-10-28 12:52           ` Maciej W. Rozycki
2026-10-25 22:20     ` Paul Cercueil

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=74546676961851519601e828c3cbbb30@boddie.org.uk \
    --to=paul@boddie.org.uk \
    --cc=akemnade@kernel.org \
    --cc=hns@goldelico.com \
    --cc=letux-kernel@openphoenux.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=macro@orcam.me.uk \
    /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