On 10/08/2012 03:40 PM, Kenneth Graunke wrote:
On 10/08/2012 03:21 PM, Chad Versace wrote:
The mesa commit 7dc0be8 changed the EGLConfig ID's for the Intel driver,
and piglit's GTF integration hardcodes the EGLConfig ID. (Apparently,
this implies that piglit's GTF integration only works the
On 10/09/2012 07:57 AM, Chad Versace wrote:
On 10/08/2012 03:40 PM, Kenneth Graunke wrote:
On 10/08/2012 03:21 PM, Chad Versace wrote:
The mesa commit 7dc0be8 changed the EGLConfig ID's for the Intel driver,
and piglit's GTF integration hardcodes the EGLConfig ID. (Apparently,
this implies
On 10/09/2012 09:01 AM, Kenneth Graunke wrote:
On 10/09/2012 07:57 AM, Chad Versace wrote:
On 10/08/2012 03:40 PM, Kenneth Graunke wrote:
On 10/08/2012 03:21 PM, Chad Versace wrote:
The mesa commit 7dc0be8 changed the EGLConfig ID's for the Intel
driver,
and piglit's GTF integration hardcodes
The mesa commit 7dc0be8 changed the EGLConfig ID's for the Intel driver,
and piglit's GTF integration hardcodes the EGLConfig ID. (Apparently,
this implies that piglit's GTF integration only works the Intel driver...
hmm).
The old -id=10 and new -id=7 should be the same underlying DRIConfig.
On 10/08/2012 03:21 PM, Chad Versace wrote:
The mesa commit 7dc0be8 changed the EGLConfig ID's for the Intel driver,
and piglit's GTF integration hardcodes the EGLConfig ID. (Apparently,
this implies that piglit's GTF integration only works the Intel driver...
hmm).
Most people don't have a
