From: kipade@163.com (kipade)
To: kernelnewbies@lists.kernelnewbies.org
Subject: What happened when the user space application accesss device registers via mapped memory on /dev/mem?
Date: Thu, 7 Dec 2017 15:09:39 +0800 (CST) [thread overview]
Message-ID: <3bdea75e.77f5.1602fceef72.Coremail.kipade@163.com> (raw)
Hi all,
I want to know the details of device(not physical ram device) registers via mapped memory on /dev/mem.
For example, a Soc CPU has some internal device register resources, the driver will map the memory
block to a virtual memory to kernel. But, the user application can use /dev/mem to access it(devmem2).
I want to know why? and what's happened on the backend?
Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20171207/cb57e01d/attachment.html
reply other threads:[~2017-12-07 7:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3bdea75e.77f5.1602fceef72.Coremail.kipade@163.com \
--to=kipade@163.com \
--cc=kernelnewbies@lists.kernelnewbies.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).