From: a.othieno@bluewin.ch (Arthur Othieno)
To: akpm@osdl.org
Cc: gc-linux-devel@lists.sourceforge.net, linuxppc-embedded@ozlabs.org
Subject: [PATCH 2/2] ppc32: Add cputable entry for 750CXe DD2.4 ("Gekko")
Date: Tue, 30 Aug 2005 19:45:17 -0400 [thread overview]
Message-ID: <20050830234517.GC16375@mars> (raw)
In-Reply-To: <20050830233759.GA16375@mars>
Add a table entry for 750CXe DD2.4 ("Gekko") as found in the GameCube
from Nintendo:
http://www-306.ibm.com/chips/techlib/techlib.nsf/techdocs/291C8D0EF3EAEC1687256B72005C745C#C1
Signed-off-by: Arthur Othieno <a.othieno@bluewin.ch>
cputable.c | 14 ++++++++++++++
1 files changed, 14 insertions(+)
diff -uprN a/arch/ppc/kernel/cputable.c b/arch/ppc/kernel/cputable.c
--- a/arch/ppc/kernel/cputable.c 2005-08-30 18:18:28.000000000 -0400
+++ b/arch/ppc/kernel/cputable.c 2005-08-30 19:21:15.000000000 -0400
@@ -240,6 +240,20 @@ struct cpu_spec cpu_specs[] = {
.num_pmcs = 4,
.cpu_setup = __setup_cpu_750cx
},
+ { /* 750CXe "Gekko" (83214) */
+ .pvr_mask = 0xffffffff,
+ .pvr_value = 0x00083214,
+ .cpu_name = "750CXe",
+ .cpu_features = CPU_FTR_COMMON |
+ CPU_FTR_SPLIT_ID_CACHE | CPU_FTR_MAYBE_CAN_DOZE |
+ CPU_FTR_USE_TB | CPU_FTR_L2CR | CPU_FTR_TAU |
+ CPU_FTR_HPTE_TABLE | CPU_FTR_MAYBE_CAN_NAP,
+ .cpu_user_features = COMMON_PPC,
+ .icache_bsize = 32,
+ .dcache_bsize = 32,
+ .num_pmcs = 4,
+ .cpu_setup = __setup_cpu_750cx
+ },
{ /* 745/755 */
.pvr_mask = 0xfffff000,
.pvr_value = 0x00083000,
prev parent reply other threads:[~2005-08-30 23:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-30 23:37 [PATCH 0/2] ppc32: Add cputable entry for 750CXe DD2.4 Arthur Othieno
2005-08-30 23:42 ` [PATCH 1/2] ppc32: Re-order cputable for 750CXe DD2.4 entry Arthur Othieno
2005-08-30 23:45 ` Arthur Othieno [this message]
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=20050830234517.GC16375@mars \
--to=a.othieno@bluewin.ch \
--cc=akpm@osdl.org \
--cc=gc-linux-devel@lists.sourceforge.net \
--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).