Michel Dänzer wrote:
>On Thu, 2002-07-18 at 16:40, Keith Whitwell wrote:
>
>>Henry Worth wrote:
>>
>>>
>>I have no idea why there is a need for the RING_SPACE_TEST macro. It's
>>disabled in the r200 branch.
>>
>
>Besides, I've never hit the added code there.
>
Ok, I won't worry about that.
>>>The current drm r128 does not have any WAIT_UNTIL_*_IDLE macros.
>>>I assume I'm going to need at least a general idle wait to address sync
>>>issues. The only WAIT_UNTIL mask bit defined in r128_drv.h is for page
>>>flip, are there any other bits available for wait functions?
>>>
>>What does the r128 currently do to synchronize access to the framebuffer?
>>
>
>XAA handles that, and both drivers provide WaitForIdle() as the Sync
>function.
>
>>It may be that 2d & 3d are synchronized by the hardware automatically,
>>
>
>I doubt that, e.g. the texture blit ioctl also flushes the pixel cache.
>Maybe there's more to do with the PC_{,N}GUI_* registers?
>
>>but you'll always need to do something before accessing the framebuffer
>>directly.
>>
>
>I don't see where direct framebuffer access is involved when using DMA
>transfers for Xv.
>
So where to go from here? I can only spend a couple more days on this in
the near
term, so I don't have time to deal with the NDA and digging thru the
docs. Unless
someone else has a good recommendation, I'll try to flesh out some sync code
based on the radeon code and maybe someone else can correct the details
later.
Henry
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
