All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: Paul Cercueil <paul@crapouillou.net>,
	"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
	linux-kernel@vger.kernel.org,
	Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Subject: Re: [PATCH 1/2] MIPS: Allow MIPS32R2 kernel to run on P5600 and M5150
Date: Tue, 30 May 2023 12:07:26 +0100 (BST)	[thread overview]
Message-ID: <alpine.DEB.2.21.2305301152080.42601@angie.orcam.me.uk> (raw)
In-Reply-To: <684C1A48-C743-4045-AF12-B0846FCE8EBE@flygoat.com>

On Tue, 30 May 2023, Jiaxun Yang wrote:

> >> M5150 and P5600 are two MIPS32R5 kernels, however as MIPS32R5 is
> >> backward compatible with MIPS32R2 there is no reason to forbid
> >> M5150 and P5600 on MIPS32R2 kernel.
> > 
> > What problem are you trying to solve?  The CONFIG_SYS_HAS_CPU_* settings 
> > denote overall platform's support for the given CPU and have nothing to do 
> > with what architecture level a given kernel has been configured for.  You 
> > do need to get the settings right for your platform, just as you do in 
> > 2/2, but this 1/2 part looks wrong to me.
> 
> Well the universal target is to allow R2 generic kernel to run on R5 CPUs.
> As R5 is backward compatible we can just have one universal kernel binary.

 Sure, but this change is not needed for it.  You just need to declare 
which ISA revisions your platform supports and leave `__get_cpu_type' 
alone.  It has worked like that for a decade now.

 Back in the day I used to run R1 kernels on R2 hardware myself.  And 
maybe MIPS IV on R1 even, as we had MIPS Malta CPU modules with both MIPS 
IV devices (QED RM5261/RM7061) and MIPS64r1 devices (MIPS 5Kc/20Kc/25Kf) 
and switching the kernel when swapping modules was a nuisance.  The Malta 
config still supports these devices although some may not exist anymore.

  Maciej

  reply	other threads:[~2023-05-30 11:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-29 13:52 [PATCH 1/2] MIPS: Allow MIPS32R2 kernel to run on P5600 and M5150 Jiaxun Yang
2023-05-29 13:52 ` [PATCH 2/2] MIPS: generic: Allow R5 CPUs to be selected Jiaxun Yang
2023-05-30 13:37   ` Serge Semin
2023-06-09  8:21   ` Thomas Bogendoerfer
2023-05-30  8:03 ` [PATCH 1/2] MIPS: Allow MIPS32R2 kernel to run on P5600 and M5150 Maciej W. Rozycki
2023-05-30  8:18   ` Paul Cercueil
2023-05-30  9:13     ` Maciej W. Rozycki
2023-05-30 10:11   ` Jiaxun Yang
2023-05-30 11:07     ` Maciej W. Rozycki [this message]
2023-05-30 11:54       ` Jiaxun Yang
2023-05-30 12:16         ` Maciej W. Rozycki
2023-05-30 12:41           ` Serge Semin
2023-05-30 12:51             ` Serge Semin
2023-05-30 12:57               ` Jiaxun Yang
2023-05-30 13:10           ` Jiaxun Yang
2023-05-30 13:14             ` Maciej W. Rozycki
2023-05-30 13:33             ` Serge Semin

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=alpine.DEB.2.21.2305301152080.42601@angie.orcam.me.uk \
    --to=macro@orcam.me.uk \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=paul@crapouillou.net \
    --cc=tsbogend@alpha.franken.de \
    /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.