> With all due respect, dropping support for the majority of AMD boards
> - with a quite significant community around them! - doesn't seem like
> a wise decision, if we still care about the coreboot marketshare on
> the worldwide-available consumer PCs. Small improvement in the common
> source, but a huge loss of boards? (almost 50!). For the sake of the
> bright future of the coreboot project, this must be prevented at all
> costs...
If there is such a community around those boards there must be someone willing to either invest time
or money to implement the proposed improvements. Having boards or platforms inside the tree
is much cheaper than paying AMI for a crappy closed source BIOS/UEFI. It's still not a free endeavor and
code requires maintenance from time to time such that development on the master branch can remain
simple and sensible. Not maintaining code from time to time and enforcing some features, is probably far worse
for the project.
> Some time ago I did
https://review.coreboot.org/c/coreboot/+/41431> change where tried to get a resource allocator V4 working for these
> AGESA boards, and despite a tiny size (less than 20 lines) - it almost
> worked, judging by that fam15h A88XM-E booted fine (although there
> might have been some other problems undercover). I wonder if it could
> help and will be happy to test the new changes related to this.
The proposed change requires the code to know what memory regions are used and must be reserved.
Angel already reviewed the patch it seems, so that's probably a good start.