From: tsbogend@alpha.franken.de (Thomas Bogendoerfer)
To: Franck Bui-Huu <vagabon.xyz@gmail.com>
Cc: mbizon@freebox.fr, linux-mips <linux-mips@linux-mips.org>
Subject: Re: [PATCH 0/2] FLATMEM: allow memory to start at pfn != 0 [take #2]
Date: Wed, 7 Mar 2007 14:18:42 +0100 [thread overview]
Message-ID: <20070307131842.GA9361@alpha.franken.de> (raw)
In-Reply-To: <cda58cb80703061339l2f8cfc09m5823b090b69a7aa7@mail.gmail.com>
On Tue, Mar 06, 2007 at 10:39:59PM +0100, Franck Bui-Huu wrote:
> I think you missed PAGE_OFFSET meaning...
>
> PAGE_OFFSET is the start of the kernel virtual address space and
> before this patchset pa(PAGE_OFFSET) was always 0.
>
> In your case, you said:
>
> PAGE_OFFSET = 0x80000000
> PHYS_OFFSET = 0x10000000
>
> this means that the first kernel virtual address is 0x80000000 and the
> corresponding physical address is 0x10000000. If you load your kernel
> at 0x9000xxxx, it will be loaded in physical memory located at
> 0x2000xxxx which is obviously not what you want.
which sound like a very bogus setup for at leat 32bit MIPS. The mapping
virtual 0x80000000 to physical 0x00000000 is a CPU thing and can't
be changed.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessary a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2007-03-07 13:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-10 8:44 [PATCH 0/2] FLATMEM: allow memory to start at pfn != 0 [take #2] Franck Bui-Huu
2007-01-10 8:44 ` [PATCH 1/2] Setup min_low_pfn/max_low_pfn correctly Franck Bui-Huu
2007-01-10 8:44 ` [PATCH 2/2] FLATMEM: introduce PHYS_OFFSET Franck Bui-Huu
2007-01-10 11:20 ` [PATCH 0/2] FLATMEM: allow memory to start at pfn != 0 [take #2] Ralf Baechle
2007-01-10 14:52 ` Franck Bui-Huu
2007-03-02 23:45 ` Maxime Bizon
2007-03-05 14:15 ` Franck Bui-Huu
2007-03-05 16:33 ` Maxime Bizon
2007-03-06 21:39 ` Franck Bui-Huu
2007-03-07 13:18 ` Thomas Bogendoerfer [this message]
2007-03-07 16:58 ` Maxime Bizon
2007-03-08 9:01 ` Franck Bui-Huu
2007-03-08 8:54 ` Franck Bui-Huu
2007-03-09 13:18 ` peter fuerst
2007-03-09 13:35 ` Franck Bui-Huu
2007-03-10 9:36 ` peter fuerst
2007-03-12 9:47 ` Franck Bui-Huu
2007-03-12 13:03 ` peter fuerst
2007-03-12 17:05 ` Franck Bui-Huu
2007-03-12 20:02 ` peter fuerst
2007-03-13 8:37 ` Franck Bui-Huu
2007-03-18 11:30 ` peter fuerst
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=20070307131842.GA9361@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-mips@linux-mips.org \
--cc=mbizon@freebox.fr \
--cc=vagabon.xyz@gmail.com \
/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