>What are you actually saying, that pages mapped in agp can't be written
>by any
>means, or just that they can't be written through the agp address range?
Through the AGP address range. I work around this by hacking the DRM to
map the RAM pages directly in drmMap using specific vmops and a hacked
agp_ioremap. AFAIK, ia64 has similar limitations and I've been told
other recent bridges used on non-x86 at least share this design "mistake"
>It sounds kindof broken to me in any case. How to mtrrs work in this world?
They don't exist ;)
>> That way, if you want several AGP contexts, you can have the processes
>> tapping their AGP buffers without lock, locking would only be required
>> once it's time to move one of these buffers in/out the physical GART
>> under the arbitration of the DRM.
>
>You don't need to lock to write to agp buffers in the current scheme.
>
>You also don't need to play with the gart table just to draw a 2-triangle
>strip. On some chipsets, particularly under smp, modifying the gart
table is
>very slow. Ask Jeff about this.
Ok.
Ben.
----------------------------------------------------------------------------
Bringing you mounds of caffeinated joy
>>> http://thinkgeek.com/sf <<<
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
