From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: status of mpc52xx with arch=powerpc?
Date: Wed, 25 Oct 2006 11:46:55 +1000 [thread overview]
Message-ID: <1161740815.22582.1.camel@localhost.localdomain> (raw)
In-Reply-To: <528646bc0610180652u2ee8e8b4xe25d555a59a27c85@mail.gmail.com>
On Wed, 2006-10-18 at 07:52 -0600, Grant Likely wrote:
> On 10/18/06, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> > Is someone working on this already?
> >
> > There are some Kconfig entries, but there seems to be no code, at least
> > not in vanilla.
>
> I'm slowly working on it. I've got a .dts written and I've got u-boot
> w/ the fdt patches running on the board. I need to port the 52xx PIC
> driver into arch/powerpc before I attempt to boot.
Can you send me your .dts ? The bplan folks are doing things for their
EFIKA board and I didn't manage to get them to open up publically their
device-tree until the firmware is final and in production :( But I've
got them to change a few things already, and I'd like to make sure
things are in sync.
Regarding devices, I want to move everything to of_platform_device. I
have some patches in progress to make those easier to work with. I'll
send something in the upcoming couple of days as it's all part of some
Cell related work for a new southbridge.
I'm trying to make sure the bplan stuff and whatever you guys come up
with don't conflict.
Ben.
next prev parent reply other threads:[~2006-10-25 1:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 13:06 status of mpc52xx with arch=powerpc? Sascha Hauer
2006-10-18 13:52 ` Grant Likely
2006-10-19 8:13 ` Sascha Hauer
2006-10-19 9:49 ` Roman Fietze
2006-10-19 14:17 ` Sascha Hauer
2006-10-19 14:46 ` Grant Likely
2006-10-19 17:21 ` John Rigby
2006-10-25 1:46 ` Benjamin Herrenschmidt [this message]
2006-10-25 6:25 ` Grant Likely
2006-10-26 20:07 ` John Rigby
2006-10-26 20:36 ` Grant Likely
2006-10-26 20:48 ` Sylvain Munaut
2006-10-27 22:39 ` Benjamin Herrenschmidt
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=1161740815.22582.1.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=grant.likely@secretlab.ca \
--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).