Re: [Mesa3d-dev] [PATCH] gallium: add PIPE_CAP_QUADS_FOLLOW_FLATSHADE_FIRST_CONVENTION
On 12/19/2009 04:11 AM, Corbin Simpson wrote: NAK to this series. Keith hasn't responded, although I expect that he would also NAK this. I would much rather have quads just never respect flatshade_first as part of the spec, than jump through these weird param hoops. Should somebody be documenting the API? I keep on having these kinds of stupid edge questions come up; r300 apparently is the quirkiest hardware of that generation. ~ C. How about we kick out quads altogether ? Having to flip the first/last bit depending on *what's being drawn* is quirky. I realize nv50 don't follow the convention for quads (at least that's what the spec says), so I'm outnumbered, but I don't see the harm in following what OpenGL does here, i.e. just have the query. On Fri, Dec 18, 2009 at 2:15 AM, Christoph Bumiller e0425...@student.tuwien.ac.at wrote: Marek Olšák schrieb: Hi, GL_ARB_provoking_vertex states that quads are not required to abide the provoking vertex convention, and the actual hardware and/or driver behavior can be queried with GL_QUADS_FOLLOW_PROVOKING_VERTEX_CONVENTION. I'd like to add a new PIPE_CAP_* to query for this capability in Gallium, as it appears R3xx-R5xx hardware doesn't support the first vertex convention for quads and I'd like the driver to behave correctly. Fortunately, other primitive types are supported. I decided to use the name quads follow flatshade_first convention instead of provoking vertex convention because the actual state variable in pipe_rasterizer_state is called flatshade_first. The attached patch: - adds PIPE_CAP_QUADS_FOLLOW_FLATSHADE_FIRST_CONVENTION - adds the query in the Mesa state tracker - and updates softpipe and llvmpipe to return 1 when this cap is queried, and r300g to explicitly return 0 You can add a return 1 for nv50, too, in case you do push this patch. I just tested and for quads I can also make them use either the first or the last vertex's colour, i.e. flatshade convention is respected. Thanks, Christoph. Please review/push. Cheers. Marek -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
Re: [Mesa3d-dev] [PATCH] gallium: add PIPE_CAP_QUADS_FOLLOW_FLATSHADE_FIRST_CONVENTION
Keith Whitwell kei...@vmware.com writes: Ideally that would mean being able to produce a single patch or patch series that contains the changes to the headers *and* the changes to the spec, so th at all is being considered together. That means in turn having the spec in the git tree. Ideally we'd have an online version as well, in a wiki style. I'm interested in suggestions for how to make this happen. Ideally we *wouldn't* pollute the header files with so much text and markup that they become unreadable - ie. I don't really like the idea of doing the spec with doxygen - I'd prefer the headers to be human-readable. Thoughts? I'm partial to / been considering both asciidoc and sphinx in my own projects. http://www.methods.co.nz/asciidoc/ http://sphinx.pocoo.org/ Both are text-based formats that are intended to be readable `raw', but are processable into more presentable formats. The git documentation: http://www.kernel.org/pub/software/scm/git/docs/user-manual.html is done with asciidoc. Python documentation: http://docs.python.org/library/index.html is done with sphinx. -tom From: Corbin Simpson [mostawesomed...@gmail.com] Sent: Friday, December 18, 2009 7:11 PM To: Christoph Bumiller Cc: mesa3d-dev@lists.sourceforge.net Subject: Re: [Mesa3d-dev] [PATCH] gallium: add PIPE_CAP_QUADS_FOLLOW_FLATSHA DE_FIRST_CONVENTION NAK to this series. Keith hasn't responded, although I expect that he would also NAK this. I would much rather have quads just never respect flatshade_first as part of the spec, than jump through these weird param hoops. Should somebody be documenting the API? I keep on having these kinds of stupid edge questions come up; r300 apparently is the quirkiest hardware of that generation. ~ C. On Fri, Dec 18, 2009 at 2:15 AM, Christoph Bumiller e0425...@student.tuwien.ac.at wrote: Marek Olák schrieb: Hi, GL_ARB_provoking_vertex states that quads are not required to abide the provoking vertex convention, and the actual hardware and/or driver behavior can be queried with GL_QUADS_FOLLOW_PROVOKING_VERTEX_CONVENTION. I'd like to add a new PIPE_CAP_* to query for this capability in Gallium, as it appears R3xx-R5xx hardware doesn't support the first vertex convention for quads and I'd like the driver to behave correctly. Fortunately, other primitive types are supported. I decided to use the name quads follow flatshade_first convention instead of provoking vertex convention because the actual state variable in pipe_rasterizer_state is called flatshade_first. The attached patch: - adds PIPE_CAP_QUADS_FOLLOW_FLATSHADE_FIRST_CONVENTION - adds the query in the Mesa state tracker - and updates softpipe and llvmpipe to return 1 when this cap is queried, and r300g to explicitly return 0 You can add a return 1 for nv50, too, in case you do push this patch. I just tested and for quads I can also make them use either the first or the last vertex's colour, i.e. flatshade convention is respected. Thanks, Christoph. Please review/push. Cheers. Marek -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and ea sy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev --- --- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and eas y Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev -- Only fools are easily impressed by what is only barely beyond their reach. ~ Unknown Corbin Simpson mostawesomed...@gmail.com - - This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers
[Mesa3d-dev] [Bug 25719] progs/perf/genmipmap segfaults in glGenerateMipmap()
http://bugs.freedesktop.org/show_bug.cgi?id=25719 Rafael Monica monr...@gmail.com changed: What|Removed |Added CC||monr...@gmail.com --- Comment #1 from Rafael Monica monr...@gmail.com 2009-12-19 18:28:24 PST --- It does segfault here with R600 but not with software renderer. The environment variable to force the software renderer is LIBGL_ALWAYS_SOFTWARE not LIBGL_SOFTWARE_RENDERING. Are you sure you were running the program with the software renderer when it segfaulted? If not, you should change it to R600 bug. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
[Mesa3d-dev] [Bug 25719] progs/perf/genmipmap segfaults in glGenerateMipmap()
http://bugs.freedesktop.org/show_bug.cgi?id=25719 --- Comment #2 from Rafael Monica monr...@gmail.com 2009-12-19 19:52:21 PST --- On second thought, the radeonGenerateMipmap function isn't called at all. So maybe it is a mesa bug? When run normal: 0x08067fe3 84glGenerateMipmap(GL_TEXTURE_2D); (gdb) si 0x in ?? () When forced to software renderer: 0x08067fe3 84glGenerateMipmap(GL_TEXTURE_2D); (gdb) si 0xb7f1b290 in glGenerateMipmapEXT () from /usr/lib/libGL.so.1 (gdb) si 0xb7f1b296 in glGenerateMipmapEXT () from /usr/lib/libGL.so.1 (gdb) si _mesa_GenerateMipmapEXT (target=3553) at main/fbobject.c:1944 -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
[Mesa3d-dev] [Bug 25719] progs/perf/genmipmap segfaults in glGenerateMipmap()
http://bugs.freedesktop.org/show_bug.cgi?id=25719 --- Comment #3 from Ian Romanick i...@freedesktop.org 2009-12-19 22:30:26 PST --- The bug is that the test uses the GL_ARB_framebuffer_object version of the function, but the driver doesn't support GL_ARB_framebuffer_object. It doesn't work. *shock* GLEW sees that the driver doesn't support GL_ARB_framebuffer_object, so it correctly never calls glXGetProcAddress on glGenerateMipmap. Since the driver does support GL_EXT_framebuffer_object, it does call glXGetProcAddress on glGenerateMipmapEXT. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
