LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Sette Agostino <Agostino.Sette@siemens.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: PPCBoot 2.0.0 Errors
Date: Tue, 08 Nov 2005 10:08:57 +0100	[thread overview]
Message-ID: <20051108090857.BCE8135265B@atlas.denx.de> (raw)
In-Reply-To: Your message of "Tue, 08 Nov 2005 09:37:07 +0100." <69DF49BE936F4441980EC1D59F0ADC2F0108C267@aqlby02a.siemens.it>

In message <69DF49BE936F4441980EC1D59F0ADC2F0108C267@aqlby02a.siemens.it> you wrote:
> 
> I agree with you concerning the PPCBoot. In fact in other boards we are using U-Boot.
> We tried to use U-Boot for MPC859 but we had some problems we are trying to
> solve.

You cannot solve  these  problems  by  downgrading  to  PPCBoot.  The
852/859/866  processors  are  definitelu *not* supported by PPCBoot -
the required changes of the clock handling were added much later. You
*must* use U-Boot.

> As far as you know to change the boot or the kernel on cards in field is not
> so easy :-(

You mean you shipped boards to customers in  the  field  in  a  state
where you did not even decide for a final version of the boot loader?
Gosh...

> We found an unexpected beahviour regarding the Linux time tick. 

...whichis probablky cause by using PPCBoot which does not understand
to deal with a 859.

> Another interesting point is that the same kernel works well on other TQM8xx
> modules, but not fot TQM859.

U-Boot is running perfectly fine on the TQM859 - we have these boards
here in our virtual lab; they are tested on a regular base.

> I will try to introduce the U-Boot, but I am not confident it will solve the
> problem, what do you think about it?

I can *guarantee* you that PPCBoot is definitely worse on your hardware.

> Last question, which is the appropriate mailing list?

u-boot-users

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Always leave room to add an explanation if it doesn't work out.

  reply	other threads:[~2005-11-08  9:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-08  8:37 PPCBoot 2.0.0 Errors Sette Agostino
2005-11-08  9:08 ` Wolfgang Denk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-11-14 11:26 Sette Agostino
2005-11-14 11:36 ` Wolfgang Denk
2005-11-08 13:52 Sette Agostino
2005-11-08  9:18 Sette Agostino
2005-11-08 13:38 ` Wolfgang Denk
2005-11-07 14:34 Sette Agostino
2005-11-07 22:09 ` Wolfgang Denk

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=20051108090857.BCE8135265B@atlas.denx.de \
    --to=wd@denx.de \
    --cc=Agostino.Sette@siemens.com \
    --cc=linuxppc-embedded@ozlabs.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