All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Maximum size of u-boot.imx for TBS2910 board
Date: Thu, 21 Nov 2019 22:59:29 +0100	[thread overview]
Message-ID: <5e69c39f-a36a-bcd3-8020-e752ded84166@gmx.de> (raw)
In-Reply-To: <20191121201253.GN971@bill-the-cat>

On 11/21/19 9:12 PM, Tom Rini wrote:
> On Thu, Nov 21, 2019 at 09:09:29PM +0100, Heinrich Schuchardt wrote:
>> Hello Soeren,
>>
>> when trying to add support for function key support in the USB keyboard
>> driver u-boot.imx for the TBS2910 surpassed the maximum size for u-boot.imx.
>> https://travis-ci.org/marex/u-boot-usb/builds/614059004
>>
>> Do you remember why on the TBS2910 board this size is limited to
>> 0x5fc00? Other i.MX6 boards like the Wandboard allow a much larger
>> u-boot.imx.
>>
>> The limit is defined here:
>> include/configs/tbs2910.h:80:
>> #define CONFIG_BOARD_SIZE_LIMIT 392192 /* (CONFIG_ENV_OFFSET - 1024) */
>>
>> Could the value CONFIG_ENV_OFFSET=0x60000 be enlarged?
>>
>> Many i.MX6 defconfigs use CONFIG_ENV_OFFSET=0xC0000.
>
> The nature of these boards (aimed at end users) means that we just do
> not want to / cannot really move the stored environment.  Thanks!
>

Another possibility would be to reduce the image size by using
CONFIG_REGEX=n which should be fine for a board with only one supported
network interface.

Best regards

Heinrich

  reply	other threads:[~2019-11-21 21:59 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-21 20:09 [U-Boot] Maximum size of u-boot.imx for TBS2910 board Heinrich Schuchardt
2019-11-21 20:12 ` Tom Rini
2019-11-21 21:59   ` Heinrich Schuchardt [this message]
2019-11-21 22:01     ` Marek Vasut
2019-11-21 22:45       ` Tom Rini
2019-11-22  0:23         ` Marek Vasut
2019-11-22  0:32           ` Tom Rini
2019-11-22  1:27             ` Marek Vasut
2019-11-22  1:30               ` Tom Rini
2019-11-22  1:38                 ` Marek Vasut
2019-11-22  2:53                   ` Tom Rini
2019-11-22  2:56                     ` Marek Vasut
2019-11-22  3:41                       ` Tom Rini
2019-11-22  3:58                         ` Marek Vasut
2019-11-22 10:29                           ` Soeren Moch
2019-11-22 11:42                             ` Heinrich Schuchardt
2019-11-22 12:30                               ` Tom Rini
2019-11-22 12:18                             ` Marek Vasut
2019-12-06 11:41                             ` Stefano Babic
2019-12-06 12:30                               ` Anatolij Gustschin
2019-12-06 14:02                                 ` Tom Rini
2019-12-06 16:18                                   ` Soeren Moch
2019-12-06 16:43                                     ` Soeren Moch
2019-11-22 15:44                           ` Tom Rini
2019-11-22 18:31                             ` Marek Vasut

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5e69c39f-a36a-bcd3-8020-e752ded84166@gmx.de \
    --to=xypron.glpk@gmx.de \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.