On 14/03/16 19:59, Kyle Brenneman wrote:
On 03/14/2016 11:43 AM, Martin Peres wrote:
On 14/03/16 19:16, Kyle Brenneman wrote:
On 03/11/2016 05:25 PM, Martin Peres wrote:
On 10/03/16 20:07, Adam Jackson wrote:
On Thu, 2016-03-10 at 10:53 -0700, Kyle Brenneman wrote:
On 03/10/2016 10:47 AM, M
On 03/14/2016 11:43 AM, Martin Peres wrote:
On 14/03/16 19:16, Kyle Brenneman wrote:
On 03/11/2016 05:25 PM, Martin Peres wrote:
On 10/03/16 20:07, Adam Jackson wrote:
On Thu, 2016-03-10 at 10:53 -0700, Kyle Brenneman wrote:
On 03/10/2016 10:47 AM, Martin Peres wrote:
That could be a hack
On 14/03/16 19:16, Kyle Brenneman wrote:
On 03/11/2016 05:25 PM, Martin Peres wrote:
On 10/03/16 20:07, Adam Jackson wrote:
On Thu, 2016-03-10 at 10:53 -0700, Kyle Brenneman wrote:
On 03/10/2016 10:47 AM, Martin Peres wrote:
That could be a hacky way of handling the case where multiple 3D
On 03/11/2016 05:25 PM, Martin Peres wrote:
On 10/03/16 20:07, Adam Jackson wrote:
On Thu, 2016-03-10 at 10:53 -0700, Kyle Brenneman wrote:
On 03/10/2016 10:47 AM, Martin Peres wrote:
That could be a hacky way of handling the case where multiple 3D
drivers could be used to drive the same GP
On 10/03/16 20:07, Adam Jackson wrote:
On Thu, 2016-03-10 at 10:53 -0700, Kyle Brenneman wrote:
On 03/10/2016 10:47 AM, Martin Peres wrote:
That could be a hacky way of handling the case where multiple 3D
drivers could be used to drive the same GPU. This may be necessary in
the future if two
On Fri, 2016-03-11 at 11:12 -0700, Kyle Brenneman wrote:
> All right, here's an updated draft of the Issues section. How does it look?
>
> Issues
> 1) Should GLX_VENDOR_NAMES_EXT contain a single vendor name or a list of
> names?
>
> UNRESOLVED: Allow a list of names.
>
>
All right, here's an updated draft of the Issues section. How does it look?
Issues
1) Should GLX_VENDOR_NAMES_EXT contain a single vendor name or a
list of
names?
UNRESOLVED: Allow a list of names.
Allowing multiple names would allow for multiple client-side
driv
On Thu, 2016-03-10 at 10:53 -0700, Kyle Brenneman wrote:
> On 03/10/2016 10:47 AM, Martin Peres wrote:
> >
> > That could be a hacky way of handling the case where multiple 3D
> > drivers could be used to drive the same GPU. This may be necessary in
> > the future if two mesa drivers support the
On 03/10/2016 10:47 AM, Martin Peres wrote:
On 09/03/16 20:15, Kyle Brenneman wrote:
The current implementation of libglvnd uses a new X extension called
x11glvnd to look up a vendor name for each screen and to find a screen
number for a GLXDrawable.
But, Adam Jackson pointed out that a GLX ex
On 09/03/16 20:15, Kyle Brenneman wrote:
The current implementation of libglvnd uses a new X extension called
x11glvnd to look up a vendor name for each screen and to find a screen
number for a GLXDrawable.
But, Adam Jackson pointed out that a GLX extension could do the same job
more cleanly: Lo
On Thu, 2016-03-10 at 08:32 -0700, Kyle Brenneman wrote:
> > That could work, although I would expect "vendor-specific info" to
> > mean "random, arbitrary, and probably not machine-parsable". I'd be
> > hesitant to try to impose a structure on something that's never had
> > any structure befor
On 03/09/2016 12:53 PM, Kyle Brenneman wrote:
On 03/09/2016 12:21 PM, Adam Jackson wrote:
On Wed, 2016-03-09 at 11:15 -0700, Kyle Brenneman wrote:
The current implementation of libglvnd uses a new X extension called
x11glvnd to look up a vendor name for each screen and to find a screen
number
On 03/09/2016 12:21 PM, Adam Jackson wrote:
On Wed, 2016-03-09 at 11:15 -0700, Kyle Brenneman wrote:
The current implementation of libglvnd uses a new X extension called
x11glvnd to look up a vendor name for each screen and to find a screen
number for a GLXDrawable.
But, Adam Jackson pointed ou
On Wed, 2016-03-09 at 11:15 -0700, Kyle Brenneman wrote:
> The current implementation of libglvnd uses a new X extension called
> x11glvnd to look up a vendor name for each screen and to find a screen
> number for a GLXDrawable.
>
> But, Adam Jackson pointed out that a GLX extension could do the
The current implementation of libglvnd uses a new X extension called
x11glvnd to look up a vendor name for each screen and to find a screen
number for a GLXDrawable.
But, Adam Jackson pointed out that a GLX extension could do the same job
more cleanly: Looking up a vendor name is just querying
15 matches
Mail list logo
