linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Matt Porter <mporter@embeddedalley.com>
To: Benjamin Delagoutte <BDE@teamlog.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: ARCH=ppc or ARCH=powerpc
Date: Thu, 24 Aug 2006 08:23:38 -0500	[thread overview]
Message-ID: <20060824132338.GA27468@gate.crashing.org> (raw)
In-Reply-To: <1156424295.19482.11.camel@localhost>

On Thu, Aug 24, 2006 at 02:58:15PM +0200, Benjamin Delagoutte wrote:
> Le jeudi 24 août 2006 à 07:49 -0500, Josh Boyer a écrit :
> > On Thu, 2006-08-24 at 05:38 -0700, Parav Pandit wrote:
> > > ppc = 32bit.
> > > powerpc= 64bit.
> > > Correct me if I am wrong.
> > 
> > Yes, you're wrong.  Some 32 bit boards are also under arch/powerpc now.
> > 
> > >  
> > > I am not sure why community didn't adopt the name ppc and ppc64 just
> > > like ia-32 and ia64.
> > 
> > They did originally.
> > 
> > The new direction is to have everything under arch/powerpc, both 32 and
> > 64 bit.  The reason arch/ppc still exists is because some 32 bit
> > platforms have not been fully migrated to the requirements to be merged
> > into arch/powerpc.  Namely, the code has to boot from an OpenFirmware
> > like flattened device tree.  The PPC 4xx family of processors, as an
> > example, does not do this yet though there is work going on to adapt it.
> 
> I'm currently working on a PPC 405 based developement card. Does it mean
> I have to work using the arch/ppc tree ? 

PPC405 is only supported in the arch/ppc tree currenty. Unless you
want to contribute to the effort to move to arch/powerpc, you'll
have to work with arch/ppc/

> What about the includes ? Do I have to use only include/asm-ppc or are
> include/asm-powerpc necessary as well ?

When you do an arch/ppc build it automagically includes shared
includes from asm-powerpc as necessary. There's nothing to worry
about there.

The goal is to have the new 4xx arch/powerpc support not break 4xx
arch/ppc support. So as boards are merged and verified working,
we'll remove the equivalent support from arch/ppc...

Some boards/chips may just die if no maintainer step up to port
them over...but all the important stuff should get an interested
party once we get the initial 4xx support in arch/powerpc working.

-Matt

  parent reply	other threads:[~2006-08-24 13:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-24 10:28 ARCH=ppc or ARCH=powerpc Benjamin Delagoutte
2006-08-24 12:38 ` Parav Pandit
2006-08-24 12:49   ` Josh Boyer
2006-08-24 12:58     ` Benjamin Delagoutte
2006-08-24 13:07       ` Josh Boyer
2006-08-24 13:26         ` Matt Porter
2006-08-24 13:23       ` Matt Porter [this message]
2006-09-15 23:06         ` Shawn Jin
2006-09-15 23:23           ` Josh Boyer
2007-06-28  1:14             ` Kumar Gala
2006-08-24 12:58     ` Parav Pandit
  -- strict thread matches above, loose matches on Subject: below --
2007-06-27 21:41 Bizhan Gholikhamseh (bgholikh)
2007-06-28  1:20 ` Kumar Gala
2007-06-28  7:44   ` Erik Christiansen
2007-06-28  8:36     ` Erik Christiansen
2007-06-29  3:15       ` Kumar Gala
2007-07-01  1:07   ` Josh Boyer
2007-06-28  2:30 ` Bhupender Saharan

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=20060824132338.GA27468@gate.crashing.org \
    --to=mporter@embeddedalley.com \
    --cc=BDE@teamlog.com \
    --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;
as well as URLs for NNTP newsgroup(s).