public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Thomas Koeller <thomas.koeller@baslerweb.com>
To: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] zlib_uncompress usage(more info)
Date: Thu, 06 May 2004 14:50:00 -0000	[thread overview]
Message-ID: <200405061652.49353.thomas.koeller@baslerweb.com> (raw)
In-Reply-To: <409A4DB8.4010404@rawbw.com>

Zlib needs _huge_ buffers in RAM. A description of how to
estimate the amount of ram required can be found in
packages/services/compress/zlib/current/include/zconf.h.

tk


John Newlin wrote:
> Most likely you need to skip around the gzip header (or strip the header
> prior to programming the image into flash)
>
> If you have the zlib code, look in gzio.c for the function check_header
> as an example
>
> -john
>
> bhanuprakash kandimalla wrote:
> >Just want to put some more info to my previous mail.
> >
> >Hello Ecos World:
> >Did any one use the zlib uncompress function. This
> >funtion has the following structure:uncompress(dest,
> >dest_len, source, source_len). Is there anylimit on
> >the souce_len to use. I have a compressed image stored
> >in boot flash and want to uncompress onto RAM. The
> >source file is of 177768 bytes. Some how when I use
> >this function, it always returns Z_MEM_ERROR. (I used
> >the Cygwin tool to create the compressed image
> >(gzip)).
> >
> >>>This Z_MEM_ERROR is returning from inflate_blocks()
> >
> >function. What does this mean...
> >
> >Can someone suggest me where I am doing wrong. I
> >appreciate any help.
> >Thanks in advance
> >
> >
> >
> >
> >__________________________________
> >Do you Yahoo!?
> >Win a $20,000 Career Makeover at Yahoo! HotJobs
> >http://hotjobs.sweepstakes.yahoo.com/careermakeover

-- 
--------------------------------------------------

Thomas Koeller, Software Development
Basler Vision Technologies

thomas dot koeller at baslerweb dot com
http://www.baslerweb.com

==============================

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2004-05-06 14:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-06  6:56 bhanuprakash kandimalla
2004-05-06 14:37 ` John Newlin
2004-05-06 14:50   ` Thomas Koeller [this message]
2004-05-06 14:56     ` Gary Thomas
2004-05-07  7:10 ` [ECOS] Unsubscri be Charlie
2004-05-07  7:18   ` William Martin

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=200405061652.49353.thomas.koeller@baslerweb.com \
    --to=thomas.koeller@baslerweb.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).