On 24.04.19 16:13, Tom Rini wrote:
On Wed, Apr 24, 2019 at 03:49:35PM +0200, Stefan Roese wrote:
On 24.04.19 15:21, Tom Rini wrote:
On Sat, Apr 13, 2019 at 09:00:48AM -0400, Tom Rini wrote:
On Fri, Apr 12, 2019 at 07:08:40PM +1200, Chris Packham wrote:
On Thu, 11 Apr 2019, 10:33 PM Stefan Roese, <s...@denx.de> wrote:

We have run now multiple times into size issues with the openrd
board port. To finally fix this, this patch now moves the U-Boot size
>from 0x6.0000 to 0x8.0000, giving enough space for the next time.

This also changes the environment location and potentially the
MTD partitioning, but I see no better fix for now. Especially since
this board does not have an active maintainer.

Signed-off-by: Stefan Roese <s...@denx.de>
Cc: Chris Packham <judge.pack...@gmail.com>


One alternative option I looked at was trimming down the dtb to drop the
nodes that aren't used in u-boot. This might just get it under the 0x60000
limit ... for a while.

I agree that this is the best approach in leiu of anyone maintiaining the
board. Once this is applied the openrd boards can be reenabled in travis.

Reviewed-by: Chris Packham <judge.pack...@gmail.com>

Please note the board is currently orphaned and excluded from travis
builds due to the size problem.  So if someone is going to address this,
I want to see the board un-orphaned too (and travis updated to build it
again), thanks!

Anyone?  Thanks!

I can add myself as maintainer and add it back to the travis builds.
Even though I can only compile test because I don't have access to
this board.

OK.  Make sure to include updating the travis rules when you update the
MAINTAINERS file, thanks!

Yep. I'll send a patch for this once I've pushed this patch here to
mainline, which should happen shortly.

Thanks,
Stefan
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

Reply via email to