linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn Jin" <shawnxjin@gmail.com>
To: "Matt Porter" <mporter@embeddedalley.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: ARCH=ppc or ARCH=powerpc
Date: Fri, 15 Sep 2006 16:06:14 -0700	[thread overview]
Message-ID: <c3d0340b0609151606i2d01b963h4c7cd6a182d8c80@mail.gmail.com> (raw)
In-Reply-To: <20060824132338.GA27468@gate.crashing.org>

Hi Matt,

> 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.

When can we expect this done? I have a 440 based SoC project ongoing
and am thinking when I should start moving to arch/powerpc.

THanks,
-Shawn.

  reply	other threads:[~2006-09-15 23:06 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
2006-09-15 23:06         ` Shawn Jin [this message]
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=c3d0340b0609151606i2d01b963h4c7cd6a182d8c80@mail.gmail.com \
    --to=shawnxjin@gmail.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=mporter@embeddedalley.com \
    /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).