* What happened when the user space application accesss device registers via mapped memory on /dev/mem?
@ 2017-12-07 7:09 kipade
0 siblings, 0 replies; only message in thread
From: kipade @ 2017-12-07 7:09 UTC (permalink / raw)
To: kernelnewbies
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2017-12-07 7:09 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-12-07 7:09 What happened when the user space application accesss device registers via mapped memory on /dev/mem? kipade
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).