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-01 02:50 -------
(In reply to comment #6)
> It's been a while since I looked at the code in detail, but the problem at the
> time was a limitation of the DRM buffer management infrastructure. As I
> recall,
> there wasn't an easy way to create two sets of DMA buffers, one mapped to
> userspace, and one which wasn't mapped.
I did something that sounds like what you're trying to do, in the Savage driver
for command DMA. Instead of using the DMA buffer infractructure I simply created
a map of a chunck of AGP memory that can't be mapped to unprivileged clients.
The DRM uses that map as a command buffer with its own ageing and buffer
management implementation.
I was going to try something like that in the Mach64 driver. Not sure how
feasible this is or if there are any hardware issues that may prevent this.
--
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
