orion/kirkwood and device tree support

orion/kirkwood and device tree support

[Michael Walle]

Dear orion/kirkwood maintainers,

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. 

Are there any plans or even ongoing developments to convert these platforms to 
support device trees?

What is the best way to convert the {orion,kirkwood}_*_init() calls to DT? 
Make each device use a device_driver structure for initialization?

-- 
Michael

orion/kirkwood and device tree support

[Jason]

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.