On 03/08/2018 06:00 PM, Michel Dänzer wrote:
On 2018-03-07 10:33 AM, Mario Kleiner wrote:
On 03/07/2018 09:50 AM, Michel Dänzer wrote:
On 2018-03-07 04:45 AM, Mario Kleiner wrote:
On 03/05/2018 10:56 PM, Alex Deucher wrote:
On Mon, Mar 5, 2018 at 12:44 PM, Michel Dänzer
wrote:
From: Miche
On 2018-03-07 10:33 AM, Mario Kleiner wrote:
> On 03/07/2018 09:50 AM, Michel Dänzer wrote:
>> On 2018-03-07 04:45 AM, Mario Kleiner wrote:
>>> On 03/05/2018 10:56 PM, Alex Deucher wrote:
On Mon, Mar 5, 2018 at 12:44 PM, Michel Dänzer
wrote:
> From: Michel Dänzer
>
> Since x
On 03/07/2018 09:50 AM, Michel Dänzer wrote:
On 2018-03-07 04:45 AM, Mario Kleiner wrote:
On 03/05/2018 10:56 PM, Alex Deucher wrote:
On Mon, Mar 5, 2018 at 12:44 PM, Michel Dänzer
wrote:
From: Michel Dänzer
Since xf86CursorCloseScreen runs after RADEONCloseScreen_KMS,
PointPriv->spriteFunc
On 2018-03-07 04:45 AM, Mario Kleiner wrote:
> On 03/05/2018 10:56 PM, Alex Deucher wrote:
>> On Mon, Mar 5, 2018 at 12:44 PM, Michel Dänzer
>> wrote:
>>> From: Michel Dänzer
>>>
>>> Since xf86CursorCloseScreen runs after RADEONCloseScreen_KMS,
>>> PointPriv->spriteFuncs doesn't point to the same
On 03/05/2018 10:56 PM, Alex Deucher wrote:
On Mon, Mar 5, 2018 at 12:44 PM, Michel Dänzer wrote:
From: Michel Dänzer
Since xf86CursorCloseScreen runs after RADEONCloseScreen_KMS,
PointPriv->spriteFuncs doesn't point to the same struct in the latter as
in RADEONCursorInit_KMS. So we were rest
On Mon, Mar 5, 2018 at 12:44 PM, Michel Dänzer wrote:
> From: Michel Dänzer
>
> Since xf86CursorCloseScreen runs after RADEONCloseScreen_KMS,
> PointPriv->spriteFuncs doesn't point to the same struct in the latter as
> in RADEONCursorInit_KMS. So we were restoring info->Set/MoveCursor to
> the wr