On Tue, Jul 9, 2013 at 11:46 PM, Paul Menzel <paulepanter@users.sourceforge.net> wrote:
Dear Google coreboot folks,


thank you for upstreaming your patches.

As there are so many patches, could you please send an overview, so the
big picture is clear. It would be awesome if you could also include a
list of crucial patches, which should get the most attention.

I am not sure if that is possible at all, but it would help to get the
patches in in my opinion.

Tough to say... A lot of these patches are just basic things to add support for new hardware. However, this change deals largely with the code architecture: http://review.coreboot.org/#/c/3640/ 

In general, the motivation for this push was just to try and get the generic ARM code up to date in upstream coreboot, in addition to improvements to the way we do graphics and display init. Much of that work was done to support development of particular products which is why a lot of mainboard code got pushed as well. However, it will also make development of other products (such as Beaglebone) easier for the community at large.
 
And lastly, do you know of a way to order the patches regarding their
dependencies in Gerrit?

That would be nice! I usually just click on a patch and follow its "Depends On" link...

--
David Hendricks (dhendrix)
Systems Software Engineer, Google Inc.