From: Peter Tyser <ptyser@xes-inc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/7] 86xx: Unlock l1 cache unconditionally
Date: Fri, 10 Jul 2009 18:14:49 -0500 [thread overview]
Message-ID: <1247267689.32367.169.camel@localhost.localdomain> (raw)
In-Reply-To: <20090710230751.C39B7832E416@gemini.denx.de>
On Sat, 2009-07-11 at 01:07 +0200, Wolfgang Denk wrote:
> Dear Peter Tyser,
>
> In message <1247259105.32367.22.camel@localhost.localdomain> you wrote:
> >
> > The only platforms the define unlock_ram_in_cache() are 83xx, 85xx,
> > 86xx, and 74xx_7xx.
> >
> > It looks like the most of them had "issues" in their implementation that
> > could explain why there weren't enabled:
> > 83xx - ade50c7fa1b16ef98be17e9c3ae286aecf4f5605,
> > 6eb2a44e27919fdc601e0c05404b298a7602c0e3
> >
> > 86xx - 392438406041415fe64ab8748ec5ab5ad01d1cf7
> >
> > 74xx - d685b74c64a38849f1a129b3ab846fbf67dd937e
> >
> > 85xx - this one works
> >
> > My best guess was all the non-85xx implementations had bugs or other
> > issues that caused U-Boot to become unstable after unlocking the cache.
> > Perhaps those bugs are fixed now, but I only have 86xx hardware to test
> > on. I've been running a few 86xx boards with the cache unlocked with no
> > noticeable problems.
>
> Thanks for the analysis. So let's go ahead and do this globally.
I'll submit a patch. Hopefully someone with an 83xx and 74xx/7xx board
can give it a shot before you apply it.
Best,
Peter
next prev parent reply other threads:[~2009-07-10 23:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-22 15:26 [U-Boot] [PATCH 0/7] Initial support for the XPedite5170 Peter Tyser
2009-05-22 15:26 ` [U-Boot] [PATCH 1/7] 85xx: Add PORBMSR and PORDEVSR shift defines Peter Tyser
2009-06-12 22:21 ` Kumar Gala
2009-05-22 15:26 ` [U-Boot] [PATCH 2/7] tsec: Add support for BCM5482S PHY Peter Tyser
2009-06-12 14:46 ` Kumar Gala
2009-06-12 16:17 ` Ben Warren
2009-05-22 15:26 ` [U-Boot] [PATCH 3/7] 86xx: Unlock l1 cache unconditionally Peter Tyser
2009-06-12 14:48 ` Kumar Gala
2009-07-10 20:37 ` Wolfgang Denk
2009-07-10 20:51 ` Peter Tyser
2009-07-10 23:07 ` Wolfgang Denk
2009-07-10 23:14 ` Peter Tyser [this message]
2009-05-22 15:26 ` [U-Boot] [PATCH 4/7] xes: Update Freescale PCI code to work with 86xx processors Peter Tyser
2009-06-12 22:24 ` Kumar Gala
2009-05-22 15:26 ` [U-Boot] [PATCH 5/7] xes: Update Freescale DDR " Peter Tyser
2009-06-12 22:24 ` Kumar Gala
2009-05-22 15:26 ` [U-Boot] [PATCH 6/7] xes: Update Freescale clock " Peter Tyser
2009-06-12 22:24 ` Kumar Gala
2009-05-22 15:26 ` [U-Boot] [PATCH 7/7] XPedite5170 board support Peter Tyser
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=1247267689.32367.169.camel@localhost.localdomain \
--to=ptyser@xes-inc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox