From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vagrant Cascadian Date: Tue, 08 May 2018 13:22:35 -0700 Subject: [U-Boot] Bug#897671: u-boot does not work on sheevaplug In-Reply-To: <20180506001349.GY12235@bill-the-cat.ec.rr.com> References: <73c25c9a-faba-a7ea-4d3d-7e1fe932eda6@web.de> <352dbeca-a872-de5f-60bf-d7a409cbecb8@web.de> <20180505091354.abo3khggep6sa7jm@jirafa.cyrius.com> <8afc29d1-8ae3-18e3-8bb9-22d13814efe4@web.de> <84c2c623-5d6d-e6fa-bc2b-b4082dca5dc2@web.de> <20180505183529.auxstq2qilg43ttm@jirafa.cyrius.com> <57d24e3c-aff7-ab81-c08a-a1362bc42ce2@web.de> <152540843251.13599.4428160353240912722.reportbug@server2.notar-krebs.de> <3ef09240-8cbe-3ad1-e070-9c4afd4cb1c0@web.de> <87a7tdpuvr.fsf@aikidev.net> <152540843251.13599.4428160353240912722.reportbug@server2.notar-krebs.de> <20180506001349.GY12235@bill-the-cat.ec.rr.com> Message-ID: <87h8nhoq2c.fsf@aikidev.net> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 2018-05-05, Tom Rini wrote: > On Sat, May 05, 2018 at 04:04:08PM -0700, Vagrant Cascadian wrote: >> Markus Krebs discovered that the sheevaplug target has again grown and >> installation overlaps where the u-boot env is saved since u-boot >> ~2017.09. Running saveenv overwrites u-boot, and installing u-boot >> overwrites any prior environment settings. >> >> More detail on the bug report in Debian: >> >> https://bugs.debian.org/897671 >> >> We don't carry any patches for the sheevaplug u-boot target in Debian, >> so this is likely also an issue upstream. Who are the current >> maintainers for sheevaplug in u-boot upstream? >> >> A brief summary of the current findings: >> >> On 2018-05-05, Markus Krebs wrote: >> > Am 05.05.2018 um 20:36 schrieb Markus Krebs: ... >> > but the environment shouldn't start at 0x80000 when u-boot.kwb > 524 KB; >> > in this case 'saveenv' overwrites u-boot (?). >> > Changing 0x80000 to 0xa0000 helps ; I compiled a u-boot.kwb from the >> > so-modified sources, and now I can start Debian fine. >> >> It looks like it was bumped from 0x60000 to 0x80000 in 2014: >> >> http://git.denx.de/?p=u-boot.git;a=commit;h=4dfb0e4d3e75763d6fbe8788316bea9ba23e8e01 >> >> If 0x80000 isn't enough, there might be some features in the config to >> experiment with removing, or it may need to be bumped again. > > I've added the maintainer to the list as well. I would suggest looking > for things to trim out, perhaps CMD_MEMTEST ? Thanks for the suggestsions. CMD_MEMTEST wasn't present, but disabling EFI_LOADER made u-boot 2018.05 go from 592k down to 548k. There's not a *lot* left to disable in the config, but that's a significant start... On a related note, I'm wondering if EFI_LOADER should only be enabled with SYS_ARM_ARCH >= 7 by default, as many of the earlier arm systems tend to be space-constrained, and those that aren't could enable it on a case-by-case basis. > Also, a patch to make it a link error when we exceed the size allowed > would be great, so that in the future we catch this when it happens. > Thanks! Will look into it, although would be happy if someone beats me to it. :) 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: