From: Ralf Baechle <ralf@linux-mips.org>
To: "Nori, Soma Sekhar" <nsekhar@ti.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Dealing with RAM not starting at 0x00000000
Date: Thu, 3 Feb 2005 13:29:43 +0100 [thread overview]
Message-ID: <20050203122943.GA8509@linux-mips.org> (raw)
In-Reply-To: <F6B01C6242515443BB6E5DDD63AE935F04682B@dbde2k01.itg.ti.com>
On Tue, Feb 01, 2005 at 03:06:29PM +0530, Nori, Soma Sekhar wrote:
> I am working towards porting 2.6.10 kernel on a mips 4kec based board
> which has physical memory starting at 0x14000000.
> What is the best way to overcome the "hole" from 0x00000000 to
> 0x14000000 without incuring a huge memory overhead.
> (For exception handling there is 4k of RAM kept at 0x00000000 also - but
> I guess linux paging need need not be aware of this small RAM)
You can set PAGE_OFFSET to 0x94000000. If you do this you're probably
going to run into a few bugs where PAGE_OFFSET is assumed to be KSEG0,
that is 0x80000000. Nothing dramatic though.
Ralf
prev parent reply other threads:[~2005-02-03 12:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-01 9:36 Dealing with RAM not starting at 0x00000000 Nori, Soma Sekhar
2005-02-01 9:36 ` Nori, Soma Sekhar
2005-02-03 12:29 ` Ralf Baechle [this message]
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=20050203122943.GA8509@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=nsekhar@ti.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