Currently we have two important u-boot trees, one for omap 4 and another for omap 3.
For omap 4 sakoman is improving and pushing the patches upstream already, and I saw that currently we have a very good support upstream (most of sakoman's patches were merged yesterday).
For omap 3 the best tree is still the beagleboard-validation one, at http://gitorious.org/beagleboard-validation/u-boot/. Probably in the future there's going to be some work trying to push the patches upstream, but currently I can't see anyone really focused on that.
So now the question now is which tree should we use for our images? The older u-boot, the one we currently use, is very very old (4 years), and probably every bug we find in the u-boot code base will be also a pain to fix.
As an example, this bug is very important, as it breaks every kernel update, and I can confirm that this doesn't happen with latest upstream u-boot code (hash 69a2a4d9a5884a6f2d04a551308980d452b9b349).
Currently we have two important u-boot trees, one for omap 4 and another for omap 3.
For omap 4 sakoman is improving and pushing the patches upstream already, and I saw that currently we have a very good support upstream (most of sakoman's patches were merged yesterday).
For omap 3 the best tree is still the beagleboard- validation one, at http:// gitorious. org/beagleboard -validation/ u-boot/. Probably in the future there's going to be some work trying to push the patches upstream, but currently I can't see anyone really focused on that.
So now the question now is which tree should we use for our images? The older u-boot, the one we currently use, is very very old (4 years), and probably every bug we find in the u-boot code base will be also a pain to fix.
As an example, this bug is very important, as it breaks every kernel update, and I can confirm that this doesn't happen with latest upstream u-boot code (hash 69a2a4d9a5884a6 f2d04a551308980 d452b9b349) .