Hi, Emil,
On 10/04/2018 04:12 PM, Emil Velikov wrote:
> On Sun, 30 Sep 2018 at 18:31, Thomas Hellstrom wrote:
>> Hi, Emil,
>>
>> On 09/05/2018 03:53 PM, Emil Velikov wrote:
>>> On 5 September 2018 at 14:20, Thomas Hellstrom
>>> wrote:
>>>
> In that case, please give me 24h to do a libdrm re
On Sun, 30 Sep 2018 at 18:31, Thomas Hellstrom wrote:
>
> Hi, Emil,
>
> On 09/05/2018 03:53 PM, Emil Velikov wrote:
> > On 5 September 2018 at 14:20, Thomas Hellstrom
> > wrote:
> >
> >>> In that case, please give me 24h to do a libdrm release before pushing.
> >>> I had to push some workarounds
Ping?
On 09/30/2018 07:31 PM, Thomas Hellstrom wrote:
> Hi, Emil,
>
> On 09/05/2018 03:53 PM, Emil Velikov wrote:
>> On 5 September 2018 at 14:20, Thomas Hellstrom
>> wrote:
>>
In that case, please give me 24h to do a libdrm release before
pushing.
I had to push some workarounds
Hi, Emil,
On 09/05/2018 03:53 PM, Emil Velikov wrote:
On 5 September 2018 at 14:20, Thomas Hellstrom wrote:
In that case, please give me 24h to do a libdrm release before pushing.
I had to push some workarounds for the sandboxing mentioned earlier :-\
Thanks
Emil
Ouch, I just pushed the pa
On 5 September 2018 at 14:20, Thomas Hellstrom wrote:
>> In that case, please give me 24h to do a libdrm release before pushing.
>> I had to push some workarounds for the sandboxing mentioned earlier :-\
>>
>> Thanks
>> Emil
>
>
> Ouch, I just pushed the patch, but feel free to cut the release ju
On 09/05/2018 03:07 PM, Emil Velikov wrote:
On 5 September 2018 at 11:10, Thomas Hellstrom wrote:
Hi, Emil,
On 09/05/2018 11:33 AM, Emil Velikov wrote:
On 4 September 2018 at 23:33, Dave Airlie wrote:
On Tue, 4 Sep 2018 at 03:00, Thomas Hellstrom
wrote:
On 09/03/2018 06:33 PM, Daniel Vet
On 5 September 2018 at 11:10, Thomas Hellstrom wrote:
> Hi, Emil,
>
>
> On 09/05/2018 11:33 AM, Emil Velikov wrote:
>>
>> On 4 September 2018 at 23:33, Dave Airlie wrote:
>>>
>>> On Tue, 4 Sep 2018 at 03:00, Thomas Hellstrom
>>> wrote:
On 09/03/2018 06:33 PM, Daniel Vetter wrote:
>
Hi, Emil,
On 09/05/2018 11:33 AM, Emil Velikov wrote:
On 4 September 2018 at 23:33, Dave Airlie wrote:
On Tue, 4 Sep 2018 at 03:00, Thomas Hellstrom wrote:
On 09/03/2018 06:33 PM, Daniel Vetter wrote:
On Mon, Sep 03, 2018 at 11:16:29AM +0200, Thomas Hellstrom wrote:
On 08/31/2018 05:30 PM,
On 4 September 2018 at 23:33, Dave Airlie wrote:
> On Tue, 4 Sep 2018 at 03:00, Thomas Hellstrom wrote:
>>
>> On 09/03/2018 06:33 PM, Daniel Vetter wrote:
>> > On Mon, Sep 03, 2018 at 11:16:29AM +0200, Thomas Hellstrom wrote:
>> >> On 08/31/2018 05:30 PM, Thomas Hellstrom wrote:
>> >>> On 08/31/2
On Tue, 4 Sep 2018 at 03:00, Thomas Hellstrom wrote:
>
> On 09/03/2018 06:33 PM, Daniel Vetter wrote:
> > On Mon, Sep 03, 2018 at 11:16:29AM +0200, Thomas Hellstrom wrote:
> >> On 08/31/2018 05:30 PM, Thomas Hellstrom wrote:
> >>> On 08/31/2018 05:27 PM, Emil Velikov wrote:
> On 31 August 201
On 09/03/2018 06:33 PM, Daniel Vetter wrote:
On Mon, Sep 03, 2018 at 11:16:29AM +0200, Thomas Hellstrom wrote:
On 08/31/2018 05:30 PM, Thomas Hellstrom wrote:
On 08/31/2018 05:27 PM, Emil Velikov wrote:
On 31 August 2018 at 15:38, Michel Dänzer wrote:
[ Adding the amd-gfx list ]
On 2018-08-
On Mon, Sep 03, 2018 at 11:16:29AM +0200, Thomas Hellstrom wrote:
> On 08/31/2018 05:30 PM, Thomas Hellstrom wrote:
> > On 08/31/2018 05:27 PM, Emil Velikov wrote:
> > > On 31 August 2018 at 15:38, Michel Dänzer wrote:
> > > > [ Adding the amd-gfx list ]
> > > >
> > > > On 2018-08-31 3:05 p.m., T
On 08/31/2018 05:30 PM, Thomas Hellstrom wrote:
On 08/31/2018 05:27 PM, Emil Velikov wrote:
On 31 August 2018 at 15:38, Michel Dänzer wrote:
[ Adding the amd-gfx list ]
On 2018-08-31 3:05 p.m., Thomas Hellstrom wrote:
On 08/31/2018 02:30 PM, Emil Velikov wrote:
On 31 August 2018 at 12:54, T
On Fri, Aug 31, 2018 at 11:32 AM Christian König
wrote:
>
> Am 31.08.2018 um 17:27 schrieb Emil Velikov:
> > On 31 August 2018 at 15:38, Michel Dänzer wrote:
> >> [ Adding the amd-gfx list ]
> >>
> >> On 2018-08-31 3:05 p.m., Thomas Hellstrom wrote:
> >>> On 08/31/2018 02:30 PM, Emil Velikov wrot
On 08/31/2018 05:27 PM, Emil Velikov wrote:
On 31 August 2018 at 15:38, Michel Dänzer wrote:
[ Adding the amd-gfx list ]
On 2018-08-31 3:05 p.m., Thomas Hellstrom wrote:
On 08/31/2018 02:30 PM, Emil Velikov wrote:
On 31 August 2018 at 12:54, Thomas Hellstrom
wrote:
To determine whether a d
Am 31.08.2018 um 17:27 schrieb Emil Velikov:
On 31 August 2018 at 15:38, Michel Dänzer wrote:
[ Adding the amd-gfx list ]
On 2018-08-31 3:05 p.m., Thomas Hellstrom wrote:
On 08/31/2018 02:30 PM, Emil Velikov wrote:
On 31 August 2018 at 12:54, Thomas Hellstrom
wrote:
To determine whether a
On 31 August 2018 at 15:38, Michel Dänzer wrote:
>
> [ Adding the amd-gfx list ]
>
> On 2018-08-31 3:05 p.m., Thomas Hellstrom wrote:
>> On 08/31/2018 02:30 PM, Emil Velikov wrote:
>>> On 31 August 2018 at 12:54, Thomas Hellstrom
>>> wrote:
To determine whether a device node is a drm device
On 08/31/2018 04:49 PM, Michel Dänzer wrote:
On 2018-08-31 4:46 p.m., Thomas Hellstrom wrote:
On 08/31/2018 04:38 PM, Michel Dänzer wrote:
[ Adding the amd-gfx list ]
On 2018-08-31 3:05 p.m., Thomas Hellstrom wrote:
On 08/31/2018 02:30 PM, Emil Velikov wrote:
On 31 August 2018 at 12:54, Thom
On 2018-08-31 4:46 p.m., Thomas Hellstrom wrote:
> On 08/31/2018 04:38 PM, Michel Dänzer wrote:
>> [ Adding the amd-gfx list ]
>>
>> On 2018-08-31 3:05 p.m., Thomas Hellstrom wrote:
>>> On 08/31/2018 02:30 PM, Emil Velikov wrote:
On 31 August 2018 at 12:54, Thomas Hellstrom
wrote:
>
On 08/31/2018 04:38 PM, Michel Dänzer wrote:
[ Adding the amd-gfx list ]
On 2018-08-31 3:05 p.m., Thomas Hellstrom wrote:
On 08/31/2018 02:30 PM, Emil Velikov wrote:
On 31 August 2018 at 12:54, Thomas Hellstrom
wrote:
To determine whether a device node is a drm device node or not, the code
c
[ Adding the amd-gfx list ]
On 2018-08-31 3:05 p.m., Thomas Hellstrom wrote:
> On 08/31/2018 02:30 PM, Emil Velikov wrote:
>> On 31 August 2018 at 12:54, Thomas Hellstrom
>> wrote:
>>> To determine whether a device node is a drm device node or not, the code
>>> currently compares the node's majo
Hi, Emil
On 08/31/2018 02:30 PM, Emil Velikov wrote:
Hi Thomas,
On 31 August 2018 at 12:54, Thomas Hellstrom wrote:
To determine whether a device node is a drm device node or not, the code
currently compares the node's major number to the static drm major device
number.
This breaks the standa
Hi Thomas,
On 31 August 2018 at 12:54, Thomas Hellstrom wrote:
> To determine whether a device node is a drm device node or not, the code
> currently compares the node's major number to the static drm major device
> number.
>
> This breaks the standalone vmwgfx driver on XWayland dri clients,
> h
On Friday, 2018-08-31 13:54:19 +0200, Thomas Hellstrom wrote:
> To determine whether a device node is a drm device node or not, the code
> currently compares the node's major number to the static drm major device
> number.
>
> This breaks the standalone vmwgfx driver on XWayland dri clients,
> htt
To determine whether a device node is a drm device node or not, the code
currently compares the node's major number to the static drm major device
number.
This breaks the standalone vmwgfx driver on XWayland dri clients,
https://cgit.freedesktop.org/mesa/vmwgfx
and any future attempt to introduce
25 matches
Mail list logo
