From: Scott Wood <oss@buserror.net>
To: David Engraf <david.engraf@sysgo.com>
Cc: benh@kernel.crashing.org, paulus@samba.org, mpe@ellerman.id.au,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: powerpc64: Enable CONFIG_E500 and CONFIG_PPC_E500MC for e5500/e6500
Date: Sun, 25 Sep 2016 01:20:17 -0500 [thread overview]
Message-ID: <20160925062017.GA10754@home.buserror.net> (raw)
In-Reply-To: <1471877203-29327-1-git-send-email-david.engraf@sysgo.com>
On Mon, Aug 22, 2016 at 04:46:43PM +0200, David Engraf wrote:
> The PowerPC e5500/e6500 architecture is based on the e500mc core. Enable
> CONFIG_E500 and CONFIG_PPC_E500MC when e5500/e6500 is used.
>
> This will also fix using CONFIG_PPC_QEMU_E500 on PPC64.
>
> Signed-off-by: David Engraf <david.engraf@sysgo.com>
> ---
> arch/powerpc/platforms/Kconfig.cputype | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/arch/powerpc/platforms/Kconfig.cputype b/arch/powerpc/platforms/Kconfig.cputype
> index f32edec..0382da7 100644
> --- a/arch/powerpc/platforms/Kconfig.cputype
> +++ b/arch/powerpc/platforms/Kconfig.cputype
> @@ -125,11 +125,13 @@ config POWER8_CPU
>
> config E5500_CPU
> bool "Freescale e5500"
> - depends on E500
> + select E500
> + select PPC_E500MC
>
> config E6500_CPU
> bool "Freescale e6500"
> - depends on E500
> + select E500
> + select PPC_E500MC
These config symbols are for setting -mcpu. Kernels built with
CONFIG_GENERIC_CPU should also work on e5500/e6500.
The problem is that CONFIG_PPC_QEMU_E500 doesn't select E500 (I didn't
notice it before because usually CORENET_GENERIC is enabled as well).
Note that your patch, by eliminating the dependency on E500, would make
it possible to build a book3s kernel with E5500_CPU/E6500_CPU, which
doesn't make any sense.
-Scott
next prev parent reply other threads:[~2016-09-25 6:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 14:46 [PATCH] powerpc64: Enable CONFIG_E500 and CONFIG_PPC_E500MC for e5500/e6500 David Engraf
2016-09-25 6:20 ` Scott Wood [this message]
2016-09-26 8:48 ` David Engraf
2016-09-26 23:08 ` Scott Wood
2016-10-07 9:00 ` David Engraf
2016-11-15 5:47 ` Scott Wood
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=20160925062017.GA10754@home.buserror.net \
--to=oss@buserror.net \
--cc=benh@kernel.crashing.org \
--cc=david.engraf@sysgo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--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).