public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] PPC440EPx/sequoia TLB question...
Date: Thu, 24 Apr 2008 07:28:43 +0200	[thread overview]
Message-ID: <200804240728.44082.sr@denx.de> (raw)
In-Reply-To: <480FF00F.4080900@verizon.net>

On Thursday 24 April 2008, Dave Littell wrote:
> Well, there's registers in that address space, not unlike other
> registers in other TLB entries (PCI, BCSR, etc.) that are marked
> Guarded.  I would think the same rationale would apply to the internal
> registers.

We should probably split this up in multiple TLB entries then. SRAM without G 
set and registers with G set.

> I need to go back and check the register settings for speculative
> accesses.  I seem to remember that there's a 440EPx Errata (actually,
> more than one) that has a workaround that turns off speculative
> instruction fetches.  Data speculative accesses may have gotten squashed
> in there as well, so it wouldn't matter what the TLB said if that's the
> case.
>
> >> Also the TLB entry for SDRAM marks it Guarded, but that?s one area I
> >> would think wouldn't need to be Guarded.
> >
> > This could be a mistake. Should work without G bis set too. Please give
> > it a try and send a patch to fix it, if it works fine.
>
> Hard to define "works fine" - this is the same 440EPx platform I'm
> asking about over in the embedded Linux mailing list.  I'm pretty sure
> the kernel doesn't flag SDRAM as Guarded,

Yes, and the 4xx code to dynamically set the SDRAM TLB's in the SPD code 
doesn't set it either. So it really isn't needed.

> but I'll give it a try to see 
> how it goes.

Thanks.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

  reply	other threads:[~2008-04-24  5:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-23  3:11 [U-Boot-Users] PPC440EPx/sequoia TLB question Dave Littell
2008-04-23 12:42 ` Stefan Roese
2008-04-24  2:27   ` Dave Littell
2008-04-24  5:28     ` Stefan Roese [this message]
2008-04-24 11:58       ` Josh Boyer
2008-04-24 13:07         ` Stefan Roese
2008-04-25  2:34   ` [U-Boot-Users] [PATCH] " Dave Littell
2008-04-25  5:31     ` Stefan Roese
2008-04-26  1:54   ` [U-Boot-Users] " Dave Littell
2008-04-29  5:54     ` Stefan Roese

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=200804240728.44082.sr@denx.de \
    --to=sr@denx.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