[waffle] [PATCH] utils/wflinfo: allow requesting a core profile without a version

Chad Versace chad.versace at linux.intel.com
Fri Mar 7 17:24:46 PST 2014

Thanks Jordan, both patches are committed to master now.

On Sat, Mar 01, 2014 at 09:05:07PM -0800, Jordan Justen wrote:
> On Fri, Feb 7, 2014 at 10:12 AM, Chad Versace
> <chad.versace at linux.intel.com> wrote:
> > On Mon, Jan 27, 2014 at 02:24:34PM -0800, Jordan Justen wrote:
> >> Previously, this command would fail:
> >> wflinfo --platform=glx --api=gl --profile=core
> >> Unless the --version parameter was also added.
> >>
> >> Now, if --version is not specified, and we are trying to
> >> create an OpenGL CORE profile, then wflinfo will try a
> >> set of known OpenGL CORE profile versions and will print
> >> information for the highest version profile created.
> >
> > This makes a lot of sense. It would be nice to follow up with another
> > patch that does the same for compatibility profile.
> --profile=compat? (Since, you don't need a version with --profile=none.)
> I started looking into this. I found this strange behavior on intel
> mesa (Haswell):
> $ wflinfo -p glx -a gl --profile=compat -V 3.2
> Waffle error: 0x0 WAFFLE_NO_ERROR
> Maybe a wflinfo bug?
> $ wflinfo -p gbm -a gl --profile=compat -V 3.2
> Waffle platform: gbm
> Waffle api: gl
> OpenGL vendor string: Intel Open Source Technology Center
> OpenGL renderer string: Mesa DRI Intel(R) Haswell
> OpenGL version string: 3.3 (Core Profile) Mesa 10.2.0-devel (git-c97763c)
> OpenGL context flags: 0x0
> This should fail to create a context, right? And, obviously, it
> shouldn't create a core profile, right?!

I committed two wflinfo bug fixes with your series. Did either of the
bugfix patches fix this bug?

> Regarding --profile=core and GL 3.1, I looked at it a little, but I
> did not address it yet.

Ok, no worry.


More information about the waffle mailing list