On 06/22/2016 10:25 AM, Graeme Gregory wrote:
MADT will now compile with v6.1 fields so we need to bump the FADT to indicate v6.1 compatability otherwise kernel will fail to parse MADT correctly and issue the error "No valid GICC entries exist".
Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Graeme Gregory graeme.gregory@linaro.org
Platforms/ARM/VExpress/AcpiTables/rtsm_ve-aemv8a/facp.asl | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Platforms/ARM/VExpress/AcpiTables/rtsm_ve-aemv8a/facp.asl b/Platforms/ARM/VExpress/AcpiTables/rtsm_ve-aemv8a/facp.asl index c288ae2..b52413f 100644 --- a/Platforms/ARM/VExpress/AcpiTables/rtsm_ve-aemv8a/facp.asl +++ b/Platforms/ARM/VExpress/AcpiTables/rtsm_ve-aemv8a/facp.asl @@ -35,7 +35,7 @@
[0004] Signature : "FACP" [0004] Table Length : 0000010C -[0001] Revision : 05 +[0001] Revision : 06 [0001] Checksum : 18 [0006] Oem ID : "LINARO" [0008] Oem Table ID : "RTSMVEV8" @@ -195,3 +195,4 @@ [0001] Encoded Access Width : 01 [Byte Access:8] [0008] Address : 0000000000000000
+[0008] Hypervisor ID : 0000000000000000
This fixes a boot failure on the foundation model with an ACPI 4.7rc4 kernel I've been testing (on a fedora root fs).
There are assorted other ugly messages including the "GICv3 system registers enabled, broken firmware!" message, but it boots!
Tested-by: Jeremy Linton jeremy.linton@arm.com
Thanks!