LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Porter <mporter@kernel.crashing.org>
To: Michael Richardson <mcr@sandelman.ottawa.on.ca>
Cc: "'linuxppc-embedded@ozlabs.org'" <linuxppc-embedded@ozlabs.org>
Subject: Re: problems with ppc405 on 2.6.11.8.
Date: Fri, 13 May 2005 18:44:59 -0700	[thread overview]
Message-ID: <20050513184458.B15958@cox.net> (raw)
In-Reply-To: <3086.1116027422@marajade.sandelman.ottawa.on.ca>; from mcr@sandelman.ottawa.on.ca on Fri, May 13, 2005 at 07:37:02PM -0400

On Fri, May 13, 2005 at 07:37:02PM -0400, Michael Richardson wrote:
> A customer of mine has a PPC405 system, which was based upon the
> Embedded Planet design. It runs U-boot 0.4.0, and the system currently
> ships with a kernel based upon Timesys 2.4.18. 
> 
> We are in the process of upgrading to 2.6.11. (linus, not timesys. We
> see no value add from timesys)
> 
> The major stumbling block was using boot/simple/{head,relocate}.S,
> and the inftrees.c. For reasons we do not understand, the system would
> fail in huft_build() when (setting up for) decompressing.  We traced
> through this using our bdi2000, after failing with puts() additions. 

If you are booting off of U-boot, why are you trying to boot a
zImage?  You should be booting a uImage which doesn't use the
bootwrapper glue code in arch/ppc/boot/. Load the right image 
and you will avoid all of this.

-Matt

  reply	other threads:[~2005-05-14  1:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-13 23:37 problems with ppc405 on 2.6.11.8 Michael Richardson
2005-05-14  1:44 ` Matt Porter [this message]
2005-05-14  2:59 ` Roger Larsson

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=20050513184458.B15958@cox.net \
    --to=mporter@kernel.crashing.org \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=mcr@sandelman.ottawa.on.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