Hi.
On Maw, 2004-11-30 at 20:09, Thomas Hellström wrote:
Textures in AGP memory is currently not allowed, but they are disabled
in the Mesa driver as well, for some reason. If they are allowed in the
future, Texture address checks probably have to be implemented but that
should be a minor
Thomas Hellström wrote:
Hi.
On Maw, 2004-11-30 at 20:09, Thomas Hellström wrote:
Textures in AGP memory is currently not allowed, but they are disabled
in the Mesa driver as well, for some reason. If they are allowed in the
future, Texture address checks probably have to be implemented but that
On Maw, 2004-11-30 at 20:09, Thomas Hellström wrote:
Textures in AGP memory is currently not allowed, but they are disabled
in the Mesa driver as well, for some reason. If they are allowed in the
future, Texture address checks probably have to be implemented but that
should be a minor task.
On Mer, 2004-12-01 at 12:19, Thomas Hellstrm wrote:
Actually, I've been running with a 512Kb userspace / kernel buffer, and
I've not seen any noticable drop in performance, but I'm not sure that the
submissions actually will be that large with the programs I've tested.
Might be worth finding
Hi!
I've put together a DMA command verifier for the VIA drm. It restricts
access to DMA registers and system and AGP memory while 3D commands and
2D / Mpeg is allowed to pass.
Currently frame-buffer memory is considered all authenticated client's
property, but I've added provisions to check
On Maw, 2004-11-30 at 20:09, Thomas Hellstrm wrote:
Textures in AGP memory is currently not allowed, but they are disabled
in the Mesa driver as well, for some reason. If they are allowed in the
future, Texture address checks probably have to be implemented but that
should be a minor task.
