From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexander Kurtz Date: Fri, 23 Feb 2018 15:39:28 +0100 Subject: [U-Boot] Support of kernels > 16 MiB on Raspberry Pi In-Reply-To: References: <1519329516.23822.16.camel@kurtz.be> Message-ID: <1519396768.31099.14.camel@kurtz.be> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi! Thanks for confirming this! I see four ways how this can be solved: 1. I can locally adjust the memory locations to make my > 16MiB kernel work. The commit mentioned by Jaehoon Chung does this via a custom boot.scr, I did this by bumping $scriptaddr and $ramdisk_addr_r interactively during bootup and storing the changes to the Micro SD card with the "saveenv" command. 2. I could place a "uEnv.txt on the Micro SD card with those bumped values in it. This would make this work-around deployable via Puppet, but unfortunately reading "uEnv.txt" on bootup seems to be a board-specific feature, and the RPI code currently doesn't seem to have this feature. [0] 3. I could ask Debian to patch the upstream default values for these memory locations. After all, a distro bootloader which doesn't boot the distro kernel is pretty useless, so I imagine they would probably consider this. 4. U-Boot upstream could adjust the memory locations themselves. I would be happy to submit a patch for this, however I want get some feedback first: Would you guys accept such a patch, bumping the supported kernel size to e.g. 32 MiB or even 64 MiB? I would prefer 4>3>2>1, what do you think? Best regards Alexander Kurtz [0] https://github.com/u-boot/u-boot/blob/master/include/configs/rpi.h#L129 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part URL: