[Sorry for the delay, I was quite busy those days and unable to test the
patch...]
Le mardi 19 septembre 2006 à 17:34 +0200, Jan Kiszka a écrit :
Or maybe we should lower the API level a little bit, and let the user
specify the physical address of the mapping instead of the virtual
Stelian Pop wrote:
[Sorry for the delay, I was quite busy those days and unable to test the
patch...]
Le mardi 19 septembre 2006 à 17:34 +0200, Jan Kiszka a écrit :
Or maybe we should lower the API level a little bit, and let the user
specify the physical address of the mapping instead of
Le vendredi 22 septembre 2006 à 10:58 +0200, Jan Kiszka a écrit :
d) make a special rtdm_mmap_iomem_to_user() function...
Also an option. Specifically, it wouldn't break the existing API... What
about rtdm_iomap_to_user? Would you like to work out a patch in this
direction?
Here it
Stelian Pop wrote:
Le vendredi 22 septembre 2006 à 10:58 +0200, Jan Kiszka a écrit :
d) make a special rtdm_mmap_iomem_to_user() function...
Also an option. Specifically, it wouldn't break the existing API... What
about rtdm_iomap_to_user? Would you like to work out a patch in this
Le vendredi 15 septembre 2006 à 18:40 +0200, Jan Kiszka a écrit :
In case no one comes up with an easy, portable way to detect remapped
memory as well: What about some flags the caller of rtdm_mmap_to_user
has to pass, telling what kind of memory it is? Would simplify the RTDM
part, and the
Hi,
I need to be able to map an IO memory buffer to userspace from a RTDM
driver.
rtdm_mmap_to_user() seems to do what I need, but it doesn't work. Its
code thinks that all virtual addresses between VMALLOC_START and
VMALLOC_END are obtained through vmalloc() and tries to call
Stelian Pop wrote:
Hi,
I need to be able to map an IO memory buffer to userspace from a RTDM
driver.
rtdm_mmap_to_user() seems to do what I need, but it doesn't work. Its
code thinks that all virtual addresses between VMALLOC_START and
VMALLOC_END are obtained through vmalloc() and tries
