On 10/28/2015 04:56 AM, Alex Gagniuc wrote:
>
> How will moving [AGESA] code [to a separate branch] affect supported [AMD] boards?
>
The biggest problem here is:
Various improvements and important bug fixes, that will be introduced to a master branch and affect all the coreboot boards, will not be automatically applied to that separate AMD branch. Those coreboot developers which have AMD boards and want to constantly use and test latest and greatest coreboot builds, they will have to constantly check the coreboot commit log and backport all these improvements and fixes to their separate (and soon to be abandoned) AMD branch. That will be adding lots of unnecessary manual work and draining lots of workhours, which otherwise could have been spent on writing the bug reports or improving a coreboot code which is common for all the coreboot-supported boards.
As result, moving AGESA code will affect - and not only AMD boards: all the coreboot supported boards will be indirectly negatively affected by that change...
Luckily Timothy Pearson has advised a perfect solution for this issue:
On 28 October 2015 at 02:23, Timothy Pearson wrote:
>
> Perhaps in the short term we can port the remaining AGESA Fam15h boards
> to native init, and look into moving Fam14h to as much native as
> possible while still keeping the PSP happy with its blobs?
>
If the AGESA boards will be ported to a native init, they will be able to continue to be supported by a master branch! That approach will allow coreboot developers with AMD boards to avoid spending time on backporting the changes and concentrate on developing and testing the latest coreboot builds from a master branch
Best regards,
Vladimir Shipovalov