From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Marvin <marvin24@gmx.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: 32-bit kernel on PPC64 supported?
Date: Sat, 19 Jul 2008 08:14:35 +1000 [thread overview]
Message-ID: <1216419275.7740.459.camel@pasglop> (raw)
In-Reply-To: <200807182043.08991.marvin24@gmx.de>
On Fri, 2008-07-18 at 20:43 +0200, Marvin wrote:
> Hi,
>
> while trying to cleanup some configs/makefiles for ppc64 I noticed, that
> CONFIG_POWER4 implies CONFIG_PPC64 and vice versa in all defconfigs.
> So I want to boldly replace CONFIG_POWER4 by CONFIG_PPC64 - ugh.
No, those are different.
CONFIG_PPC64 means a 64 bits kernel.
CONFIG_POWER4 means a 64 bits kernel that only runs on IBM POWER4 and
later (ie, processors conforming to, iirc, version 2.01 or later of
the architecture).
That is, it's legal to have CONFIG_PPC64 and !CONFIG_POWER4, and this
is even necessary if you want to boot on a POWER3 or an RS64 processor.
Now, there also used to be some 32 bits support for POWER4 and G5 but
that has been dropped a while ago.
Cheers,
Ben.
next prev parent reply other threads:[~2008-07-18 22:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 18:43 32-bit kernel on PPC64 supported? Marvin
2008-07-18 21:24 ` Arnd Bergmann
2008-07-18 22:14 ` Benjamin Herrenschmidt [this message]
2008-07-19 7:29 ` Marvin
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=1216419275.7740.459.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=marvin24@gmx.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 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).