RE: [PATCH 10/56] microblaze_v2: Generic dts file for platforms

From: John Williams
Date: Mon May 05 2008 - 19:17:56 EST


On Mon, 2008-05-05 at 10:25 -0700, Stephen Neuendorffer wrote:
> I think it would be nice if dts files were stored in boot/dts, as on
> powerpc, which would reduce confusion.

I'm not so sure. By grouping

* the DTS
* Kconfig.auto (now just storing CPU parameters for CPUFLAGS); and
* board-specific setup.c if required,

we concentrate in one place, in a single subdir of
arch/microblaze/platform/*, all of the board specific info.

Maybe our Kbuild should copy the platform .dts file out of the platform
dir and into microblaze/boot, like we do with the finished kernel? Then
it's ready to be picked up by the user or some higher level build tool.

If users or vendors want to maintain multiple DTS files for a single
board, again they can just collect them in the platform subdir so their
intended target remains obvious.

John


>
> Steve
>
> > -----Original Message-----
> > From: monstr@xxxxxxxxx [mailto:monstr@xxxxxxxxx]
> > Sent: Sunday, May 04, 2008 4:41 AM
> > To: linux-kernel@xxxxxxxxxxxxxxx
> > Cc: arnd@xxxxxxxx; linux-arch@xxxxxxxxxxxxxxx; Stephen Neuendorffer;
> John Linn;
> > john.williams@xxxxxxxxxxxxx; matthew@xxxxxx; will.newton@xxxxxxxxx;
> drepper@xxxxxxxxxx; microblaze-
> > uclinux@xxxxxxxxxxxxxx; grant.likely@xxxxxxxxxxxx; Michal Simek
> > Subject: [PATCH 10/56] microblaze_v2: Generic dts file for platforms
> >
> > From: Michal Simek <monstr@xxxxxxxxx>
> >
> >
> > Signed-off-by: Michal Simek <monstr@xxxxxxxxx>
> > ---
> > arch/microblaze/platform/generic/system.dts | 137
> +++++++++++++++++++++++++++
> > 1 files changed, 137 insertions(+), 0 deletions(-)
> > create mode 100644 arch/microblaze/platform/generic/system.dts
>
--
John Williams, PhD, B.Eng, B.IT
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663 f: +61-7-30090663


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/