[Mesa3d-dev] [Bug 24226] libGL tries using direct mode when it should use indirect (only tries indirect if forced)

2010-03-27 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=24226 --- Comment #15 from George Sapountzis gsapount...@gmail.com 2010-03-27 05:56:07 PST --- (In reply to comment #14) The question is, when libGL.so is compiled with direct rendering support, how to decide if direct rendering is viable at

[Mesa3d-dev] [Bug 24226] libGL tries using direct mode when it should use indirect (only tries indirect if forced)

2009-10-08 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=24226 --- Comment #10 from Chia-I Wu olva...@gmail.com 2009-10-08 03:10:44 PST --- Any comment on the patch? IMO, the issue is a general one that can be seen on XQuartz and other non-DRI based X servers. -- Configure bugmail:

[Mesa3d-dev] [Bug 24226] libGL tries using direct mode when it should use indirect (only tries indirect if forced)

2009-10-08 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=24226 Jon TURNEY jon.tur...@dronecode.org.uk changed: What|Removed |Added CC|

[Mesa3d-dev] [Bug 24226] libGL tries using direct mode when it should use indirect (only tries indirect if forced)

2009-10-08 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=24226 --- Comment #13 from Chia-I Wu olva...@gmail.com 2009-10-08 20:49:45 PST --- (In reply to comment #11) From my experience working on a similar problem with the Cygwin/X DDX, I think the real problem is that the config matching code expects

[Mesa3d-dev] [Bug 24226] libGL tries using direct mode when it should use indirect (only tries indirect if forced)

2009-10-08 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=24226 --- Comment #14 from Chia-I Wu olva...@gmail.com 2009-10-08 21:00:10 PST --- (In reply to comment #12) I might not be understanding the issue correctly, but you can build GLX to only support indirect rendering. Basically, the code needs

[Mesa3d-dev] [Bug 24226] libGL tries using direct mode when it should use indirect (only tries indirect if forced)

2009-10-02 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=24226 --- Comment #5 from Chia-I Wu olva...@gmail.com 2009-10-01 23:50:01 PST --- Created an attachment (id=29992) -- (http://bugs.freedesktop.org/attachment.cgi?id=29992) no empy configs Do you have a nvidia card on your local machine?

[Mesa3d-dev] [Bug 24226] libGL tries using direct mode when it should use indirect (only tries indirect if forced)

2009-10-02 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=24226 --- Comment #6 from Jeremy Huddleston jerem...@freedesktop.org 2009-10-02 00:02:05 PST --- Yes, I have an nVidia card on this machine, but it also happens when I have an ATI card on the server machine. The vendor card information is

[Mesa3d-dev] [Bug 24226] libGL tries using direct mode when it should use indirect (only tries indirect if forced)

2009-10-02 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=24226 --- Comment #7 from Chia-I Wu olva...@gmail.com 2009-10-02 00:43:07 PST --- There is no spec on the rules. The visuals/fbconfigs reported by the server are converted to __GLcontextModes in mesa. You can have a look at driConfigEqual in

[Mesa3d-dev] [Bug 24226] libGL tries using direct mode when it should use indirect (only tries indirect if forced)

2009-10-02 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=24226 --- Comment #8 from Chia-I Wu olva...@gmail.com 2009-10-02 00:57:36 PST --- I had a quick look at the link you gave. It might be maxPbufferWidth/maxPbufferHeight that fails the matching test. But there is no point to adjust the two fileds

[Mesa3d-dev] [Bug 24226] libGL tries using direct mode when it should use indirect (only tries indirect if forced)

2009-10-02 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=24226 --- Comment #9 from Jeremy Huddleston jerem...@freedesktop.org 2009-10-02 01:08:27 PST --- Excellent. With that patch in place, we end up with AIGLX rather than erroring out. Looks good to me. -- Configure bugmail:

[Mesa3d-dev] [Bug 24226] libGL tries using direct mode when it should use indirect (only tries indirect if forced)

2009-10-01 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=24226 --- Comment #2 from Jeremy Huddleston jerem...@freedesktop.org 2009-10-01 01:17:41 PST --- You miss the point. This isn't about glxinfo, this is about *ALL* glx applications. glxinfo is just an example. You said, glxinfo creates a context

[Mesa3d-dev] [Bug 24226] libGL tries using direct mode when it should use indirect (only tries indirect if forced)

2009-10-01 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=24226 --- Comment #3 from Chia-I Wu olva...@gmail.com 2009-10-01 20:29:39 PST --- I see your point. I guess the old behavior is simply because there was no swrast_dri. As for swrast_dri, it has _direct_ access to the (pure software) OpenGL

[Mesa3d-dev] [Bug 24226] libGL tries using direct mode when it should use indirect (only tries indirect if forced)

2009-10-01 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=24226 --- Comment #4 from Jeremy Huddleston jerem...@freedesktop.org 2009-10-01 21:11:29 PST --- Created an attachment (id=29991) -- (http://bugs.freedesktop.org/attachment.cgi?id=29991) glxinfo.txt Here's glxinfo's output when run as a local

[Mesa3d-dev] [Bug 24226] libGL tries using direct mode when it should use indirect (only tries indirect if forced)

2009-09-30 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=24226 Chia-I Wu olva...@gmail.com changed: What|Removed |Added CC||olva...@gmail.com ---