Am 12.04.2017 um 23:28 schrieb Vagrant Cascadian:
> Set ramdisk_addr_r to 0x20000000, otherwise it may conflict with
> kernel_addr_r location (0x01080000) with a moderately large kernel.
> 
> Signed-off-by: Vagrant Cascadian <vagr...@debian.org>
> ---
> 
>  include/configs/meson-gxbb-common.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/include/configs/meson-gxbb-common.h 
> b/include/configs/meson-gxbb-common.h
> index cc2b5b61d4..32602cb7c2 100644
> --- a/include/configs/meson-gxbb-common.h
> +++ b/include/configs/meson-gxbb-common.h
> @@ -48,7 +48,7 @@
>       "scriptaddr=0x1f000000\0" \
>       "kernel_addr_r=0x01080000\0" \
>       "pxefile_addr_r=0x01080000\0" \
> -     "ramdisk_addr_r=0x10000000\0" \
> +     "ramdisk_addr_r=0x20000000\0" \

So that's at 512 MiB. Have you checked for any S905 devices (e.g., TV
boxes) with little RAM?

No objection here, I'm not using $ram_addr_r on S905 due to GRUB.

>       MESON_FDTFILE_SETTING \
>       BOOTENV
>  

Regards,
Andreas

-- 
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

Reply via email to