From: David Gibson <david@gibson.dropbear.id.au>
To: Satya <satyakiran@gmail.com>
Cc: David Woodhouse <dwmw2@infradead.org>, Linuxppc-dev@ozlabs.org
Subject: Re: Patches for ppc?
Date: Tue, 21 Aug 2007 15:25:14 +1000 [thread overview]
Message-ID: <20070821052514.GC21169@localhost.localdomain> (raw)
In-Reply-To: <acbcf3840708171628k242e96ffl2b65011bf6d39512@mail.gmail.com>
On Fri, Aug 17, 2007 at 06:28:50PM -0500, Satya wrote:
> hi,
> what's the issue with arch/ppc again? why is it being phased out? I
> am
It's a crusty, nasty, old codebase that we want to replace with the
newer and nicer arch/powerpc.
> working with the IBM Blue Gene/L which is based on ppc440. I need to
> get a patch in too! :)
>
> I noticed that head_44x.S has been copied to arch/powerpc/kernel in
> the current head tree, but is it functional yet? has everything been
> moved to arch/powerpc ? how about the include files ?
It's not a question of indivudual files being copied over - things are
done differently in arch/powerpc. Things are gradually being ported
over to arch/powerpc as people get the time - that's why arch/ppc
isn't gone yet. 440 support is now in arch/powerpc, but is not yet
complete: it works, but is missing some fairly important device
support (RTC and PCI are the most prominent).
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2007-08-21 5:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-17 7:43 Patches for ppc? Johan Borkhuis
2007-08-17 8:00 ` Kumar Gala
2007-08-17 12:26 ` David Woodhouse
2007-08-17 14:36 ` Johan Borkhuis
2007-08-17 14:40 ` David Woodhouse
2007-08-17 14:43 ` Johan Borkhuis
2007-08-17 23:28 ` Satya
2007-08-21 5:25 ` David Gibson [this message]
2007-08-21 15:14 ` Segher Boessenkool
2007-08-21 16:11 ` Phil Terry
2007-08-21 16:35 ` Josh Boyer
2007-08-21 16:40 ` Kumar Gala
2007-08-21 17:12 ` Phil Terry
2007-08-21 17:30 ` Scott Wood
2007-08-21 18:09 ` Segher Boessenkool
2007-08-21 17:22 ` Linas Vepstas
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=20070821052514.GC21169@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=Linuxppc-dev@ozlabs.org \
--cc=dwmw2@infradead.org \
--cc=satyakiran@gmail.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).