Hi Michael, Michal Simek wrote:
That's the whole point of what we did to u-boot with auto-config - it just works on any board - there is just a generic microblaze-auto BSP, and it uses autoconfig to get the necessary parameters.What about Spartan-3e support? I don't have ml401 to test...You don't have to use it if you don't want to, but understand there is a reason we did it that way...You are absolutely right.I made the similar one BSP autoconfig system, because Petalogix eg. John use auto-config.h for U-BOOT and uClinux but for upload whole auto-config.h to U-BOOT tree is unacceptible.Auto-config.h is very huge.
Perhaps a solution here is to commit a stripped version of auto-config.h into the u-boot tree, on the understanding that it is dynamically generated for each new system anyway?
I think all that's really needed is the RAM and FLASH settings, CPU configuration, and any network device support (emac / emaclite).
I concede that much (most?) of auto-config.h contents are not required by u-boot. In PetaLinux it's actually a symlink to the kernel's autoconf.h, but understand that nothing will go into the main u-boot repository that imposes a dependency on PetaLinux.
Cheers, John ___________________________ microblaze-uclinux mailing list microblaze-uclinux@xxxxxxxxxxxxxx Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/