On 28 June 2016 at 13:11, G Gregory graeme.gregory@linaro.org wrote:
On 28 June 2016 at 12:05, Leif Lindholm leif.lindholm@linaro.org wrote:
So, the fix looks good, but clearly this is one of those lock-step updates...
It does not however seem like the required acpica-tools update breaks any of the existing public builds, so I guess it's just time for another bump.
Acpica-tools 20160527 is now the one to use.
I'm testing with this commit right now:
https://github.com/acpica/acpica/commit/d0126a368a1f712d1d4bf723cd9be663aba8...
A quick busybox build on FVP and Juno seems to confirm that it's fine with the existing code I use.
Thanks, pushed!
Yes, this is why I think I made a mistake choosing .asl. These lock-step upgrades are a pain and avoided using the aslc macros.
Graeme
On 22 June 2016 at 16:25, Graeme Gregory graeme.gregory@linaro.org 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
2.8.1
Linaro-uefi mailing list Linaro-uefi@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-uefi