From: "Grant Likely" <grant.likely@secretlab.ca>
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: Sat, 19 Apr 2008 10:27:07 -0600 [thread overview]
Message-ID: <fa686aa40804190927u1067bd00m5734dd8b2aa84d0b@mail.gmail.com> (raw)
In-Reply-To: <D713F373-AE2A-4341-9C29-EF65B9399B36@kernel.crashing.org>
On Sat, Apr 19, 2008 at 9:30 AM, 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.
>
> LITE5200 52xx
This is in arch/powerpc
> XILINX_ML300 40x
> XILINX_ML403 40x
These are also supported in arch/powerpc; we just don't have .dts
files for the reference designs merged yet.
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2008-04-19 16:27 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 [this message]
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
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=fa686aa40804190927u1067bd00m5734dd8b2aa84d0b@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--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).