From: Franck Bui-Huu <vagabon.xyz@gmail.com>
To: ralf@linux-mips.org
Cc: linux-mips@linux-mips.org
Subject: [PATCH 3/5] Make PAGE_OFFSET aware of PHYS_OFFSET
Date: Mon, 4 Jun 2007 17:46:33 +0200 [thread overview]
Message-ID: <1180971996831-git-send-email-fbuihuu@gmail.com> (raw)
In-Reply-To: <1180971995757-git-send-email-fbuihuu@gmail.com>
From: Franck Bui-Huu <fbuihuu@gmail.com>
For platforms that use PHYS_OFFSET and do not use a mapped kernel,
this patch automatically adds PHYS_OFFSET into PAGE_OFFSET.
Therefore there are no more needs for them to redefine PAGE_OFFSET.
For mapped kernel, they need to redefine PAGE_OFFSET anyways.
Signed-off-by: Franck Bui-Huu <fbuihuu@gmail.com>
---
include/asm-mips/mach-generic/spaces.h | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/include/asm-mips/mach-generic/spaces.h b/include/asm-mips/mach-generic/spaces.h
index c90900b..96c8971 100644
--- a/include/asm-mips/mach-generic/spaces.h
+++ b/include/asm-mips/mach-generic/spaces.h
@@ -72,7 +72,7 @@
* This handles the memory map.
*/
#ifndef PAGE_OFFSET
-#define PAGE_OFFSET CAC_BASE
+#define PAGE_OFFSET (CAC_BASE + PHYS_OFFSET)
#endif
--
1.5.1.4
next prev parent reply other threads:[~2007-06-04 15:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 15:46 [PATCH 0/5] PHYS_OFFSET fix and cleanup [take #2] Franck Bui-Huu
2007-06-04 15:46 ` [PATCH 1/5] Allow generic spaces.h to be included by platform specific ones Franck Bui-Huu
2007-06-07 7:32 ` Ralf Baechle
2007-06-04 15:46 ` [PATCH 2/5] Clean up asm-mips/mach-generic/spaces.h Franck Bui-Huu
2007-06-07 7:32 ` Ralf Baechle
2007-06-04 15:46 ` Franck Bui-Huu [this message]
2007-06-07 7:32 ` [PATCH 3/5] Make PAGE_OFFSET aware of PHYS_OFFSET Ralf Baechle
2007-06-04 15:46 ` [PATCH 4/5] Move PHY_OFFSET definition in spaces.h Franck Bui-Huu
2007-06-07 7:32 ` Ralf Baechle
2007-06-04 15:46 ` [PATCH 5/5] Fix PHYS_OFFSET for 64-bits kernels with 32-bits symbols Franck Bui-Huu
2007-06-07 7:32 ` Ralf Baechle
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=1180971996831-git-send-email-fbuihuu@gmail.com \
--to=vagabon.xyz@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.