linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Marvin <marvin24@gmx.de>
To: linuxppc-dev@ozlabs.org
Subject: 32-bit kernel on PPC64 supported?
Date: Fri, 18 Jul 2008 20:43:08 +0200	[thread overview]
Message-ID: <200807182043.08991.marvin24@gmx.de> (raw)


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.

However, there are some constructs like:

#ifndef CONFIG_PPC64
...
#ifdef CONFIG_POWER4
...
#endif
...
#endif /* CONFIG_PPC64 */

in which POWER4 is always undefined, e.g. in 
include/asm-powerpc/mmu_context.h. Maybe this is a leftover from times, where 
64-bit kernels where not supported on Powermacs. Is this 32-bit support still 
necessary?

Greetings

Marvin

             reply	other threads:[~2008-07-18 18:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-18 18:43 Marvin [this message]
2008-07-18 21:24 ` 32-bit kernel on PPC64 supported? Arnd Bergmann
2008-07-18 22:14 ` Benjamin Herrenschmidt
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=200807182043.08991.marvin24@gmx.de \
    --to=marvin24@gmx.de \
    --cc=linuxppc-dev@ozlabs.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).