From: Zakir Ahmed <zakir.ahmed@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Unable to decompress files greater than 500 MB
Date: Wed, 26 Oct 2016 15:52:08 +0530 [thread overview]
Message-ID: <05d201d22f72$cf61b530$6e251f90$@samsung.com> (raw)
In-Reply-To: CGME20161026102024epcas3p2a9e2d042ccba443ea9daa8db60154fb3@epcas3p2.samsung.com
Hi,
We are using u-boot source code which has the support for most of the
compressions like bz2, lzma, gz etc.
We tried uncompressing bz2, lzma and gz images and most of them either fail
or data abort or hang indefinitely for large sized uncompressed data > 500
MB.
This is for the arm port.
Could you please provide us any pointers for the same?
signature
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 113456 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20161026/5bd501cf/attachment.png>
next parent reply other threads:[~2016-10-26 10:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20161026102024epcas3p2a9e2d042ccba443ea9daa8db60154fb3@epcas3p2.samsung.com>
2016-10-26 10:22 ` Zakir Ahmed [this message]
2016-10-27 4:16 ` [U-Boot] Unable to decompress files greater than 500 MB Heiko Schocher
2016-10-27 7:23 ` Zakir Ahmed
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='05d201d22f72$cf61b530$6e251f90$@samsung.com' \
--to=zakir.ahmed@samsung.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