From: "Mats Kärrman" <Mats.Karrman@tritech.se>
To: u-boot@lists.denx.de
Subject: [U-Boot] mpc512x: Trouble migrating from 2012.07 to 2013.01
Date: Wed, 23 Jan 2013 21:58:56 +0000 [thread overview]
Message-ID: <ED3E0BCACD909541BA94A34C4A164D4C427B4CA1@post.tritech.se> (raw)
In-Reply-To: <20130123212559.309ED2454A1@gemini.denx.de>
Dear Wolfgang Denk,
>> Found that it was looping endlessly in arch/powerpc/lib/ticks.S::wait_ticks(). Reverting commit "ppc: Create a stack frame for wait_ticks()" made everything work again.
>
> This makes no sense to me - especially as it works on all other
> systems.
If you say it works, it makes no sense to me either. I thought it might be some subtle difference in the way the e300c4 core or GCC works compared to other PPC cores. If there are no such differences, then a patch with no intended functional difference beyond keeping gdb happy should not make any difference, good or bad.
> Well, you mentioned you were using a MPC5125 processor which is not
> supported in mainline U-Boot, and which is known to have enough
> differences in it's register layout that anything might be the cause
> for such issues.
>
> Is it correct to assume that you have a _lot_ of local modifiucations
> in your tree? I bet the problem lies there...
I wouldn't say a lot. I'm using only the serial console to be able to download and flash images (using CFI flash) and to boot Linux so the primary patches are the serial driver and the DRAM initialization. On top of that there are some minimal I/O initialization and of course I went through and updated the register mappings for the relevant peripherals. It worked fine with 2009.03 and with 2012.07 but of course I might have overlooked something.
I will report back when / if I find out something more.
I'm not much for betting though ;)
Best regards,
Mats
next prev parent reply other threads:[~2013-01-23 21:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 15:24 [U-Boot] mpc512x: Trouble migrating from 2012.07 to 2013.01 Mats Kärrman
2013-01-23 21:25 ` Wolfgang Denk
2013-01-23 21:58 ` Mats Kärrman [this message]
2013-01-24 8:40 ` Joakim Tjernlund
[not found] ` <OFD3C888A1.560BEE31-ONC1257AFD.002DB246-C1257AFD.002FAD45@LocalDomain>
2013-01-24 8:58 ` Joakim Tjernlund
[not found] ` <OF5A9C9414.751DE82C-ONC1257AFD.0030970D-C1257AFD.00314F3A@LocalDomain>
2013-01-24 9:21 ` Joakim Tjernlund
2013-01-24 11:54 ` Mats Kärrman
2013-01-24 13:31 ` Mats Kärrman
2013-01-24 13:48 ` Joakim Tjernlund
-- strict thread matches above, loose matches on Subject: below --
2013-01-23 13:17 Mats Kärrman
2013-01-23 20:40 ` 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=ED3E0BCACD909541BA94A34C4A164D4C427B4CA1@post.tritech.se \
--to=mats.karrman@tritech.se \
--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.