In message 4630F14C.8020705@ovro.caltech.edu you wrote:
This sounds like a good idea. I am developing a custom MPC8349E board that I'll submit a U-Boot patch for when its done. I also plan to build a test-suite that executes as a u-boot stand-alone application. Its not clear to me that such a test suite should also be added into the U-Boot source, since its board-specific; more so than whatever changes to the current
If you are willing to release your code under GPL, it is definitely welcome to be added to the U-Boot source tree. In cases whwere this code is board-specific it makes sense to add it to the specfic board directory. Thi shas been done before in similar cases.
I figured I'd submit the board support patch, and then just maintain the test-suite locally, with an email reference in a u-boot README to anyone who wanted to get access to the test-suite code. Of course, if lots of people build test suites using U-Boot, and there is common code, I'd be happy to use it. I just haven't looked for it in the source yet.
There are several test utilities, but no general infrastructure yet.
Best regards,
Wolfgang Denk