From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Christophe Leroy <christophe.leroy@c-s.fr>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/6] powerpc/32s: add an option to exclusively select powerpc 601
Date: Mon, 2 Sep 2019 13:29:36 +1000 (AEST) [thread overview]
Message-ID: <46MFv46j2Qz9sPJ@ozlabs.org> (raw)
In-Reply-To: <d644eaf7dff8cc149260066802af230bdf34fded.1566834712.git.christophe.leroy@c-s.fr>
On Mon, 2019-08-26 at 15:52:13 UTC, Christophe Leroy wrote:
> Powerpc 601 is rather old powerpc which as some important
> limitations compared to other book3s/32 powerpcs:
> - No Timebase.
> - Common BATs for instruction and data.
> - No execution protection in segment registers.
> - No RI bit in MSR
> - ...
>
> It is starting to be difficult and cumbersome to maintain
> kernels that are compatible both with 601 and other 6xx cores.
>
> Create a compiletime option to exclusively select either powerpc 601
> or other 6xx.
>
> Signed-off-by: Christophe Leroy <christophe.leroy@c-s.fr>
Series applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/f7a0bf7d904e902e13024986b7b357181ee30849
cheers
prev parent reply other threads:[~2019-09-02 4:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 15:52 [PATCH 1/6] powerpc/32s: add an option to exclusively select powerpc 601 Christophe Leroy
2019-08-26 15:52 ` [PATCH 2/6] powerpc/32s: get rid of CPU_FTR_601 feature Christophe Leroy
2019-08-26 15:52 ` [PATCH 3/6] powerpc/32s: drop CPU_FTR_USE_RTC feature Christophe Leroy
2019-08-26 15:52 ` [PATCH 4/6] powerpc/32s: use CONFIG_PPC_BOOK3S_601 instead of reading PVR Christophe Leroy
2019-08-26 15:52 ` [PATCH 5/6] powerpc/32: drop CPU_FTR_UNIFIED_ID_CACHE Christophe Leroy
2019-08-26 15:52 ` [PATCH 6/6] powerpc/32: don't use CPU_FTR_COHERENT_ICACHE Christophe Leroy
2019-09-02 3:29 ` Michael Ellerman [this message]
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=46MFv46j2Qz9sPJ@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=benh@kernel.crashing.org \
--cc=christophe.leroy@c-s.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).