public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Oleksandr Suvorov <oleksandr.suvorov@foundries.io>, u-boot@lists.denx.de
Cc: Peng Fan <peng.fan@nxp.com>, Fabio Estevam <festevam@gmail.com>,
	Oliver Graute <oliver.graute@kococonnector.com>
Subject: Re: [PATCH 3/3] imx8qm_mek: Increase CONFIG_SYS_BOOTM_LEN to 64MB
Date: Sun, 29 Aug 2021 21:55:16 +0200	[thread overview]
Message-ID: <deae62d0-5f9a-34bd-6308-144fc3cd565a@denx.de> (raw)
In-Reply-To: <20210829193913.124217-3-oleksandr.suvorov@foundries.io>

On 8/29/21 9:39 PM, Oleksandr Suvorov wrote:
> The BSP platform LmP supports the board NXP iMX8QM MEK. The
> kernel size in LmP exceeds 32Mb. Increase the maximum size
> of an uncompressed kernel to fix the following error:
>      Uncompressing Kernel Image
>      Error: inflate() returned -5
>      Image too large: increase CONFIG_SYS_BOOTM_LEN
>      Must RESET board to recover
> 

Maybe we should increase the default for arm64 instead ? 8 MiB is too small.

  reply	other threads:[~2021-08-29 19:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-29 19:39 [PATCH 1/3] imx8mm_evk: Increase CONFIG_SYS_BOOTM_LEN to 64MB Oleksandr Suvorov
2021-08-29 19:39 ` [PATCH 2/3] imx8mq_evk: " Oleksandr Suvorov
2021-08-29 19:39   ` [PATCH 3/3] imx8qm_mek: " Oleksandr Suvorov
2021-08-29 19:55     ` Marek Vasut [this message]
2021-08-29 20:53       ` Tom Rini
2021-08-30 11:11       ` Oleksandr Suvorov
2021-08-30 12:18         ` Marek Vasut
2021-08-30 15:05           ` Marcel Ziswiler
2021-08-30 15:10             ` Marek Vasut
2021-08-30 16:34               ` Marcel Ziswiler
2021-08-30 16:49                 ` Marek Vasut
2021-08-30 17:46             ` Tom Rini
2021-08-30 19:42               ` Marcel Ziswiler
2021-09-15  3:06         ` Peng Fan (OSS)
2021-10-07 14:13     ` sbabic
2021-10-07 14:13   ` [PATCH 2/3] imx8mq_evk: " sbabic
2021-10-07 14:13 ` [PATCH 1/3] imx8mm_evk: " sbabic

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=deae62d0-5f9a-34bd-6308-144fc3cd565a@denx.de \
    --to=marex@denx.de \
    --cc=festevam@gmail.com \
    --cc=oleksandr.suvorov@foundries.io \
    --cc=oliver.graute@kococonnector.com \
    --cc=peng.fan@nxp.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox