public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Andre Schwarz <andre.schwarz@matrix-vision.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mpc83xx: Make it boot again
Date: Fri, 05 Nov 2010 09:24:12 +0100	[thread overview]
Message-ID: <4CD3BF2C.1070705@matrix-vision.de> (raw)
In-Reply-To: <63BE59A941660E44B1E66C95E0347C3C063666F3@az33exm25.fsl.freescale.net>

On 11/04/2010 08:49 PM, Wood Scott-B07421 wrote:
>
> Timur Tabi wrote:
> > Wood Scott-B07421 wrote:
> > > To be totally safe, we probably want to do a readback plus twi (to 
> turn
> > > a data dependency into a flow dependency) before the isync.
> >
> > twi == trap word immediate?
>
> Yes.
>
> > If so, I don't see how that will turn a data dependency into a flow 
> dependency.
> > Is that some sort of side effect of twi?
>
> It decides based on the input register (data dependency) whether to 
> cause a trap (flow dependency).  We never want it to actually trap, so 
> we set a condition that says never trap, but the dependency is still 
> there -- the hardware doesn't decode it as a no-op.
>

Might there be any other location this could be used for ?

Actually my 8377 is running fine up to 533MHz core and csb up to 400MHz.
As soon as core frequency rises to 600MHz+ there'll be frequent hangs 
during flush_dcache.

core voltage is clean at 1.05V without any glitches or significant load 
steps.

Can anybody confirm that current code runs stable on MPC837x at 600MHz+ ?


Regards,
Andr?

MATRIX VISION GmbH, Talstrasse 16, DE-71570 Oppenweiler
Registergericht: Amtsgericht Stuttgart, HRB 271090
Geschaeftsfuehrer: Gerhard Thullner, Werner Armingeon, Uwe Furtner

  reply	other threads:[~2010-11-05  8:24 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-04 14:45 [U-Boot] [PATCH] mpc83xx: Make it boot again Joakim Tjernlund
2010-11-04 16:47 ` Wood Scott-B07421
2010-11-04 16:57   ` Timur Tabi
2010-11-04 19:49     ` Wood Scott-B07421
2010-11-05  8:24       ` Andre Schwarz [this message]
2010-11-10 12:46       ` Joakim Tjernlund
2010-11-12 15:43         ` Joakim Tjernlund
2010-11-04 17:02   ` Joakim Tjernlund
2010-11-12 15:58   ` Kumar Gala
2010-11-12 17:22     ` Scott Wood
2010-11-12 19:26       ` Kumar Gala
2010-11-12 19:31         ` Scott Wood
2010-11-15  9:57           ` Andre Schwarz
2010-11-15 10:13             ` Joakim Tjernlund
2010-11-15 14:40               ` Liu Dave-R63238
2010-11-15 15:05                 ` Andre Schwarz
2010-11-15 16:43                   ` Liu Dave-R63238
2010-11-15 17:30                     ` Joakim Tjernlund
2010-11-15 18:37                       ` Scott Wood
2010-11-15 23:49                         ` Liu Dave-R63238
2010-11-17 16:57                     ` Joakim Tjernlund
2010-11-17 17:02                       ` Liu Dave-R63238
2010-11-17 17:05                       ` Scott Wood
     [not found]                         ` <OFEC1AFE7E. <20101117130325.6069bede@udp111988uds.am.freescale.net>
2010-11-17 17:26                         ` Joakim Tjernlund
2010-11-17 19:03                           ` Scott Wood
2010-11-17 19:15                             ` Joakim Tjernlund
2010-11-17 19:27                               ` Scott Wood
2010-11-17 21:00                                 ` Joakim Tjernlund
2010-11-12 15:58 ` Kumar Gala
2010-11-12 16:36   ` 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=4CD3BF2C.1070705@matrix-vision.de \
    --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