Patrick Georgi via coreboot:
On 25.11.21 17:04, Mike Banon <mikeb...@gmail.com> wrote:
2. It's not just the loss of boards - it's also the loss of coreboot
users/contributors who only have these boards and don't want to switch
These users didn't contribute fixes to their boards (or even just
feedback that things needs to be done and testing when others provide
patches) - are they even contributors?
It's easy to argue in favor of "lots of users" (or contributors if you
want), but if they're all but invisible, do they even exist?
I contributed a number of changes to address Coverity warnings in the
AMD families, and am actively using a corebooted G505s and PC Engines
APU. I lurk in the mailing list most of the time, and have a hard time
tracking what needs to be done to keep boards alive. On this thread, for
example, the updated requirements feel like they are (but are likely
not) coming out of the blue.
To address the OP, it seems like there is some activity on getting an
AGESA RESOURCE_ALLOCATOR_V4 working, but is an AGESA PARALLEL_MP init
also needed (and is there any activity or something I can do to help?)
Realize resources may not exist to spoon feed problem definitions to a
level my brain can handle.
The rest of the reply might be due to communication losses of non-face
to face transmission medium.
_______________________________________________
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org
