From: Wade Farnsworth <wfarnsworth@mvista.com>
To: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: [PATCH 4/6] L2 Cache support for 440SP
Date: 01 Mar 2006 16:51:24 -0700 [thread overview]
Message-ID: <1141257084.25758.28.camel@rhino.az.mvista.com> (raw)
In-Reply-To: <1141257021.25761.26.camel@rhino.az.mvista.com>
[-- Attachment #1: Type: text/plain, Size: 107 bytes --]
This adds L2 Cache support for the 440SP.
--Wade
Signed off by: Wade Farnsworth <wfarnsworth@mvista.com>
[-- Attachment #2: luan-l2c.patch --]
[-- Type: text/x-patch, Size: 636 bytes --]
diff --git a/arch/ppc/platforms/4xx/luan.c b/arch/ppc/platforms/4xx/luan.c
--- a/arch/ppc/platforms/4xx/luan.c
+++ b/arch/ppc/platforms/4xx/luan.c
@@ -408,6 +408,11 @@ luan_setup_arch(void)
printk("Luan port (MontaVista Software, Inc. <source@mvista.com>)\n");
}
+static void __init luan_init(void)
+{
+ ibm440gx_l2c_setup(&clocks);
+}
+
void __init platform_init(unsigned long r3, unsigned long r4,
unsigned long r5, unsigned long r6, unsigned long r7)
{
@@ -422,4 +427,5 @@ void __init platform_init(unsigned long
#ifdef CONFIG_KGDB
ppc_md.early_serial_map = luan_early_serial_map;
#endif
+ ppc_md.init = luan_init;
}
next prev parent reply other threads:[~2006-03-01 23:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 23:35 [PATCH 0/6] AMCC 440SP/Luan board enhancements & fixes Wade Farnsworth
2006-03-01 23:45 ` [PATCH 1/6] Support for UART 2 on 440SP and Luan Wade Farnsworth
2006-03-01 23:47 ` [PATCH 2/6] Add UIC settings for 440SP & Luan Wade Farnsworth
2006-03-01 23:50 ` [PATCH 3/6] PCIX fixes and enhancements " Wade Farnsworth
2006-03-01 23:51 ` Wade Farnsworth [this message]
2006-03-01 23:52 ` [PATCH 5/6] Clock and power management define fixes for 440SP Wade Farnsworth
2006-03-01 23:54 ` [PATCH 6/6] MTD defines for Luan Wade Farnsworth
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=1141257084.25758.28.camel@rhino.az.mvista.com \
--to=wfarnsworth@mvista.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