linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "David H. Lynch Jr." <dhlii@dlasys.net>
To: wei.li4@elf.mcgill.ca
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Uncompressing Linux failure
Date: Thu, 14 Sep 2006 21:16:49 -0400	[thread overview]
Message-ID: <4509FF01.6030903@dlasys.net> (raw)
In-Reply-To: <20060914141550.b4x2d2aqck48osk4@webmail.mcgill.ca>

    This looks like the ppc bug with new version of zlib.
But I thought it was fixed by 2.6.18-rc2.

MY recomendation would be to either move newer or older.
Alternatively back out the zlib patch.

wei.li4@elf.mcgill.ca wrote:
> Hi All,
>
> I got the following error when I ported linux 2.6.18-rc2-g73a589b5 to 
> my board(MPC875), my bootloader is working fine with linux 2.6.13, and 
> I am using same cross-tools from ELDK 4.0:
>
> loaded at:     00400000 00529124
> board data at: 00FFFEA8 00FFFF2C
> relocated to:  00404068 004040EC
> zimage at:     00404EE1 00526337
> avail ram:     0052A000 01000000
>                                                                         
>          Uncompressing Linux...inflate returned FFFFFFFE
> exit
>
> Can you advise me? thanks.
>
> Wei
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>   


-- 
Dave Lynch 					  	    DLA Systems
Software Development:  				         Embedded Linux
717.627.3770 	       dhlii@dlasys.net 	  http://www.dlasys.net
fax: 1.253.369.9244 			           Cell: 1.717.587.7774
Over 25 years' experience in platforms, languages, and technologies too numerous to list.

"Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction."
Albert Einstein

      reply	other threads:[~2006-09-15  1:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-14 18:15 Uncompressing Linux failure wei.li4
2006-09-15  1:16 ` David H. Lynch Jr. [this message]

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=4509FF01.6030903@dlasys.net \
    --to=dhlii@dlasys.net \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=wei.li4@elf.mcgill.ca \
    /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 NNTP newsgroup(s).