From: Josh Boyer <jwboyer@jdub.homelinux.org>
To: Srinivas Murthy <codevana@gmail.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: ioremap
Date: Mon, 01 May 2006 17:45:34 -0500 [thread overview]
Message-ID: <1146523534.3697.3.camel@vader.jdub.homelinux.org> (raw)
In-Reply-To: <7cb1293c0605011425w1cc34197h4d5fa73ad1077d5a@mail.gmail.com>
On Mon, 2006-05-01 at 14:25 -0700, Srinivas Murthy wrote:
> Hi,
> Why does ioremap() not allow normal system RAM to be mapped in using
> ioremap().
>
> We have a need to access a portion of the normal system RAM to be
> mapped in non-cached.
>
> To simulate, I used kmalloc() to allocate the memory and then passed
> the virt_to_phys() of the memory to ioremap() but then noticed that
> ioremap() wont allow it.
>
> Is there another way to access this memory non-cached?
Limit the amount of memory the kernel consumes using mem=XXM. Then you
should be able to use ioremap on the remainder.
josh
prev parent reply other threads:[~2006-05-01 23:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-01 21:25 ioremap Srinivas Murthy
2006-05-01 22:45 ` Josh Boyer [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=1146523534.3697.3.camel@vader.jdub.homelinux.org \
--to=jwboyer@jdub.homelinux.org \
--cc=codevana@gmail.com \
--cc=linuxppc-dev@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox