As i965 support drawbuffers and support 4 other buffers, the call glGetIntegerv(GL_AUX_BUFFERS, &nAuxBufs) should return 4, but now it is zero. (please refer to opengl spec2.1 Page299 for this constant) And call glGetIntegerv(GL_MAX_DRAW_BUFFERS, &nMaxBufs); it return 4. If i965 driver supports 4 AUX buffer, the MAX_DRAW_BUFFERS should be 6(4 AUX buffers + double buffers). (refer to openGL spec2.1 Page 216, the last of second paragraph). You can use attachment #13391 [details] to reproduce this bug.
Mesa core bug, reassigned. With soft rendering, glGetIntegerv(GL_AUX_BUFFERS, &nAuxBufs) also return 0. Should be 4 as mesa implemented.
With glxinfo do you see 4 in the "ax bf" column? The GL_AUX_BUFFERS query is just returning the value found in the visual info record. If you're seeing 0, the code that sets up the GLX visuals probably needs fixing. As for GL_MAX_DRAW_BUFFERS, I think it's possible for this value to be less than 2 + numAuxBuffers. I believe it advertises the number of color outputs supported by the fragment shader, not the number of possible drawing surfaces. You can set ctx->Const.MaxDrawBuffers in the driver to whatever is appropriate. Though, you may have to increase MAX_DRAW_BUFFERS in config.h too...
(In reply to comment #2) > With glxinfo do you see 4 in the "ax bf" column? The GL_AUX_BUFFERS query is > just returning the value found in the visual info record. If you're seeing 0, > the code that sets up the GLX visuals probably needs fixing. The glxinfo tells 0 in the "ax bf" column. GLX code needs fixing.
This issue has gone
verified on GM45 against: Libdrm: (master)00fae87f96e1fc5198311feec81866bf9c53d0e1 Mesa: (master)9f6ec50f8c79283583eeebdebd16bf7dcd134816 Xserver: (master)7f027d9dc0146e229802aeac342ea2dbab63264a Xf86_video_intel: (master)b8e360bf2b77d28559d15a7c0f9c766848eb6ced Kernel: (for-linus)07f4f3e8a24138ca2f3650723d670df25687cd05
Mass version move, cvs -> git
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.