Hey Ian, On Feb 27, 09 17:13:41 -0800, Ian Romanick wrote: > Matthias Hopf wrote: > > I haven't noticed until recently (due to a bug opened against our > > openSUSE 11.1) that indirect rendering via GLX doesn't work any more > > when an older Xserver is involved. > > Can you be more specific? What commands don't work? Can you run > glxinfo on one machine using the display on another?
You can run it, but the output doesn't make any sense, because it doesn't get reasonable visuals: gkar:~ # glxinfo name of display: localhost:10.0 Error: couldn't find RGB GLX visual visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat ---------------------------------------------------------------------- 0x23 24 tc 1 0 0 c . . 0 0 0 0 0 0 0 0 0 0 0 0 0 None 0x24 24 tc 1 0 0 c . . 0 0 0 0 0 0 0 0 0 0 0 0 0 None 0x25 24 tc 1 0 0 c . . 0 0 0 0 0 0 0 0 0 0 0 0 0 None 0x26 24 tc 1 0 0 c . . 0 0 0 0 0 0 0 0 0 0 0 0 0 None 0x27 24 dc 1 0 0 c . . 0 0 0 0 0 0 0 0 0 0 0 0 0 None 0x28 24 dc 1 0 0 c . . 0 0 0 0 0 0 0 0 0 0 0 0 0 None 0x29 24 dc 1 0 0 c . . 0 0 0 0 0 0 0 0 0 0 0 0 0 None 0x2a 24 dc 1 0 0 c . . 0 0 0 0 0 0 0 0 0 0 0 0 0 None You can find the whole history in https://bugzilla.novell.com/show_bug.cgi?id=469280 > > Some research brought up that this had been broken knowingly: > > > > git commit #1087cc61b3776f: > > > > Author: George Sapountzis <gs...@yahoo.gr> 2008-06-13 14:54:08 > > > > glx: load swrast_dri.so > > > > caveats: > > - does not work with old (i.e. libGLcore) xserver: > > [...] > > Eh...what? What repo is that? swrast_dri.so doesn't have anything to > do with the GLX protocol. I'm not really sure what is meant by that > comment. George? Standard, in master branch. And yes, I do stand puzzled here as well :-] > > IMHO this is a no-go - the protocol layer is standardized, and I don't > > know why this had to be broken. Given that I don't understand the > > benefits of direct software rendering (compared to indirect) I just > > use the applied patch to disable it again. I haven't seen any serious > > side effects so far. > > There is quite a bit of functionality for which there is no indirect > rendering protocol. Also, client-side software rendering is usually > faster than server-side software rendering. Ok, but given that software rendering isn't exactly useful in normal cases, I see the non-ability to connect to older Xservers as a much more severe issue. CU Matthias -- Matthias Hopf <mh...@suse.de> __ __ __ Maxfeldstr. 5 / 90409 Nuernberg (_ | | (_ |__ m...@mshopf.de Phone +49-911-74053-715 __) |_| __) |__ R & D www.mshopf.de ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
