From: Roland Dreier <rolandd@cisco.com>
To: mporter@kernel.crashing.org
Cc: linuxppc-embedded@ozlabs.org
Subject: [PATCH 1/4] [PPC32] Allow ERPN for early serial to depend on CPU type
Date: Thu, 22 Sep 2005 20:03:35 -0700 [thread overview]
Message-ID: <2005922203.92drttvd27WS9dXk@cisco.com> (raw)
In-Reply-To: <2005922203.zpZEPMsMBP43qjJI@cisco.com>
The PowerPC 440SPe supports up to 16 GB of RAM, and therefore its IO
registers are at 0x4_xxxx_xxxx instead of being at 0x1_xxxx_xxxx like
most other PPC 440 chips. To allow for this, this patch moves the
definition of the ERPN used for mapping UART0 from being hard-coded in
the head_44x.S assembly code to being defined in ibm44x.h.
Signed-off-by: Roland Dreier <rolandd@cisco.com>
---
arch/ppc/kernel/head_44x.S | 4 ++--
include/asm-ppc/ibm44x.h | 7 ++++++-
2 files changed, 8 insertions(+), 3 deletions(-)
eb79641bc2a92b7d4c2f62e072650e20a7748f45
diff --git a/arch/ppc/kernel/head_44x.S b/arch/ppc/kernel/head_44x.S
--- a/arch/ppc/kernel/head_44x.S
+++ b/arch/ppc/kernel/head_44x.S
@@ -190,8 +190,8 @@ skpinv: addi r4,r4,1 /* Increment */
/* xlat fields */
lis r4,UART0_PHYS_IO_BASE@h /* RPN depends on SoC */
-#ifndef CONFIG_440EP
- ori r4,r4,0x0001 /* ERPN is 1 for second 4GB page */
+#ifdef UART0_PHYS_ERPN
+ ori r4,r4,UART0_PHYS_ERPN /* Add ERPN if above 4GB */
#endif
/* attrib fields */
diff --git a/include/asm-ppc/ibm44x.h b/include/asm-ppc/ibm44x.h
--- a/include/asm-ppc/ibm44x.h
+++ b/include/asm-ppc/ibm44x.h
@@ -34,12 +34,17 @@
/* Lowest TLB slot consumed by the default pinned TLBs */
#define PPC44x_LOW_SLOT 63
-/* LS 32-bits of UART0 physical address location for early serial text debug */
+/*
+ * Least significant 32-bits and extended real page number (ERPN) of
+ * UART0 physical address location for early serial text debug
+ */
#if defined(CONFIG_440SP)
+#define UART0_PHYS_ERPN 1
#define UART0_PHYS_IO_BASE 0xf0000200
#elif defined(CONFIG_440EP)
#define UART0_PHYS_IO_BASE 0xe0000000
#else
+#define UART0_PHYS_ERPN 1
#define UART0_PHYS_IO_BASE 0x40000200
#endif
next prev parent reply other threads:[~2005-09-23 3:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-23 3:03 [PATCH 0/4] 440SPe support Roland Dreier
2005-09-23 3:03 ` Roland Dreier [this message]
2005-09-23 3:03 ` [PATCH 2/4] [PPC32] Add " Roland Dreier
2005-09-23 3:03 ` [PATCH 3/4] [PPC32] ibm_emac: " Roland Dreier
2005-09-23 3:03 ` [PATCH 4/4] [PPC32] Add Yucca (440SPe eval board) platform Roland Dreier
2005-09-23 3:32 ` Eugene Surovegin
2005-09-23 5:44 ` Roland Dreier
2005-09-23 3:22 ` [PATCH 3/4] [PPC32] ibm_emac: Add 440SPe support Eugene Surovegin
2005-09-23 5:25 ` Roland Dreier
2005-09-23 8:24 ` Eugene Surovegin
2005-09-23 15:17 ` Roland Dreier
2005-09-23 17:11 ` Matt Porter
2005-09-23 20:25 ` Roland Dreier
2005-09-23 20:36 ` Matt Porter
2005-09-23 3:29 ` [PATCH 2/4] [PPC32] " Eugene Surovegin
2005-09-23 5:44 ` Roland Dreier
2005-09-23 17:17 ` Matt Porter
2005-09-23 20:27 ` Roland Dreier
2005-09-23 17:20 ` Matt Porter
2005-09-23 20:27 ` Roland Dreier
2005-09-23 22:44 ` Roland Dreier
2005-09-23 22:58 ` Eugene Surovegin
-- strict thread matches above, loose matches on Subject: below --
2005-10-12 4:20 [PATCH 0/4] updated " Roland Dreier
2005-10-12 4:20 ` [PATCH 1/4] [PPC32] Allow ERPN for early serial to depend on CPU type Roland Dreier
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=2005922203.92drttvd27WS9dXk@cisco.com \
--to=rolandd@cisco.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=mporter@kernel.crashing.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).