linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Om Vadlapatla <pdfdoc15@yahoo.com>
Cc: "U-Boot-Users@lists.sourceforge.net"
	<U-Boot-Users@lists.sourceforge.net>,
	"linuxppc-embedded@ozlabs.org" <linuxppc-embedded@ozlabs.org>
Subject: Re: Failure of 2 BAT schemes to enable D-cache
Date: Fri, 12 May 2006 00:38:14 +0200	[thread overview]
Message-ID: <20060511223814.2195C352B0C@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 11 May 2006 13:13:29 PDT." <20060511201329.23866.qmail@web37105.mail.mud.yahoo.com>

In message <20060511201329.23866.qmail@web37105.mail.mud.yahoo.com> you wrote:
>
> Please post comments and suggestions of how I can
> initialized MMU for d-cache performance. I am  new
> to this.

We have been through this before, several times. Many times actually.
I have explained it to you, and so did others.

It is perfectly fine with me if you ignore my advice. But then please
stop posting the same question again and again here.

You will not receive any new answers.

Again, and definitely for the last time:

It makes no sense to try to enable the data cache on a MPC82xx system
in U-Boot; the time you could save if you succeeded  is  marginal  to
your application startup time.

And in Linux the D-Cache is enabled, so no changes are needed.


Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
They say a little knowledge is a dangerous thing,  but it is not  one
half so bad as a lot of ignorance.   - Terry Pratchett, _Equal Rites_

  reply	other threads:[~2006-05-11 22:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-11 20:13 Failure of 2 BAT schemes to enable D-cache Om Vadlapatla
2006-05-11 22:38 ` Wolfgang Denk [this message]
2006-05-12 12:26   ` [U-Boot-Users] " Jerry Van Baren

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=20060511223814.2195C352B0C@atlas.denx.de \
    --to=wd@denx.de \
    --cc=U-Boot-Users@lists.sourceforge.net \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=pdfdoc15@yahoo.com \
    /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;
as well as URLs for NNTP newsgroup(s).