All of lore.kernel.org
 help / color / mirror / Atom feed
From: Serge Semin <fancer.lancer@gmail.com>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
	tsbogend@alpha.franken.de
Subject: Re: [PATCH 2/2] MIPS: generic: Allow R5 CPUs to be selected
Date: Tue, 30 May 2023 16:37:40 +0300	[thread overview]
Message-ID: <20230530133740.2w2sbqg3hjhe2q2q@mobilestation> (raw)
In-Reply-To: <20230529135245.4085-2-jiaxun.yang@flygoat.com>

On Mon, May 29, 2023 at 02:52:45PM +0100, Jiaxun Yang wrote:
> Since we do have P5600 bitfile for boston board, we should
> allow generic kernel to be compiled for R5 CPUs.

Would be good to place the outcomes from the Patch 1/2 discussion here.

> 
> Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>

Anyway. Thanks for the patch.
Reviewed-by: Serge Semin <fancer.lancer@gmail.com>

-Serge(y)

> ---
>  arch/mips/Kconfig | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig
> index e437bf43ecfc..215fcdc059d2 100644
> --- a/arch/mips/Kconfig
> +++ b/arch/mips/Kconfig
> @@ -154,9 +154,11 @@ config MIPS_GENERIC_KERNEL
>  	select SWAP_IO_SPACE
>  	select SYS_HAS_CPU_MIPS32_R1
>  	select SYS_HAS_CPU_MIPS32_R2
> +	select SYS_HAS_CPU_MIPS32_R5
>  	select SYS_HAS_CPU_MIPS32_R6
>  	select SYS_HAS_CPU_MIPS64_R1
>  	select SYS_HAS_CPU_MIPS64_R2
> +	select SYS_HAS_CPU_MIPS64_R5
>  	select SYS_HAS_CPU_MIPS64_R6
>  	select SYS_SUPPORTS_32BIT_KERNEL
>  	select SYS_SUPPORTS_64BIT_KERNEL
> -- 
> 2.39.2 (Apple Git-143)
> 

  reply	other threads:[~2023-05-30 13:37 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 [this message]
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
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=20230530133740.2w2sbqg3hjhe2q2q@mobilestation \
    --to=fancer.lancer@gmail.com \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --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.