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
Subject: Re: When I use ichache_enable or dcache_enable in uboot,it crash
Date: Thu, 7 Dec 2006 20:20:36 +0800	[thread overview]
Message-ID: <001501c719fa$19e45020$8809a8c0@class> (raw)
In-Reply-To: 20061207095910.AD77667BB2@ozlabs.org

disable icache& dcache at the beginning is essential or else your program 
will crash. Only when you do the proper initiation, can you enable them. For 
details you can refer to you reference manual.


----- Original Message ----- 
From: "陈希" <xchen@sunrisetelecom.com.cn>
To: <linuxppc-embedded@ozlabs.org>; <linuxppc-embedded-request@ozlabs.org>
Sent: Thursday, December 07, 2006 5:52 PM
Subject: When I use ichache_enable or dcache_enable in uboot,it crash


> Hi,
>
> In the very begin of the uboot, the dcache is disable and the icache
> is enable. The code runs in flash nomarlly. Then the uboot should jump to
> ram and if I don't  disable icache the uboot will crash. I can't enable 
> the
> dcache too. The more serious problem is that when I boot the linux kernel
> ,it will stop at init_mmu. I think it is the same reason. Please help me.
>
> Thanks & Br,
> Andy
>
>


--------------------------------------------------------------------------------


> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded 

  reply	other threads:[~2006-12-07 12:20 UTC|newest]

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

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='001501c719fa$19e45020$8809a8c0@class' \
    --to=enorm@126.com \
    --cc=linuxppc-embedded-request@ozlabs.org \
    --cc=linuxppc-embedded@ozlabs.org \
    --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).