blobs/pi/amd
Michał Żygowski 797e7fc6d7 00730F01/binaryPI: fix firmware table lookup
The bug was discussed in CB:31074, referred to as "off-by-one" error.
AGESA looks for ROM signature of the firmware table at 5 offsets
instead of all 6 possible offsets. As a result placing the AMD firmware
with amdfwtool at offset FFFA0000 will lead to the incorrect xHCI
controller initialization by not loading the xHCI firmware from the
firmware table.

Increase the loop iterations to 6 in order to allow offset FFFA0000 to
be checked for ROM signature presence. The goal is to save even more
space in the SPI flash by putting the AMD firmware at the highest possible
address. The bug was present in both AGESA 1.0.0.A and 1.0.0.4 used by
PC Engines apu2 platforms.

TEST=Set the AMD FW offset to FFFA0000, build apu2 firmware and check
whether xHCI controller appears in lspci on Linux and USB 3.0 devices get
enumerated properly.

Signed-off-by: Michał Żygowski <michal.zygowski@3mdeb.com>
Change-Id: I7d81998b34c24d8294c81631224d92133bb67f24
2023-06-10 03:59:43 +00:00
..
00630F01/FP3 pi/amd: Fix AGESA.bin license files 2016-12-14 10:10:32 -07:00
00660F01/FP4 pi/amd/00660F01/FP4/AGESA.bin: Remove execute file mode bit 2020-10-17 14:38:22 +02:00
00670F00 3rdparty/blobs/pi/amd/00670F00/FT4: Release AGESA.bin 2018-03-13 09:53:49 -07:00
00730F01/FT3b 00730F01/binaryPI: fix firmware table lookup 2023-06-10 03:59:43 +00:00