All of lore.kernel.org
 help / color / mirror / Atom feed
From: Giuseppe CONDORELLI <giuseppe.condorelli@st.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] zlib: updated to v.1.2.3
Date: Mon, 27 Jul 2009 16:24:13 +0200	[thread overview]
Message-ID: <05a201ca0ec5$eab6dfc0$c08182a4@st.com> (raw)
In-Reply-To: <20090724122716.B1A50832E416@gemini.denx.de>

Hi All,

unfortunately currently I'm not able to reproduce this issue because boards
I'm using are not ported
to the best so far u-boot tree.
However:
- I worked with zlib-1.2.3 patch on my current u-boot version (1.3.1)
without problem with sh boards.
- This u-boot version is a little bit different about decompression, e.g.
here we have gunzip inside cmd_bootm and in the bsf it is
  in a different file (gunzip.c)
- Given this, I backported these into 1.3.1 and tested again, with success.
I mean, I tested an old u-boot version
  with newest decompression code. I think it should be a good test, the one
I modified is common code and should be self contained.

I'm wondering if something is going wrong only with PPC arch (errors are
related to this arch), and in this case I cannot
reproduce the issue at all.
Please, is there somebody that can test this patch on a differen arch than
PPC?

What's your thinking about?

Best regards and, please, let me know.
Giuseppe Condorelli

-----Original Message-----
From: Wolfgang Denk [mailto:wd at denx.de] 
Sent: Friday, July 24, 2009 2:27 PM
To: Stefan Roese
Cc: u-boot at lists.denx.de; rhabarber1848 at web.de; Giuseppe CONDORELLI
Subject: Re: [U-Boot] [PATCH v3] zlib: updated to v.1.2.3

Dear Stefan Roese,

In message <200907241356.06963.sr@denx.de> you wrote:
>
> >    Uncompressing Kernel Image ... Error: inflate() returned -2
> > GUNZIP: uncompress, out-of-mem or overwrite error - must RESET board to
> > recover
> >
> > Maybe the zlib update is responsible?
> 
> Yes, I'm just noticing the same behaviour:
...
> I checked and verified that commit
b201171f2b4d509f3ad510b214bee70ff902e3d6 
> [zlib: updated to v.1.2.3] is responsible for this.
> 
> So we should probably revert this patch for now. Wolfgang, what do you
think?

I reverted the patch.

Giuseppe, please resubmit, but unly after *thorough* testing, please.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Harrisberger's Fourth Law of the Lab:
	Experience is directly proportional to the
	amount of equipment ruined.

  reply	other threads:[~2009-07-27 14:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-23  8:54 [U-Boot] [PATCH v3] zlib: updated to v.1.2.3 Giuseppe CONDORELLI
2009-07-23 17:16 ` Wolfgang Denk
2009-07-24  7:25   ` rhabarber1848
2009-07-24 11:56     ` Stefan Roese
2009-07-24 12:27       ` Wolfgang Denk
2009-07-27 14:24         ` Giuseppe CONDORELLI [this message]
2009-07-24 16:49     ` Kim Phillips
     [not found] <05a201ca0ec5@st.com>
2009-07-27 15:09 ` Alessandro Rubini
2009-07-27 15:30   ` Stefan Roese

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='05a201ca0ec5$eab6dfc0$c08182a4@st.com' \
    --to=giuseppe.condorelli@st.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 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.