I fail to see where there is a significant difference between the Linux kernel and U-Boot: you can patch either of the source trees to your liking, and when you copy a "$(LINUX26_DIR)/.config" file for Linux before running "make oldconfig" and "make uImage" you will copy a "include/configs/<board>.h" file with U-Boot before you run "make".
The only difference, and I agree that it is a significant one, is that you cannot easily auto-generate "include/configs/<board>.h" from a Kconfig based configuration system. You would need at least some helper script, but even this should be straightforward to implement.
I consider it acceptable to have "include/configs/<board>.h" to be constant for most users of my S/W; but the networking environment will be different. This is different for each user. The memory configuration is also different.
Instead of doing this, which fixes the problem for you while leaving the rest of the U-Boot community in the dark, we could also discuss if there is a way to make U-Boot configuration easier for all of us.
This is a major undertaking and a long term project, which I have no chance of driving. If someone decides that u-boot should be configured as part of the buildroot configuration, then I can contribute.
Buildroot will allow me to create the contents of the board.h file in an incremental fashion if I let the automatically generated info override the board.h files. I like that. I do not need to test any boards that I do not have access to.
It seems you prefer the first approach, while I am looking for the latter.
I am not sure I agree that I keep everyone in the dark since I publish the source of my buildroot tree. I would not have any problem providing this and my Atmel customized U-boot to you for inclusion in your ftp site.
Best regards,
Wolfgang Denk
Best Regards Ulf Samuelsson ulf@atmel.com Atmel Nordic AB Mail: Box 2033, 174 02 Sundbyberg, Sweden Visit: Kavallerivägen 24, 174 58 Sundbyberg, Sweden Phone +46 (8) 441 54 22 Fax +46 (8) 441 54 29 GSM +46 (706) 22 44 57
Technical support when I am not available: AT89 C51 Applications Group: mailto:micro.hotline@nto.atmel.com AT90 AVR Applications Group: mailto:avr@atmel.com AT91 ARM Applications Group: mailto:at91support@atmel.com FPSLIC Application Group: mailto:fpslic@atmel.com Best AVR