Glitch in newer drm-next/drm-radeon-testing

[Dave Airlie]

On Mon, Aug 2, 2010 at 8:12 PM, Marius Gröger
<marius.groeger at googlemail.com> wrote:
> Am 07.06.2010 00:15, wrote Dave Airlie:
>>
>> On Mon, Jun 7, 2010 at 3:52 AM, Marius Gröger
>> <marius.groeger at googlemail.com>  wrote:
>>>
>>> Am 06.06.2010 18:47, schrieb James Simmons:
>>>>
>>>>>> Apologies for such an unspecific description, and for what almost
>>>>>> seems
>>>>>> like a support request for MythTV. I wouldn't post here if I were not
>>>>>> 100% sure it must be related with the recent drm changes.
>>>>>
>>>>> Note that the DRM APIs are intended for use by userspace components of
>>>>> graphics drivers / API libraries, not applications directly. MythTV
>>>>> shouldn't use the DRM directly for synchronization but rather use GLX
>>>>> synchronization APIs.
>>>>
>>>> Tho not the case for MythTV on a embedded device requiring apps to use
>>>> GLX
>>>> wuld be to heavy. I would agree libdrm should be used.
>>>
>>> I have found the cause for the glitch and just filed
>>> http://bugs.freedesktop.org/show_bug.cgi?id=28411.
>>
>> Okay I can see the problem, now I have to think of a good solution,
>>
>> I probably need to break down the locking a bit further which is a bit
>> messy.
>
> Is there any news on this issue? I didn't notice any commits to d-r-t or d-n
> WRT this, but then again those repos aren't updated very frequently anyway
> (how come?)
>

Should be fixed in 2.6.35 final, 29508eb66bfacdef324d2199eeaea31e0cdfaa29
drm/radeon/kms: drop taking lock around crtc lookup.

Generally regression fixes go via the drm-fixes tree, the other trees
get rebased/updated as patches arrive, we didn't really have much for
d-r-t this cycle.

Dave.