LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Becky Bruce <becky.bruce@freescale.com>
To: jie han <jiehanca@yahoo.com.cn>
Cc: "linuxppc-embedded@ozlabs.org" <linuxppc-embedded@ozlabs.org>
Subject: Re: issue about CONFIG_PPC_MMU and CONFIG_SMP define
Date: Tue, 11 Mar 2008 10:53:15 -0500	[thread overview]
Message-ID: <E8F6B026-A4C0-46F7-9A70-2EF42C0CD019@freescale.com> (raw)
In-Reply-To: <604678.57629.qm@web15104.mail.cnb.yahoo.com>

On Mar 10, 2008, at 3:15 PM, jie han wrote:

> Hi guys,
>
> I want to simulate compile mutli-core using sequoia(IBM/AMCC 44x  
> processor) source code under kernel arch/powerpc directory.I want  
> to define CONFIG_SMP, I sould define CONFIG_STD_MMU at first,but  
> AMCC 44x don't need to config CONFIG_STD_MMU.Is CONFIG_STD_MMU just  
> for freescale chip? How can I do next? Thanks ahead for your help,

STD_MMU is for all powerpc cpus with a non-BookE MMU.  That includes  
all the 64-bit parts from IBM to date, pasemi's parts, and 32-bit  
parts from IBM & Freescale like the 6xx, 7xx, 7xxx, e600 e300, etc.   
You cannot set this for 44x, because it is a BookE part.

BTW, there's no real relationship between STD_MMU and SMP.  It was  
just a convenient way to restrict the SMP config option in the  
kernel, since all the Linux configs that currently support SMP are  
STD_MMU. We will have BookE configs in the future that do support  
SMP, at which point arch/powerpc/platforms/Kconfig.cputype will be  
changed to allow SMP to be set for those configs.

You can't enable SMP on 44x right now.  It's not supported.

Cheers,
B

      reply	other threads:[~2008-03-11 15:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-10 20:15 issue about CONFIG_PPC_MMU and CONFIG_SMP define jie han
2008-03-11 15:53 ` Becky Bruce [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=E8F6B026-A4C0-46F7-9A70-2EF42C0CD019@freescale.com \
    --to=becky.bruce@freescale.com \
    --cc=jiehanca@yahoo.com.cn \
    --cc=linuxppc-embedded@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