Found out the problem. Not all reserved/mmio/ram resources were reported
and because of that the allocated resources landed in the WB memory.
Feel free to test/review. I will adapt it to agesa/family14 now.
--
Michał Żygowski
Firmware Engineer
https://3mdeb.com | @3mdeb_com
On 4/28/21 2:47 PM, Kyösti Mälkki wrote:
> On Wed, Apr 28, 2021 at 3:17 PM Michal Zygowski
>
michal.zygowski@3mdeb.com wrote:
>> Hi Kyösti,
>>
>> On 28.04.2021 12:33, Kyösti Mälkki wrote:
>>> Hi
>>>
>>> According to Documentation/releases/coreboot-4.14-relnotes.md we are
>>> expecting following chipset deprecations due to RESOURCE_ALLOCATOR_V3:
>>>
>>> * northbridge/amd/pi/00630F01
>>> * northbridge/amd/pi/00730F01
>>> * northbridge/amd/pi/00660F01 (already removed)
>>> * northbridge/amd/agesa/family14
>>> * northbridge/amd/agesa/family15tn
>>> * northbridge/amd/agesa/family16kb
>>>
>>> Any progress or any interest to get these fixed?
>> Working on northbridge/amd/pi/00630F01 and
>> northbridge/amd/agesa/family14 in particular right now. Hope to upload
>> the patches soon. Struggling with the SeaBIOS right now which doesn't
>> seem to see any content behind BARs of peripheral controllers and PCIe
>> devices after switching to allocator v4. Any hints?
>>
> Not really. The deprecation was announced May 2020 but I have not
> witnessed any real progress in form of code merges in upstream at
> least. And the conversion was advertised as easier than dropping
> ROMCC. So I mostly came to check if someone had earmarked donations on
> the topic, and if things were stuck with the bureaucracy.
>
> I still have following to test and develop with:
> * lippert/frontrunner-af, gizmosphere/gizmo, pcengines/apu1
> * lenovo/g505s, ibase/mi959f (not published)
> * amd/olivehill, asrock/imb-a180
> * pcengines/apu{2,3}
>
> Kyösti
> _______________________________________________
> coreboot mailing list -- coreboot@coreboot.org
> To unsubscribe send an email to coreboot-leave@coreboot.org