one more question, i think, on the framework of u-boot POST tests. the README.POST file states:
o) Extensibility The framework shall allow adding/removing/replacing POST tests. Also, standalone POST tests shall be supported. how many different ways are there to extend the list of POST tests? given that post/tests.c defines the list of tests statically, you clearly can't *dynamically* add tests. i do see that that list of tests includes the generic tests: #if CONFIG_POST & CONFIG_SYS_POST_BSPEC1 CONFIG_POST_BSPEC1, #endif #if CONFIG_POST & CONFIG_SYS_POST_BSPEC2 CONFIG_POST_BSPEC2, #endif #if CONFIG_POST & CONFIG_SYS_POST_BSPEC3 CONFIG_POST_BSPEC3, #endif #if CONFIG_POST & CONFIG_SYS_POST_BSPEC4 CONFIG_POST_BSPEC4, #endif #if CONFIG_POST & CONFIG_SYS_POST_BSPEC5 CONFIG_POST_BSPEC5, #endif so, sure, one can take advantage of any of those five available test slots, but that's not really a general solution. so other than editing post/tests.c and manually adding more tests, is there any other mechanism for adding POST tests? rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot