What happened when the user space application accesss device registers via mapped memory on /dev/mem?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.


 

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux