From: 张忠山 <zzs213@126.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox <barebox@lists.infradead.org>
Subject: Re: Howto known uncompressed length when uncompress_fd_to_buf
Date: Tue, 4 Dec 2012 09:42:42 +0800 [thread overview]
Message-ID: <20121204014242.GB20812@greatfirst.com> (raw)
In-Reply-To: <20121203095534.GL10369@pengutronix.de>
In message <20121203095534.GL10369@pengutronix.de> Sascha Hauer wrote:
> On Fri, Nov 30, 2012 at 07:03:36PM +0800, 张忠山 wrote:
> > the function uncompress_fd_to_buf has no parameter to return
> > the uncompressed length, How to get the uncompressed content
> > length?
>
> AFAIK the uncompressed size is not contained in the compressed data
> You would have to uncompress to a file and use this afterwards.
> If I understand correctly you want to load a FPGA firmware which you
> have in compressed form. What I would do is:
>
> - uncompress the firmware in a script rather than uncompress it from
> C code.
> - write a command to flash the firmware.
>
But if uncompress it to a device file, like /dev/tmpmem. the file size
is the device size, not the uncompressed size.
So now I uncompressed it to a file in C code using uncompress_fd_to_fd,
then use lseek to get the current position of target file. That is the
uncompressed size.
--
Best Regards,
zzs
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-12-04 1:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-30 11:03 Howto known uncompressed length when uncompress_fd_to_buf 张忠山
2012-12-03 9:55 ` Sascha Hauer
2012-12-04 1:42 ` 张忠山 [this message]
2012-12-04 7:44 ` Sascha Hauer
2012-12-04 8:09 ` 张忠山
2012-12-04 23:13 ` Sascha Hauer
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=20121204014242.GB20812@greatfirst.com \
--to=zzs213@126.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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.