All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] ppc4xx: Add dcache_enable() for 440
Date: Mon, 21 Apr 2008 11:45:27 +0200	[thread overview]
Message-ID: <200804211145.28004.sr@denx.de> (raw)
In-Reply-To: <20080421091255.1E5A224764@gemini.denx.de>

On Monday 21 April 2008, Wolfgang Denk wrote:
> > This has nothing to do with 440. It's more a general question. But OK,
> > from my
>
> Well, it affects only processors which need MMU support. Most doen't.

I'm not so sure here anymore with all the newer PPC's and other platforms. But 
I have to admit that I'm no expert for those other platforms.

> > understanding, it makes most sense that the i/dcache U-Boot commands
> > touch the cache attributes of all SDRAM related TLB's.
>
> In general, the chackes should be enabled whenever and whereever
> possible.
>
> I think it should be pretty safe to enable the I cache for all SDRAM,
> SRAM and flash areas; or,  put  differently,  for  all  memory  areas
> except maybe any mapped PCI memory windows.
>
> If possible, also D cahce should be enabled, but I cannot judge if
> this works or not with the given driver code.
>
> Also, it depends on where the initial stack and data is located  (you
> probably cannot disable caches if you put initial data in cache).

Another problemtic issue could be the POST area for caches etc. I know that 
self modifying code is used here in some places. This could be more 
problematic with caches enabled.

<snip>

> > And what does this mean that you "insist that this must be fixed for the
> > next release"? I'm sorry, but I personally can't promise to "fix" this
> > issue until the next merge window opens.
>
> Next release means the one that comes after the next merge window.

I did understand this part of the sentence. I'm just not sure what should 
happen with the current code if it doesn't get changed. Again, I personally 
can't promise to "fix" this issue until the next merge window opens.

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-21  9:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-18 14:51 [U-Boot-Users] [PATCH] ppc4xx: Add dcache_enable() for 440 Stefan Roese
2008-04-20 22:34 ` Wolfgang Denk
2008-04-21  4:58   ` Stefan Roese
2008-04-21  5:04     ` Wolfgang Denk
2008-04-21  5:29       ` Stefan Roese
2008-04-21  7:44         ` Wolfgang Denk
2008-04-21  8:23           ` Stefan Roese
2008-04-21  9:12             ` Wolfgang Denk
2008-04-21  9:45               ` Stefan Roese [this message]
2008-04-21 10:27                 ` Wolfgang Denk
2008-04-21 11:37 ` [U-Boot-Users] [PATCH] Fix missing dcache_enable symbol and declare cache function as weak Jean-Christophe PLAGNIOL-VILLARD
2008-04-21 12:18   ` 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=200804211145.28004.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 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.