[PATCH 0/5 v2] mv643xx_eth: device tree bindings

Jason Cooper jason at lakedaemon.net
Mon Apr 15 09:43:25 EDT 2013


On Mon, Apr 15, 2013 at 04:07:14AM +0100, Ben Hutchings wrote:
> On Sat, 2013-04-13 at 15:00 -0400, Jason Cooper wrote:
> > On Sat, Apr 13, 2013 at 05:21:26PM +0200, Thomas Petazzoni wrote:
> > > Dear Jason Cooper,
> > > 
> > > On Thu, 11 Apr 2013 12:53:03 -0400, Jason Cooper wrote:
> > > 
> > > > With this and Thomas' pci series, we will have Kirkwood fully
> > > > converted to devicetree, can begin removing board files, and finally
> > > > begin migrating everything over to mach-mvebu/.  This will lead to
> > > > the removal of five directories under arch/arm/ (plat-orion,
> > > > mach-kirkwood, mach-orion5x, mach-dove, and mach-mv78xx0).
> > > 
> > > No, we can't remove mach-orion5x and mach-mv78xx0 for now, they have
> > > not been converted at all in terms of gpio/pinmux support. I've started
> > > writing some pinmux code for orion5x but it's not ready.
> [...]
> > Also, I have a feeling that not all legacy boards will get converted
> > over.  If there is no interest or no way to test, certains boards may
> > get deprecated.
> 
> Debian supports many Kirkwood and Orion 5x systems.  A call for testing
> on the debian-arm at lists.debian.org list might be worthwhile.

definitely.

> I would be very glad to see kirkwood, orion5x and mv78xx0 merged - we
> build natively and this takes about 8 hours for each configuration.

That's the plan, build an armv5 kernel, and dtb's for all the boards.
Then, an armv7 kernel for the armadaXP/370 boards, etc.

thx,

Jason.



More information about the linux-arm-kernel mailing list