On Thu, Oct 20, 2016 at 11:44:46AM +0100, Emil Velikov wrote:
> On 20 October 2016 at 05:35, Jonathan Gray wrote:
> > On Sat, Oct 15, 2016 at 01:32:02PM +0100, Emil Velikov wrote:
> >> On Saturday, 15 October 2016, Jonathan Gray wrote:
> >>
> >> > On Tue, Oct 11, 2016 at 07:31:46PM +0100, Emil Ve
On 20 October 2016 at 05:35, Jonathan Gray wrote:
> On Sat, Oct 15, 2016 at 01:32:02PM +0100, Emil Velikov wrote:
>> On Saturday, 15 October 2016, Jonathan Gray wrote:
>>
>> > On Tue, Oct 11, 2016 at 07:31:46PM +0100, Emil Velikov wrote:
>> > > From: Emil Velikov >
>> > >
>> > > Currently mesa ha
On Sat, Oct 15, 2016 at 01:32:02PM +0100, Emil Velikov wrote:
> On Saturday, 15 October 2016, Jonathan Gray wrote:
>
> > On Tue, Oct 11, 2016 at 07:31:46PM +0100, Emil Velikov wrote:
> > > From: Emil Velikov >
> > >
> > > Currently mesa has three code paths in the loader - libudev, manual
> > > s
On 11.10.2016 20:31, Emil Velikov wrote:
From: Emil Velikov
Currently mesa has three code paths in the loader - libudev, manual
sysfs and drm ioctl one.
Considering the issues we had with libudev - strip those down in favour
of the libdrm drm device API. The latter can be implemented in any wa
On Saturday, 15 October 2016, Jonathan Gray wrote:
> On Tue, Oct 11, 2016 at 07:31:46PM +0100, Emil Velikov wrote:
> > From: Emil Velikov >
> >
> > Currently mesa has three code paths in the loader - libudev, manual
> > sysfs and drm ioctl one.
> >
> > Considering the issues we had with libudev -
On Tue, Oct 11, 2016 at 07:31:46PM +0100, Emil Velikov wrote:
> From: Emil Velikov
>
> Currently mesa has three code paths in the loader - libudev, manual
> sysfs and drm ioctl one.
>
> Considering the issues we had with libudev - strip those down in favour
> of the libdrm drm device API. The la