<<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. -- Mike Koss _______________________________________________ Linuxppc-embedded mailing list [email protected] https://ozlabs.org/mailman/listinfo/linuxppc-embedded
