Please do not reply to this email: if you want to comment on the bug, go to    
       
the URL shown below and enter yourcomments there.     
   
https://bugs.freedesktop.org/show_bug.cgi?id=6242          
     




------- Additional Comments From [EMAIL PROTECTED]  2006-04-04 10:51 -------
What about the following approach:

Do not map the DMA buffers to user-space.

For dma_vertex, nothing changes.

For dma_blit, the client submits a pointer to user-space memory. 
In the AGP case nothing changes since the default method is AGP texturing (in
fact "local_textures" do not currently work with AGP, bug #6209). 
In the PCI case, the simple thing is copy_from_user to a private DMA buffer. If
the performance regression is unacceptable, we can change the blit ioctl to
submit w/h/pitch parameters and turn the memcpy currently done in user-space to
copy_from_user. I presume that its easy to determine that the pointer actually
points to memory owned by the process.

Hopefully, we can reuse the current buffer management routines. If it is
possible to do drmAddBufs without drmMapBufs, then very little changes are
required (I saw a comment in drm_mapbufs that PCI buffers are actually mapped in
drm_addbufs ...).

Sorry if I am waisting your time with uninformed assumptions,
george.
          
     
     
--           
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email         
     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to