From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 2/2] RISCV: image: Parse Image.gz support in booti.
Date: Tue, 30 Apr 2019 11:52:20 +0200 [thread overview]
Message-ID: <be7e886c-1760-1dba-7241-b06a69075c2e@gmail.com> (raw)
In-Reply-To: <6a65fac9-fafd-35d9-ef0b-d5e62514cec0@wdc.com>
On 4/30/19 3:27 AM, Atish Patra wrote:
[...]
>>> Yes. FIT image parsing can be done in that way. However, the idea was
>>> here to load Image.gz directly. Image.gz is default compressed Linux
>>> kernel image format in RISC-V.
>>
>> Sigh, and the image header is compressed as well, so there's no way to
>> identify the image format, right ? And there's no decompressor, so the
>> dcompressing has to be done by bootloader, which would need some sort of
>> very smart way of figuring out which exact compression method is used ?
>>
> Yes. Image.gz is always gunzip. So checking first two bytes is enough to
> confirm that it is a gz file.
What happens once people start feeding it more exotic compression
methods, like LZ4 or LZO or LZMA for example ?
> The tricky part is length of the compressed file. I took another look at
> the gunzip implementation in U-Boot. It looks like to me that compressed
> header length just to parse the header correctly. It doesn't actually
> use the "length" to decompress. In fact, it updates the length with
> uncompressed bytes after the decompression.
That's possible.
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2019-04-30 9:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-25 19:56 [U-Boot] [PATCH v2 1/2] RISCV: image: Add booti support Atish Patra
2019-04-25 19:56 ` [U-Boot] [PATCH v2 2/2] RISCV: image: Parse Image.gz support in booti Atish Patra
2019-04-26 1:43 ` Marek Vasut
2019-04-26 17:08 ` Atish Patra
2019-04-26 18:04 ` Marek Vasut
2019-04-30 1:27 ` Atish Patra
2019-04-30 9:52 ` Marek Vasut [this message]
2019-04-30 18:13 ` Atish Patra
2019-04-30 19:11 ` Marek Vasut
2019-04-30 20:38 ` Atish Patra
2019-04-30 21:42 ` Marek Vasut
2019-04-30 22:06 ` Atish Patra
2019-05-01 10:34 ` Marek Vasut
2019-05-01 18:22 ` Atish Patra
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=be7e886c-1760-1dba-7241-b06a69075c2e@gmail.com \
--to=marek.vasut@gmail.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