linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Suresh Chandra Mannava" <coreppcdevel@gmail.com>
To: "Kumar Gala" <galak@kernel.crashing.org>
Cc: "linuxppc-dev@ozlabs.org list" <linuxppc-dev@ozlabs.org>,
	LinuxPPC-Embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: removal of arch/ppc in 2.6.27?
Date: Fri, 16 May 2008 19:35:14 +0530	[thread overview]
Message-ID: <543e3890805160705l10e718f2g6e49d842086ec662@mail.gmail.com> (raw)
In-Reply-To: <D713F373-AE2A-4341-9C29-EF65B9399B36@kernel.crashing.org>

[-- Attachment #1: Type: text/plain, Size: 2174 bytes --]

On Sat, Apr 19, 2008 at 9:00 PM, Kumar Gala <galak@kernel.crashing.org>
wrote:

> This is intended as a reminder that we plan on getting rid of arch/ppc this
> summer.  I'm guessing based on kernel release times that will be 2.6.27. That would mean 2.6.26 will be the last kernel to support arch/ppc.
>
> If people have boards that like ported over please let us know and work
> with us to port this over to arch/powerpc.
>
> Here is a list based on arch/ppc/platforms.  Its not intended to be
> complete but a general idea of what's left in arch/ppc.



I am still struggling to make SPRUCE work with 2.6.24 arch/ppc. I think no
body had tested 2.6.x on SPRUCE. I think there is some issue with cpc700 pic
driver.
I feel it is better to move SPRUCE along with other arch/ppc boards to
arch/powerpc

Thanks,
Suresh


>
>
> PPC_PREP        e6xx
> PQ2ADS          82xx            in arch/powerpc?
> TQM8260         82xx
> CPCI690         e6xx/mv64x60
> EV64260         e6xx/mv64x60
> CHESTNUT        e6xx/mv64x60
> LOPEC           e6xx
> KATANA          e6xx/mv64x60
> HDPU            e6xx/mv64x60
> MVME5100        e6xx
> PAL4            e6xx
> POWERPMC250     e6xx
> PPLUS           e6xx
> PRPMC750        e6xx
> PRPMC800        e6xx
> RADSTONE_PPC7D  e6xx
> SANDPOINT       e6xx
> SBC82xx         82xx
> SPRUCE          e6xx
> LITE5200        52xx
> EV64360         e6xx/mv64x60
> MPC86XADS       8xx             in arch/powerpc
> MPC885ADS       8xx             in arch/powerpc
> ADS8272         82xx            in arch/powerpc
>
> 4xx:
> BAMBOO          44x             in arch/powerpc
> CPCI405         40x
> EBONY           44x             in arch/powerpc
> EP405           40x             in arch/powerpc
> BUBINGA         40x
> LUAN            44x
> YUCCA           44x
> OCOTEA          44x
> REDWOOD_5       40x
> REDWOOD_6       40x
> SYCAMORE        40x
> TAISHAN         44x             in arch/powerpc
> WALNUT          40x             in arch/powerpc
> XILINX_ML300    40x
> XILINX_ML403    40x
>
> - k
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
>

[-- Attachment #2: Type: text/html, Size: 3972 bytes --]

      parent reply	other threads:[~2008-05-16 14:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-19 15:30 removal of arch/ppc in 2.6.27? Kumar Gala
2008-04-19 16:27 ` Grant Likely
2008-04-19 18:13 ` Josh Boyer
2008-04-19 20:43 ` Chuck Meade
2008-04-20  0:39 ` Dwayne Fontenot
2008-04-20 11:14 ` Marvin
2008-04-20 12:27   ` Paul Mackerras
2008-04-20 12:55     ` Gabriel Paubert
2008-04-20 13:43     ` Marvin
2008-04-21  8:03     ` David Woodhouse
2008-05-16 14:05 ` Suresh Chandra Mannava [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=543e3890805160705l10e718f2g6e49d842086ec662@mail.gmail.com \
    --to=coreppcdevel@gmail.com \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --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).