[R300 and other radeons] MergedFB lockups
Vladimir Dergachev
volodya at mindspring.com
Sat Feb 19 08:05:51 PST 2005
On Sat, 19 Feb 2005, Alex Deucher wrote:
> On Sat, 19 Feb 2005 09:56:33 -0500 (EST), Vladimir Dergachev
> <volodya at mindspring.com> wrote:
>>>>
>>>> Also, I have no idea why the code in radeon_cursor.c that writes images
>>>> directly into framebuffer memory works - according to the manual any
>>>> writes into framebuffer while GUI is active should cause a hard lock.
>>>>
>>>> However, I could not produce any lockups with it, and so left it as is.
>>>>
>>>
>>> Does using the overlay also cause a lockup? there are some non-idled
>>> INREGs in there as well. I've never had a problem with them on r100
>>> or r200 though.
>>
>> Not anymore, I think I fixed all of those when importing GATOS code a
>> while back.
>
> there's still one is the overlay gamma setup function, and I think
> another one further down. I can add the idle calls at some point this
> weekend unless someone beats me to it.
Ohh I see - these are triggerred only by changing Xv attributes and I
don't think many people do this simultaneously with running 3d.
I fixed it, no problem.
best
Vladimir Dergachev
More information about the xorg
mailing list