Sorting out the various issues we actually observe with various MLO & uboot & kernel combinations on Beagle, yesterday at IRC there was the idea to track the various combinations and their symptoms . With something like a table/matrix with working/not working MLO & uboot & kernel combinations, we hopefully will get a better overview. And then a better idea about the root causes of some issues This table/matrix should contain pointers to the working/not working MLO & uboot & kernel versions, too. To not loose the overview, the number of combinations have to be limited, though.
Currently I'm aware of the following (main*) MLO & uboot & kernel versions (MLO & uboot have to fit together):
a) "Default" MLO & uboot (381 MHz, L2 cache at kernel jump disabled)
b) "500MHz" MLO & uboot (L2 cache at kernel jump disabled)
c) "2.6.22 WTBU" kernel
d) "OMAP git" kernel
Runtime version checking: As clock and L2 cache seem to have big influence, we should always check/identify them at runtime. For clock I propose to use BogoMIPS (379.19 == 381 MHz, 499.92 == 500MHz). The WTBU kernel doesn't seem to have this nice "Clocking rate (Crystal/DPLL/ARM core): 26.0/332/500 MHz" output from git kernel.
For L2 cache I propose to apply my kernel patch  and observe the output.
Additionally, we should ensure that our boards have no known HW issues and HW errata 2 & 4  are fixed on the board used for testing. Revision A5 boards should have both fixed, but re-checking can't be wrong
*Note: "main" versions: Not using binaries, but self compiled versions, there may be differences (toolchain, additional patches)