On Sat, Oct 11, 2014 at 10:51 AM, Hu Keping wrote:
> As there are many drivers using /dev/mem and we can not
> make sure that the different task will not trample on
> each others memory.Shall we add some printk to help locating the problem
> when error happened?
Actually no driver should use /dev
Hi there,
Recently, I run a little testcase about using mmap to check
some physical address.What I found was that the different task can
read and write the same physical address at the same time.
For example,
I make proc1 to access 0x2000, read and write "512" to
that address every 2 seconds.
2 matches
Mail list logo
