From: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] max gunzip output buffer size in do_bootm()
Date: Tue, 24 Jan 2006 17:28:34 +0100 [thread overview]
Message-ID: <43D655B2.6070204@esd-electronics.com> (raw)
Hi,
I ran into trouble when booting huge compressed images via bootm.
do_bootm uses a fixed maximum size for the uncompressed data of 0x400000
bytes. That's not enough for our images (about uncompressed 9MB VxWorks
image).
Is there any reason for the 4MB limiting? I'd like to post a patch that
fixes this issue:
a) just increase the unc_len variable to e.g. 16MB
b) add a define with default to board config file
(CONFIG_MAX_BOOTM_UNC_LEN). When not defined in config file, 0x400000 is
used
c) set unc_len to mem size :-) So user must know what he is doing.
What do you like best?
BTW: When the uncompressed data is more than the unc_len limit no error
is reported. The uncompressed data is just truncated leading to
corrupted uncompressed data. Should that be fixed, too?
Regards
Matthias
next reply other threads:[~2006-01-24 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 16:28 Matthias Fuchs [this message]
2006-01-24 17:32 ` [U-Boot-Users] max gunzip output buffer size in do_bootm() Wolfgang Denk
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=43D655B2.6070204@esd-electronics.com \
--to=matthias.fuchs@esd-electronics.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