From: "André Schwarz" <andre.schwarz@matrix-vision.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [MPC83xx] broken patch "do not fixup NULL ptrs" ?
Date: Fri, 22 Oct 2010 21:25:34 +0200 [thread overview]
Message-ID: <1287775534.2169.3.camel@swa-e6500> (raw)
In-Reply-To: <OFD619D753.E5A8A659-ONC12577C4.00518D0B-C12577C4.005207ED@transmode.se>
On Fri, 2010-10-22 at 16:56 +0200, Joakim Tjernlund wrote:
> Andr? Schwarz <andre.schwarz@matrix-vision.de> wrote on 2010/10/22
> 16:30:49:
> >
> > Joakim,
> >
> >
> > your commit d1e0b10accdbac2e0a8b2cbf7c589645442f87c5 renders my MPC8377
> > based board unbootable.
> >
> >
> > Two weeks ago I got this after power on :
> >
> >
> > U-Boot 2010.09-00486-gfda6278-dirty (Oct 22 2010 - 16:19:20) MPC83XX
> >
> > Reset Status:
> >
> > CPU: e300c4, MPC8377, Rev: 2.1 at 533.333 MHz, CSB: 266.667 MHz
> > Board: Matrix Vision MergerBox
> > ....
> >
> >
> >
> > After rebasing my work to current master completely silences the serial
> > line and the CPU doesn't come up. Bisection leads to your patch.
> >
> > reverting it makes the board work again.
> >
> > Any ideas ?
>
> Yes, the problem is else where. This code runs after relocation to RAM.
> I had a similar problem and the reason was the patch:
> "powerpc: Remove warm reset entry point"
hmm, ok.
But what's the root cause ?
>
> Try sticking 4 nop's right after _start:
> in start.S
>
... and why should this work ?
Has this something to do with trial and error ?
Can you shed some light on this ?
Regards,
Andr?
MATRIX VISION GmbH, Talstrasse 16, DE-71570 Oppenweiler
Registergericht: Amtsgericht Stuttgart, HRB 271090
Geschaeftsfuehrer: Gerhard Thullner, Werner Armingeon, Uwe Furtner
next prev parent reply other threads:[~2010-10-22 19:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 14:30 [U-Boot] [MPC83xx] broken patch "do not fixup NULL ptrs" ? André Schwarz
2010-10-22 14:56 ` Joakim Tjernlund
2010-10-22 19:25 ` André Schwarz [this message]
2010-10-23 9:17 ` Joakim Tjernlund
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=1287775534.2169.3.camel@swa-e6500 \
--to=andre.schwarz@matrix-vision.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox