On Fri, Feb 15, 2019 at 6:16 PM Helen Koike wrote:
>
>
>
> On 2/15/19 2:45 PM, Daniel Vetter wrote:
> > On Fri, Feb 15, 2019 at 10:25:03AM -0200, Helen Koike wrote:
> >> Hello,
> >>
> >> The legacy_cursor_update flag in the drm_atomic_state struct was being
> >> used to track if the update was asy
On 2/15/19 2:45 PM, Daniel Vetter wrote:
> On Fri, Feb 15, 2019 at 10:25:03AM -0200, Helen Koike wrote:
>> Hello,
>>
>> The legacy_cursor_update flag in the drm_atomic_state struct was being
>> used to track if the update was asyncronous or not for the cursor plane.
>> Which is really similar to
On Fri, Feb 15, 2019 at 10:25:03AM -0200, Helen Koike wrote:
> Hello,
>
> The legacy_cursor_update flag in the drm_atomic_state struct was being
> used to track if the update was asyncronous or not for the cursor plane.
> Which is really similar to what the async_update flag do, so I was
> trying
Hello,
The legacy_cursor_update flag in the drm_atomic_state struct was being
used to track if the update was asyncronous or not for the cursor plane.
Which is really similar to what the async_update flag do, so I was
trying to get rid of the legacy_cursor_update flag (just for cleanup).
So I did
