The .dts is not board specific, it's design specific.  In my opinion,
this is not something that 'a vendor might maintain multiple versions
of': instead it is in most cases simply fundamental to the FPGA design
flow.  In fact, in most cases, I'd like to make the .dts file part of
the bitstream and not compiled into the kernel.

Although powerpc has a bit more boot-time complexity than the microblaze
does currently, I think it makes alot of sense to have some consistency
here, and there is already a pattern to follow here which nicely
orthogonalizes multiple .dts files for the same platform code.

Steve

quoted text
> -----Original Message-----
> From: John Williams [mailto:john.williams@petalogix.com]
> Sent: Monday, May 05, 2008 4:17 PM
> To: Stephen Neuendorffer
> Cc: monstr@seznam.cz; linux-kernel@vger.kernel.org; arnd@arndb.de;
linux-arch@vger.kernel.org; John
quoted text
> Linn; matthew@wil.cx; will.newton@gmail.com; drepper@redhat.com;
microblaze-uclinux@itee.uq.edu.au;
quoted text
> grant.likely@secretlab.ca; Michal Simek
> Subject: RE: [PATCH 10/56] microblaze_v2: Generic dts file for
platforms
quoted text
> 
> 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
quoted text
> dir and into microblaze/boot, like we do with the finished kernel?
Then
quoted text
> it's ready to be picked up by the user or some higher level build
tool.
quoted text
> 
> 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
quoted text
> intended target remains obvious.
> 
> John
> 
> 
> >
> > Steve
> >
> > > -----Original Message-----
> > > From: monstr@seznam.cz [mailto:monstr@seznam.cz]
> > > Sent: Sunday, May 04, 2008 4:41 AM
> > > To: linux-kernel@vger.kernel.org
> > > Cc: arnd@arndb.de; linux-arch@vger.kernel.org; Stephen
Neuendorffer;
quoted text
> > John Linn;
> > > john.williams@petalogix.com; matthew@wil.cx;
will.newton@gmail.com;
quoted text
> > drepper@redhat.com; microblaze-
> > > uclinux@itee.uq.edu.au; grant.likely@secretlab.ca; Michal Simek
> > > Subject: [PATCH 10/56] microblaze_v2: Generic dts file for
platforms
quoted text
> > >
> > > From: Michal Simek <monstr@monstr.eu>
> > >
> > >
> > > Signed-off-by: Michal Simek <monstr@monstr.eu>
> > > ---
> > >  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
> 
> 


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