From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vagrant Cascadian Date: Wed, 12 Apr 2017 16:59:51 -0700 Subject: [U-Boot] [PATCH] Set ramdisk_addr_r to a higher address location on meson-gxbb. In-Reply-To: <31b2db97-0262-8f6e-562f-1b4ae55e96d3@suse.de> References: <20170412212805.4626-1-vagrant@debian.org> <31b2db97-0262-8f6e-562f-1b4ae55e96d3@suse.de> Message-ID: <87a87lmb2g.fsf@aikidev.net> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: u-boot@lists.denx.de On 2017-04-12, Andreas F=C3=A4rber wrote: > 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. ... >> 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=3D0x1f000000\0" \ >> "kernel_addr_r=3D0x01080000\0" \ >> "pxefile_addr_r=3D0x01080000\0" \ >> - "ramdisk_addr_r=3D0x10000000\0" \ >> + "ramdisk_addr_r=3D0x20000000\0" \ > > So that's at 512 MiB. Have you checked for any S905 devices (e.g., TV > boxes) with little RAM? I didn't. I just picked a value out of the air and tried it. :) I just now tested with 0x12000000 and it worked, where 0x10000000 consistantly failed. Debian ships a largely modular multiplatform kernel, so should be on the small side, and the current value (0x10000000) conflicted. Not sure how much of a buffer 0x12000000 gives for the kernel to grow, but that's considerably less than 0x20000000 (at 512MiB), and still works for me so far... live well, vagrant -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 832 bytes Desc: not available URL: