On Wed, Dec 4, 2019 at 4:48 PM Michal Zygowski michal.zygowski@3mdeb.com wrote:
On 03.12.2019 18:29, Kyösti Mälkki wrote:
Hi
Regarding the deprecation of AGESA platforms due to ROMCC_BOOTBLOCK.
As of 3rd December there is active development, while not much testing yet, only for the following AGESA platform boards:
- asrock/imb-a180
- lenovo/g505s
- pcengines/apu1
I do not exactly understand "not much testing". While uploading patches for family14 or apu1 I always build, flash, boot Linux test whether it works...
You can read this no testing at all for fam15tn and fam16kb so far, and testing fam14 with a single board.
I believe there was a commit for apu1 where newly added bootblock.c file was not linked in, while the boot sequence to OS worked just perfect? Some super-io configuration bits are sticky and powered from Vbat /Vrtc or Vstb rails, these bootblock changes should be verified with (RTC) battery removed.
Kyösti