Re: [waffle] [wflinfo] [RFC] platform-specific info from wflinfo

2015-04-22 Thread Dylan Baker
> > I think I'd prefer to not convert wflinfo to python. > > I also hesitate to convert wflinfo to python. After we push all the > complexity of wflinfo.c into a library call, then wflinfo.c will largely > consist of argparsing and a minimal json parser. wflinfo.c will then be > so small that I do

Re: [waffle] [wflinfo] [RFC] platform-specific info from wflinfo

2015-04-22 Thread Chad Versace
On Fri 10 Apr 2015, Jordan Justen wrote: > On 2015-04-10 07:05:32, Frank Henigman wrote: > > Sorry I let this thread get stale. I apologise too for letting it go stale. > > > On 02/20/2015 01:49 PM, Jordan Justen wrote: > > >> My idea was just to define a one-time API that left presentation of >

Re: [waffle] [wflinfo] [RFC] platform-specific info from wflinfo

2015-02-26 Thread Chad Versace
On 02/20/2015 01:49 PM, Jordan Justen wrote: > On 2015-02-20 12:58:07, Chad Versace wrote: >> On 02/17/2015 11:30 PM, Jordan Justen wrote: >> For the sake of apps who want to dump the info to a log file or to >> the console and get on >> with their lives, I think the default output format should

Re: [waffle] [wflinfo] [RFC] platform-specific info from wflinfo

2015-02-20 Thread Jordan Justen
On 2015-02-20 12:58:07, Chad Versace wrote: > On 02/17/2015 11:30 PM, Jordan Justen wrote: > > On 2015-02-10 12:09:05, Chad Versace wrote: > >> I prefer "core" too. Not for the sake of less code, but because I like > >> the idea of it being available as core API. > > > > This surprised me a bit. I

Re: [waffle] [wflinfo] [RFC] platform-specific info from wflinfo

2015-02-20 Thread Chad Versace
On 02/17/2015 11:30 PM, Jordan Justen wrote: > On 2015-02-10 12:09:05, Chad Versace wrote: >>> On Sun, Feb 08, 2015 at 07:50:15PM -0500, Frank Henigman wrote: I'd like to extend wflinfo so it can print platform-specific information and eventually be able to replace glxinfo, eglinfo and th

Re: [waffle] [wflinfo] [RFC] platform-specific info from wflinfo

2015-02-19 Thread Dylan Baker
I don't know how I missed this, I don't care if the output is character for character with glxinfo, as long as it conveys the same information. On Wed, Feb 11, 2015 at 06:01:26PM -0800, Chad Versace wrote: > On 02/10/2015 01:20 PM, Frank Henigman wrote: > > On Tue, Feb 10, 2015 at 4:08 PM, Frank

Re: [waffle] [wflinfo] [RFC] platform-specific info from wflinfo

2015-02-17 Thread Jordan Justen
On 2015-02-10 12:09:05, Chad Versace wrote: > > On Sun, Feb 08, 2015 at 07:50:15PM -0500, Frank Henigman wrote: > >> I'd like to extend wflinfo so it can print platform-specific > >> information and eventually be able to replace glxinfo, eglinfo and the > >> like (I only know what's on linux). The

Re: [waffle] [wflinfo] [RFC] platform-specific info from wflinfo

2015-02-17 Thread Emil Velikov
On 17/02/15 19:18, Chad Versace wrote: > On 02/14/2015 09:22 AM, Emil Velikov wrote: >> On 13 February 2015 at 02:22, Frank Henigman wrote: >>> On Thu, Feb 12, 2015 at 5:44 AM, Emil Velikov >>> wrote: On 12 February 2015 at 02:01, Chad Versace wrote: > On 02/10/2015 01:20 PM, Frank Hen

Re: [waffle] [wflinfo] [RFC] platform-specific info from wflinfo

2015-02-17 Thread Chad Versace
On 02/14/2015 09:22 AM, Emil Velikov wrote: > On 13 February 2015 at 02:22, Frank Henigman wrote: >> On Thu, Feb 12, 2015 at 5:44 AM, Emil Velikov >> wrote: >>> On 12 February 2015 at 02:01, Chad Versace wrote: On 02/10/2015 01:20 PM, Frank Henigman wrote: > On Tue, Feb 10, 2015 at 4:0

Re: [waffle] [wflinfo] [RFC] platform-specific info from wflinfo

2015-02-14 Thread Emil Velikov
On 13 February 2015 at 02:22, Frank Henigman wrote: > On Thu, Feb 12, 2015 at 5:44 AM, Emil Velikov > wrote: >> On 12 February 2015 at 02:01, Chad Versace wrote: >>> On 02/10/2015 01:20 PM, Frank Henigman wrote: On Tue, Feb 10, 2015 at 4:08 PM, Frank Henigman wrote: >>> Looks l

Re: [waffle] [wflinfo] [RFC] platform-specific info from wflinfo

2015-02-12 Thread Frank Henigman
On Thu, Feb 12, 2015 at 5:44 AM, Emil Velikov wrote: > On 12 February 2015 at 02:01, Chad Versace wrote: >> On 02/10/2015 01:20 PM, Frank Henigman wrote: >>> On Tue, Feb 10, 2015 at 4:08 PM, Frank Henigman >>> wrote: >> >>> Looks like Issue #3 is the format of the information. I thought it >>>

Re: [waffle] [wflinfo] [RFC] platform-specific info from wflinfo

2015-02-12 Thread Emil Velikov
On 12 February 2015 at 02:01, Chad Versace wrote: > On 02/10/2015 01:20 PM, Frank Henigman wrote: >> On Tue, Feb 10, 2015 at 4:08 PM, Frank Henigman >> wrote: > >> Looks like Issue #3 is the format of the information. I thought it >> was given we should duplicate existing glxinfo/eglinfo/etc as

Re: [waffle] [wflinfo] [RFC] platform-specific info from wflinfo

2015-02-11 Thread Jordan Justen
On 2015-02-11 18:01:26, Chad Versace wrote: > On 02/10/2015 01:20 PM, Frank Henigman wrote: > > On Tue, Feb 10, 2015 at 4:08 PM, Frank Henigman > > wrote: > > > Looks like Issue #3 is the format of the information. I thought it > > was given we should duplicate existing glxinfo/eglinfo/etc as c

Re: [waffle] [wflinfo] [RFC] platform-specific info from wflinfo

2015-02-11 Thread Chad Versace
On 02/10/2015 01:20 PM, Frank Henigman wrote: > On Tue, Feb 10, 2015 at 4:08 PM, Frank Henigman wrote: > Looks like Issue #3 is the format of the information. I thought it > was given we should duplicate existing glxinfo/eglinfo/etc as closely > as possible, in order to be a drop-in replacement,

Re: [waffle] [wflinfo] [RFC] platform-specific info from wflinfo

2015-02-10 Thread Chad Versace
On 02/10/2015 01:08 PM, Frank Henigman wrote: > On Tue, Feb 10, 2015 at 3:09 PM, Chad Versace wrote: >> I see two significant design decisions that need to be made: >> >> Issue #1: Should Waffle provide a query mechanism for the native >> platform info? Or should it just dump the info as a we

Re: [waffle] [wflinfo] [RFC] platform-specific info from wflinfo

2015-02-10 Thread Frank Henigman
On Tue, Feb 10, 2015 at 4:08 PM, Frank Henigman wrote: > On Tue, Feb 10, 2015 at 3:09 PM, Chad Versace wrote: >> On 02/10/2015 10:31 AM, Dylan Baker wrote: >>> I like this idea, it would be convenient for piglit to be able to assume >>> waffle info can provide all of the information we currently

Re: [waffle] [wflinfo] [RFC] platform-specific info from wflinfo

2015-02-10 Thread Frank Henigman
On Tue, Feb 10, 2015 at 3:09 PM, Chad Versace wrote: > On 02/10/2015 10:31 AM, Dylan Baker wrote: >> I like this idea, it would be convenient for piglit to be able to assume >> waffle info can provide all of the information we currently call out to >> multiple binaries for. > > Yes, Piglit wants t

Re: [waffle] [wflinfo] [RFC] platform-specific info from wflinfo

2015-02-10 Thread Chad Versace
On 02/08/2015 04:50 PM, Frank Henigman wrote: > I'd like to extend wflinfo so it can print platform-specific > information and eventually be able to replace glxinfo, eglinfo and the > like (I only know what's on linux). There would be a new flag to > request the platform-specific output in additio

Re: [waffle] [wflinfo] [RFC] platform-specific info from wflinfo

2015-02-10 Thread Chad Versace
On 02/10/2015 10:31 AM, Dylan Baker wrote: > I like this idea, it would be convenient for piglit to be able to assume > waffle info can provide all of the information we currently call out to > multiple binaries for. Yes, Piglit wants this. I imagine more users will begin using it too. > On Sun,

Re: [waffle] [wflinfo] [RFC] platform-specific info from wflinfo

2015-02-10 Thread Dylan Baker
I like this idea, it would be convenient for piglit to be able to assume waffle info can provide all of the information we currently call out to multiple binaries for. On Sun, Feb 08, 2015 at 07:50:15PM -0500, Frank Henigman wrote: > I'd like to extend wflinfo so it can print platform-specific > i

[waffle] [wflinfo] [RFC] platform-specific info from wflinfo

2015-02-08 Thread Frank Henigman
I'd like to extend wflinfo so it can print platform-specific information and eventually be able to replace glxinfo, eglinfo and the like (I only know what's on linux). There would be a new flag to request the platform-specific output in addition to the existing output. For example on glx you'd se