On 3/1/11 3:02 PM, Nathan Kidd wrote:
This matches what my WireShark trace saw (last request was
glXCreatePBuffer). In that hypothesis:
VGL handles glXCreatePbuffer() with no problems (I even test for that in
rrfakerut.) In the trace, that function completes without error, so it
must be a
On 11-03-02 03:01 AM, DRC wrote:
On 3/1/11 3:02 PM, Nathan Kidd wrote:
This matches what my WireShark trace saw (last request was
glXCreatePBuffer). In that hypothesis:
VGL handles glXCreatePbuffer() with no problems (I even test for that in
rrfakerut.) In the trace, that function
On 11-03-01 04:02 PM, Nathan Kidd wrote:
Hmmm, actually, I have an idea, based on what DRC said before about
NV-GLX. When an NV-GLX libGL talks to a server that supports NV-GLX it
has additional traffic (major opcode 139 on my server). This must be
where the error comes from and why nothing
On 11-03-01 03:37 PM, calvin.mor...@comcast.net wrote:
Forgive the direct forward - I tried sending this message out to the
list and it is either delayed or lost in mailing list limbo.
Heh, Mesa did recently move mailing lists to freedesktop.org for a
reason. :)
- Forwarded Message -
