Re: [Mesa-dev] [RFC 00/10] Let us welcome EGLDevice

2018-09-06 Thread Mathias Fröhlich
Hi Emil, On Tuesday, 4 September 2018 22:16:18 CEST Emil Velikov wrote: > Aaand it out, yet I forgot to CC you :-\ Never mind. I have seen that but did not find the time so far to test and review. But that's on my list. best Mathias ___ mesa-dev

Re: [Mesa-dev] [RFC 00/10] Let us welcome EGLDevice

2018-09-04 Thread Emil Velikov
On 4 September 2018 at 16:21, Mathias Fröhlich wrote: > Hi Emil, > > On Tuesday, 4 September 2018 16:21:49 CEST you wrote: >> > ssh different-machine.somewhere >> > >> > Then you will see that you are not added to the card0 acl as you are not >> > logged to any console. >> >> Ouch, I should have

Re: [Mesa-dev] [RFC 00/10] Let us welcome EGLDevice

2018-09-04 Thread Mathias Fröhlich
Hi Emil, On Tuesday, 4 September 2018 16:21:49 CEST you wrote: > > ssh different-machine.somewhere > > > > Then you will see that you are not added to the card0 acl as you are not > > logged to any console. > > Ouch, I should have noticed the "rw" for "other" of your render node. > Looking at a

Re: [Mesa-dev] [RFC 00/10] Let us welcome EGLDevice

2018-09-04 Thread Emil Velikov
HI Mathias, On 30 August 2018 at 15:11, Mathias Fröhlich wrote: >> > >> > It's just the file permissions: >> > >> > $ ls -l /dev/dri/{card*,render*} >> > crw-rw+ 1 root video 226, 0 Aug 30 08:28 /dev/dri/card0 >> > crw-rw-rw- 1 root render 226, 128 Aug 30 08:28 /dev/dri/renderD128 >> >

Re: [Mesa-dev] [RFC 00/10] Let us welcome EGLDevice

2018-08-30 Thread Mathias Fröhlich
Hi Emil, > Correct. We had a number of bugs (one of which breaking MT apps) that > makes me cautious. Working with environment variables basically is often asking for problems. The thread race condition ones being the most prominent. To overwrite something - especially for debugging - its ok to

Re: [Mesa-dev] [RFC 00/10] Let us welcome EGLDevice

2018-08-30 Thread Emil Velikov
On 30 August 2018 at 10:54, Mathias Fröhlich wrote: > On Tuesday, 28 August 2018 16:22:33 CEST Emil Velikov wrote: >> > From a higher point of view the approach looks good. >> > >> > To sum up, you basically associate an _EGLDevice with each _EGLDisplay >> > where the _EGLDevice only contains the

Re: [Mesa-dev] [RFC 00/10] Let us welcome EGLDevice

2018-08-30 Thread Mathias Fröhlich
On Tuesday, 28 August 2018 16:22:33 CEST Emil Velikov wrote: > > From a higher point of view the approach looks good. > > > > To sum up, you basically associate an _EGLDevice with each _EGLDisplay > > where the _EGLDevice only contains the meta information where to > > find the device and the

Re: [Mesa-dev] [RFC 00/10] Let us welcome EGLDevice

2018-08-28 Thread Emil Velikov
Thanks Mathias, On 28 August 2018 at 08:31, Mathias Fröhlich wrote: > Hi Emil, > > On Friday, 3 August 2018 14:44:16 CEST Emil Velikov wrote: >> Hi all, >> >> This series implements the following extensions: >> - EGL_EXT_device_base >> - EGL_MESA_device_software >> - EGL_EXT_device_drm >> -

Re: [Mesa-dev] [RFC 00/10] Let us welcome EGLDevice

2018-08-28 Thread Mathias Fröhlich
Hi Emil, On Friday, 3 August 2018 14:44:16 CEST Emil Velikov wrote: > Hi all, > > This series implements the following extensions: > - EGL_EXT_device_base > - EGL_MESA_device_software > - EGL_EXT_device_drm > - EGL_platform_device > > As you know the APIs are used to enumerate, select and

[Mesa-dev] [RFC 00/10] Let us welcome EGLDevice

2018-08-03 Thread Emil Velikov
Hi all, This series implements the following extensions: - EGL_EXT_device_base - EGL_MESA_device_software - EGL_EXT_device_drm - EGL_platform_device As you know the APIs are used to enumerate, select and use EGLDevices. The second extension (proposed by Ajax) defines a 'software' device,