diff options
| author | Emil Velikov <[email protected]> | 2014-02-21 22:52:46 +0000 |
|---|---|---|
| committer | Emil Velikov <[email protected]> | 2014-02-21 22:52:46 +0000 |
| commit | 68bc1e2025db5bfbfdd77c5f3b47a4ac2db8fd8d (patch) | |
| tree | 616846c3ec906f3f6ae282aa23e5c386f6beec1e /docs/specs/MESA_query_renderer.spec | |
| parent | 0432aa064bf5d4d0ad8fc3c4d648b8feb238ddfa (diff) | |
specs: MESA_query_renderer.spec resolve a couple of typos
Cc: Ian Romanick <[email protected]>
Signed-off-by: Emil Velikov <[email protected]>
Reviewed-by: Ian Romanick <[email protected]>
Diffstat (limited to 'docs/specs/MESA_query_renderer.spec')
| -rw-r--r-- | docs/specs/MESA_query_renderer.spec | 11 |
1 files changed, 8 insertions, 3 deletions
diff --git a/docs/specs/MESA_query_renderer.spec b/docs/specs/MESA_query_renderer.spec index e5e2a524247..dd45e02ba50 100644 --- a/docs/specs/MESA_query_renderer.spec +++ b/docs/specs/MESA_query_renderer.spec @@ -20,7 +20,7 @@ Status Version - Version 7, 7-November-2013 + Version 8, 14-February-2014 Number @@ -211,7 +211,7 @@ Additions to the GLX 1.4 Specification The attribute name GLX_RENDERER_ID_MESA specified the index of the render against which the context should be created. The default value of - GLX_RENDER_ID_MESA is 0. + GLX_RENDERER_ID_MESA is 0. [Add to list of errors for glXCreateContextAttribsARB in section section @@ -373,7 +373,7 @@ Issues should make every attempt to return as much information as is possible. For example, if the implementation is running on a non-PCI SoC with a Qualcomm GPU, GLX_RENDERER_VENDOR_ID_MESA should return - 0x168C, but GLX_RENDERER_DEVICE_ID_MESA will return 0x0000. + 0x5143, but GLX_RENDERER_DEVICE_ID_MESA will return 0xFFFFFFFF. Revision History @@ -403,3 +403,8 @@ Revision History Version 7, 2013/11/07 - Fix a couple more typos. Add issue #17 regarding the PCI queries on systems that don't have PCI. + + Version 8, 2014/02/14 - Fix a couple typos. GLX_RENDER_ID_MESA should + read GLX_RENDERER_ID_MESA. The VENDOR/DEVICE_ID + example given in issue #17 should be 0x5143 and + 0xFFFFFFFF respectively. |