From: Franck Bui-Huu <vagabon.xyz@gmail.com>
To: ralf@linux-mips.org
Cc: linux-mips@linux-mips.org
Subject: [RFC] FLATMEM: allow memory to start at pfn != 0
Date: Wed, 6 Dec 2006 16:48:27 +0100 [thread overview]
Message-ID: <1165420110699-git-send-email-fbuihuu@gmail.com> (raw)
This patchset relaxes this constraint. Basically you just need to
define in your platform code (include/asm-mips/mach-foo/spaces.h
probably) PHYS_OFFSET that corresponds to the start of your
physical memory and you're done.
The first patch is just a fix for HIGHMEM, I just found it while
writing this patchset. I haven't done any tests though, I have
no hardwares to play with.
The second and third patchs are the real meat. There are 2 points
that I'm not really sure:
- PHYS_OFFSET is defined in page.h, I'm not sure if it's
the right place though.
- ARCH_PFN_OFFSET is always defined whatever the memory
model. I don't think it will hurt since physical memory
always has a starting point in all cases.
Please consider.
Franck
---
arch/mips/kernel/setup.c | 30 ++++++++++++++++++++++--------
arch/mips/mm/init.c | 30 +++++++++++++-----------------
include/asm-mips/dma.h | 1 +
include/asm-mips/io.h | 4 ++--
include/asm-mips/page.h | 25 +++++++++++++++++++++----
5 files changed, 59 insertions(+), 31 deletions(-)
next reply other threads:[~2006-12-06 15:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 15:48 Franck Bui-Huu [this message]
2006-12-06 15:48 ` [PATCH 1/3] paging_init(): use highend_pfn/highstart_pfn Franck Bui-Huu
2006-12-06 15:48 ` [PATCH 2/3] Setup min_low_pfn/max_low_pfn correctly Franck Bui-Huu
2006-12-11 18:16 ` Ralf Baechle
2006-12-12 9:14 ` Franck Bui-Huu
2006-12-06 15:48 ` [PATCH 3/3] FLATMEM: allow memory to start at pfn != 0 Franck Bui-Huu
2006-12-11 18:46 ` [RFC] " Ralf Baechle
2006-12-12 8:55 ` Franck Bui-Huu
2006-12-16 11:17 ` 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=1165420110699-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.