From: Larry Johnson <lrj@arlinx.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Problem with cache diag on sequoia board in PPC4xx branch for-1.3.2
Date: Sat, 22 Dec 2007 14:38:18 -0500 [thread overview]
Message-ID: <476D67AA.50000@arlinx.com> (raw)
In-Reply-To: <200712221223.18347.sr@denx.de>
Stefan Roese wrote:
> On Saturday 22 December 2007, Stefan Roese wrote:
>>> In testing my merge of Korat PPC440EPx board support into PPC4xx branch
>>> "for-1.3.2", I found problem with the "DIAG RUN CACHE" command. The
>>> same problem occurs in the latest for-1.3.2 code for sequoia. Here is a
>>> copy of the console output showing what happens:
>> Thanks for reporting. I'll try to take a look at it in the next days. But I
>> have no problems at all, if you provide a patch to fix it. ;)
>
> OK, I found the problem and fixed in the for-1.3.2 branch:
>
> commit 8092791c5d959e89f9bc4ed0ff880c3509da743f
> Author: Stefan Roese <sr@denx.de>
> Date: Sat Dec 22 12:18:26 2007 +0100
>
> ppc4xx: Fix problem in 44x cache POST routine
>
> As repoted by Larry Johnson, running "diag run cache" caused a crash
> in U-Boot. This problem was introduced by a patch that removed the
> TLB entry for the cache test after the test has completed. Since this
> TLB was only setup once, a 2nd attempt to run this cache test
> failed with a crash. Now this TLB entry is created every time the
> routine is called.
>
> Signed-off-by: Stefan Roese <sr@denx.de>
>
> [snip]
This fixes the problem on Korat as well. Thanks!
Best regards,
Larry
prev parent reply other threads:[~2007-12-22 19:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-20 22:31 [U-Boot-Users] Problem with cache diag on sequoia board in PPC4xx branch for-1.3.2 Larry Johnson
2007-12-22 7:56 ` Stefan Roese
2007-12-22 11:23 ` Stefan Roese
2007-12-22 19:38 ` Larry Johnson [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=476D67AA.50000@arlinx.com \
--to=lrj@arlinx.com \
--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.