Steve, > 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. I have not compiled DTB with kernel!!! This not make sense. This was the first thing which I removed some month ago. I registered discussion about incorporating DTB to bitstream. It's bogus because if you do it, you can't change any parameters. If you want to DTB in your design, you can add xps_bram (or whatever) to your design and you can load DTB with bitstream. M > 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 > >> -----Original Message----- >> From: John Williams [mailto:john.williams@xxxxxxxxxxxxx] >> Sent: Monday, May 05, 2008 4:17 PM >> To: Stephen Neuendorffer >> Cc: monstr@xxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; arnd@xxxxxxxx; > linux-arch@xxxxxxxxxxxxxxx; John >> Linn; matthew@xxxxxx; will.newton@xxxxxxxxx; drepper@xxxxxxxxxx; > microblaze-uclinux@xxxxxxxxxxxxxx; >> grant.likely@xxxxxxxxxxxx; Michal Simek >> Subject: RE: [PATCH 10/56] microblaze_v2: Generic dts file for > platforms >> 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-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
