The main thing that Grant's script lacks is the ability to pull in default parameters that aren't listed in the MPD for a core, but not in the MHS file... I think the only way to easily solve that is to live within EDK's bsp generation, unfortunately...
BTW: I'm currently hacking away to see if I can get a microblaze system booting using a flat device tree... I haven't decided if it's worth it to go that route in the end yet, but... Steve > -----Original Message----- > From: > [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] labs.org] On Behalf Of Grant Likely > Sent: Friday, August 10, 2007 6:48 AM > To: Koss, Mike (Mission Systems) > Cc: [email protected] > Subject: Re: Device Tree tool [was RE: [PATCH] Consolidate > XILINX_VIRTEX boardsupport] > > On 8/10/07, Koss, Mike (Mission Systems) <[EMAIL PROTECTED]> wrote: > > > > <<SNIPPAGE>> > > > > > diff --git a/arch/ppc/platforms/4xx/xparameters/xparameters.h > > > > > b/arch/ppc/platforms/4xx/xparameters/xparameters.h > > > > > index 01aa043..34d9844 100644 > > > > > --- a/arch/ppc/platforms/4xx/xparameters/xparameters.h > > > > > +++ b/arch/ppc/platforms/4xx/xparameters/xparameters.h > > > > > @@ -15,8 +15,12 @@ > > > > > > > > > > #if defined(CONFIG_XILINX_ML300) > > > > > #include "xparameters_ml300.h" > > > > > +#elif defined(CONFIG_XILINX_XUPV2P) #include > > > > > +"xparameters_xupv2p.h" > > > > > #elif defined(CONFIG_XILINX_ML403) > > > > > #include "xparameters_ml403.h" > > > > > +#elif defined(CONFIG_XILINX_ML41x) > > > > > + #include "xparameters_ml41x.h" > > > > > #else > > > > > /* Add other board xparameter includes here before > the #else */ > > > > > #error No xparameters_*.h file included > > > > > > > > see comment above. > > > > > This whole xparams stuff is a special case; but it is > going away for > > arch/powerpc. xparameters.h is generated by the xilinx EDK > tool and it > > is painful to work with in the Linux context. For > arch/powerpc, I've > > got a tool that generates a device tree from the FPGA > hardware design. > > > > What is the tool that you are using and are you willing to > share it at > > this point? I'm currently working on some code to generate platform > > files for our internal drivers and the ll_temac vs using the ugle > > xparam's file. I'd like to not duplicate, or actually > assist, any effort > > in this area. > > It's on my git tree; http://git.secretlab.ca > > I've also got some feedback from the Xilinx folks in the form of a > patch, but I haven't integrated it yet. Pretty experimental stuff, > I'll probably end up rewriting it from scratch before it's done. > > Cheers, > g. > > > > > -- Mike Koss > > > > > > > -- > Grant Likely, B.Sc., P.Eng. > Secret Lab Technologies Ltd. > [EMAIL PROTECTED] > (403) 399-0195 > _______________________________________________ > Linuxppc-embedded mailing list > [email protected] > https://ozlabs.org/mailman/listinfo/linuxppc-embedded > > _______________________________________________ Linuxppc-embedded mailing list [email protected] https://ozlabs.org/mailman/listinfo/linuxppc-embedded
