Hi Al,
These two patches will give some extra ACPI debug output in u-boot so you can see the start/end of the ACPI address allocation. You can also see the size and physical address of each ram bank.
Hopefully this helps you track down the issue. My DSDT changes are not big enough to cross the 0x50000000 boundary yet.
Thanks
Graeme
From: Graeme Gregory graeme.gregory@linaro.org
Enable the RAM bank debug so we can see actual physical locations of RAM bank.
Signed-off-by: Graeme Gregory graeme.gregory@linaro.org --- arch/arm/lib/board.c | 2 ++ 1 file changed, 2 insertions(+)
diff --git a/arch/arm/lib/board.c b/arch/arm/lib/board.c index d0a2690..2ada5db 100644 --- a/arch/arm/lib/board.c +++ b/arch/arm/lib/board.c @@ -64,6 +64,8 @@ #include "../drivers/net/lan91c96.h" #endif
+#define DEBUG + DECLARE_GLOBAL_DATA_PTR;
ulong monitor_flash_len;
From: Graeme Gregory graeme.gregory@linaro.org
Print the address we loaded the ACPI blob to to better help debugging issues with memory allocation.
Signed-off-by: Graeme Gregory graeme.gregory@linaro.org --- arch/arm/lib/bootm.c | 3 +++ 1 file changed, 3 insertions(+)
diff --git a/arch/arm/lib/bootm.c b/arch/arm/lib/bootm.c index 06d4014..7a8686a 100644 --- a/arch/arm/lib/bootm.c +++ b/arch/arm/lib/bootm.c @@ -463,6 +463,9 @@ static void arm_boot_get_acpi(int argc, char *argv[], bootm_headers_t *images) return; }
+ printf("* acpi: loading to %x, end %x\n", images->acpi_lmb_start, + images->acpi_lmb_start + images->acpi_len); + memmove((void *)images->acpi_lmb_start, (void *)images->acpi_start, images->acpi_len); }
On 05/22/2013 05:00 AM, Graeme Gregory wrote:
Hi Al,
These two patches will give some extra ACPI debug output in u-boot so you can see the start/end of the ACPI address allocation. You can also see the size and physical address of each ram bank.
Hopefully this helps you track down the issue. My DSDT changes are not big enough to cross the 0x50000000 boundary yet.
Aha! Thanks, Graeme. These will help quite a bit.