From: Franck Bui-Huu <vagabon.xyz@gmail.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: mbizon@freebox.fr, post@pfrst.de, linux-mips <linux-mips@linux-mips.org>
Subject: [PATCH] Always include PHYS_OFFSET in PAGE_OFFSET
Date: Mon, 19 Mar 2007 16:59:15 +0100 [thread overview]
Message-ID: <45FEB353.5020001@innova-card.com> (raw)
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 for these platforms there are no more needs to change
PAGE_OFFSET.
For mapped kernel, they need to redefine PAGE_OFFSET anyways.
Signed-off-by: Franck Bui-Huu <fbuihuu@gmail.com>
---
Maxime,
Could you give a try to this patch ? It removes the need to
change your PAGE_OFFSET. If I remember correctly it's now
0x90000000, and you should be able to restore back to
0x80000000.
Franck
include/asm-mips/mach-generic/spaces.h | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/include/asm-mips/mach-generic/spaces.h b/include/asm-mips/mach-generic/spaces.h
index 0ae9997..600561f 100644
--- a/include/asm-mips/mach-generic/spaces.h
+++ b/include/asm-mips/mach-generic/spaces.h
@@ -22,7 +22,7 @@
* This handles the memory map.
* We handle pages at KSEG0 for kernels with 32 bit address space.
*/
-#define PAGE_OFFSET 0x80000000UL
+#define PAGE_OFFSET (0x80000000UL + PHYS_OFFSET)
/*
* Memory above this physical address will be considered highmem.
@@ -39,9 +39,9 @@
* This handles the memory map.
*/
#ifdef CONFIG_DMA_NONCOHERENT
-#define PAGE_OFFSET 0x9800000000000000UL
+#define PAGE_OFFSET (0x9800000000000000UL + PHYS_OFFSET)
#else
-#define PAGE_OFFSET 0xa800000000000000UL
+#define PAGE_OFFSET (0xa800000000000000UL + PHYS_OFFSET)
#endif
/*
--
1.4.4.3.ge6d4
next reply other threads:[~2007-03-19 16:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-19 15:59 Franck Bui-Huu [this message]
2007-03-20 16:21 ` [PATCH] Always include PHYS_OFFSET in PAGE_OFFSET Franck Bui-Huu
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=45FEB353.5020001@innova-card.com \
--to=vagabon.xyz@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=mbizon@freebox.fr \
--cc=post@pfrst.de \
--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.