linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "siman" <siman@bsysjob.sharella.com>
To: <linuxppc-embedded@ozlabs.org>
Subject: port linux to prpmc610  kernel-2.4.25 with MVME2100 patch
Date: Tue, 10 Jan 2006 20:06:37 +0800	[thread overview]
Message-ID: <000001c615de$58f01590$1200a8c0@xbh> (raw)
In-Reply-To: <20060110082311.B29B1689DF@ozlabs.org>

[-- Attachment #1: Type: text/plain, Size: 987 bytes --]

Hi All:
I still work for port the Linux to the prpmc610 board. I get the MVME2100
patch on the kernel-2.4.25, so I port base it, because the MVME2100 have the
MPC8240 CPU  similar  the MPC8245, they all have 603e core.

I use the light a LED on the prpmc610 to trace the kernel code. I start at
the "head's",  I found it will be dead on CPU initial. The detail
information is dead on the file "cpu_setup_6xx.S" function below:

setup_common_caches:
	mfspr	r11,HID0
	andi.	r0,r11,HID0_DCE
	ori	r11,r11,HID0_ICE|HID0_DCE
	ori	r8,r11,HID0_ICFI
	bne	1f			/* don't invalidate the D-cache */
	ori	r8,r8,HID0_DCI		/* unless it wasn't enabled */
1:	sync
	mtspr	HID0,r8			/* enable and invalidate caches */
	sync
	mtspr	HID0,r11		/* enable caches */
	sync
	isync
	blr

it will be dead on the 	"mtspr	HID0,r8			/* enable and
invalidate caches */" ,
 
who has any experience for this, Please tell me, Thank you so much.
The attached is MVME2100 patch file. 
Any very good man may tell me why dead?

[-- Attachment #2: mvme2100-linux-2.4.25.patch.bz2 --]
[-- Type: application/octet-stream, Size: 9130 bytes --]

           reply	other threads:[~2006-01-10 12:03 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20060110082311.B29B1689DF@ozlabs.org>]

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='000001c615de$58f01590$1200a8c0@xbh' \
    --to=siman@bsysjob.sharella.com \
    --cc=linuxppc-embedded@ozlabs.org \
    /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).