From: Dan Malek <dan@mvista.com>
To: Ofer Rashuk <OferR@Radlan.co.il>
Cc: "'linuxppc-embedded@lists.linuxppc.org'"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: virtual memory issue
Date: Mon, 05 Nov 2001 14:11:51 -0500 [thread overview]
Message-ID: <3BE6E477.1090508@mvista.com> (raw)
In-Reply-To: 42AB6BE23C29D511831E0002B32024881999FF@messenger.radlan.co.il
Ofer Rashuk wrote:
> my question is who can i translate the virtual address to a physical one.
You can't from a user program, nor do you want to do this. Using
mmap() to physical devices from a user application must be done
with great care, and is often used just for debugging purposes. There
are resources used by the kernel and other applications that cause
race conditions you can't control.
If you need access to physical memory for any reason, you must
write a kernel device driver for this device so you can properly
manage the resources necessary to ensure proper system operation.
Thanks.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-11-05 19:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-04 8:42 virtual memory issue Ofer Rashuk
2001-11-05 19:11 ` Dan Malek [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=3BE6E477.1090508@mvista.com \
--to=dan@mvista.com \
--cc=OferR@Radlan.co.il \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).