linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "enorm" <enorm@126.com>
To: 陈希 <xchen@sunrisetelecom.com.cn>,
	linuxppc-embedded@ozlabs.org,
	linuxppc-embedded-request@ozlabs.org
Cc: 'Elvis Ma' <npma@sunrisetelecom.com.cn>
Subject: Re: When I use ichache_enable or dcache_enable in uboot,it crash
Date: Fri, 8 Dec 2006 09:55:11 +0800	[thread overview]
Message-ID: <004001c71a6b$e5c87150$8809a8c0@class> (raw)
In-Reply-To: 4578C0DC.0D5B9A.00597

At the end of the "board_init_f()" function all data and code will be 
relocated to SDRAM. So, If you enable icache & dcache it will cause 
inconsistence between cache and Memory, so your program will crash




----- Original Message ----- 
From: "陈希" <xchen@sunrisetelecom.com.cn>
To: "'enorm'" <enorm@126.com>; <linuxppc-embedded@ozlabs.org>; 
<linuxppc-embedded-request@ozlabs.org>
Cc: "'Elvis Ma'" <npma@sunrisetelecom.com.cn>
Sent: Friday, December 08, 2006 9:33 AM
Subject: Re: When I use ichache_enable or dcache_enable in uboot,it crash


Hi enorm

Thank you for your reply. In fact, the uboot has never disable
icache. The icache is enable at all times.And the code run in flash normally
when the icache is enable.  I have to add disable_icache() in the
board_init_f() so that the code can run in ram normally.  BTW, I just use
the function supported by uboot to enable icache&dcache, I'm sure the steps
of cache init have no problem. I just can't understand why the icache can
effect the code run in ram.

Thanks &Br,
Andy

       reply	other threads:[~2006-12-08  1:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4578C0DC.0D5B9A.00597>
2006-12-08  1:55 ` enorm [this message]
2006-12-08  2:43   ` When I use ichache_enable or dcache_enable in uboot,it crash 陈希
     [not found] <20061208024333.C5FCB67B6F@ozlabs.org>
2006-12-08  7:48 ` 陈希
2006-12-07  9:52 陈希
2006-12-07 12:20 ` enorm
2006-12-08  1:33   ` 陈希

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='004001c71a6b$e5c87150$8809a8c0@class' \
    --to=enorm@126.com \
    --cc=linuxppc-embedded-request@ozlabs.org \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=npma@sunrisetelecom.com.cn \
    --cc=xchen@sunrisetelecom.com.cn \
    /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).