From: Jason <linux_arm@lakedaemon.net>
To: Michael Walle <michael@walle.cc>
Cc: devicetree-discuss@lists.ozlabs.org,
Lennert Buytenhek <kernel@wantstofly.org>,
linux-arm-kernel@lists.infradead.org,
Nicolas Pitre <nico@fluxnic.net>
Subject: Re: orion/kirkwood and device tree support
Date: Mon, 10 Oct 2011 07:23:22 -0400 [thread overview]
Message-ID: <20111010112322.GJ31288@titan.lakedaemon.net> (raw)
In-Reply-To: <201110091545.55645.michael@walle.cc>
Resend, messed up my email alias. I'm a dork. :-( Apologies.
Michael,
On Sun, Oct 09, 2011 at 03:45:55PM +0200, Michael Walle wrote:
> I submitted a patch to support the Buffalo LS-XHL three months ago, which was
> rejected because no more old fashioned board setup patches will be merged.
We have the same situation with the dreamplug (kirkwood based).
> Are there any plans or even ongoing developments to convert these platforms to
> support device trees?
I'm attempting to, but that requires my learning devicetree. Which is
fine in and of itself, but it also means I'm learning how Linux supports
arm SoCs. Which is taking some time. My current thought process is this:
1.) add arch/arm/mach-kirkwood/board-dt.c, arch/arm/boot/dts/kirkwood.dtsi,
and arch/arm/boot/dts/kirkwood-dreamplug.dts
2.) fill it in with replacements of calls in common.c and irq.c
3.) get it working cleanly.
4.) add in calls from mpp.c, pcie.c, and cpuidle.c
5.) build arch/arm/boot/dts/kirkwood-*.dts for other boards.
I'd be happy to coordinate and test, although I have no buffalo gear.
And I sure would appreciate some help. ;-)
thx,
Jason.
prev parent reply other threads:[~2011-10-10 11:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201110091545.55645.michael@walle.cc>
[not found] ` <201110091545.55645.michael-QKn5cuLxLXY@public.gmane.org>
2011-10-09 16:23 ` orion/kirkwood and device tree support Jason
2011-10-10 11:23 ` Jason [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=20111010112322.GJ31288@titan.lakedaemon.net \
--to=linux_arm@lakedaemon.net \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=kernel@wantstofly.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=michael@walle.cc \
--cc=nico@fluxnic.net \
/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