David Dawes wrote:
The patch below fixes the problem. The command lengths for several
rendering requests were getting set incorrectly because of mis-ordered
variable initialisations. I'm committing it now.
Index: g_render.c
===
RCS
On Fri, Nov 14, 2003 at 12:40:55PM +0100, Frank Gießler wrote:
David Dawes wrote:
The patch below fixes the problem. The command lengths for several
rendering requests were getting set incorrectly because of mis-ordered
variable initialisations. I'm committing it now.
Index: g_render.c
At 10:01 AM -0800 11/10/03, Ian Romanick wrote:
Frank Gießler wrote:
with my current CVS snapshot (Changelog up to
#530), glxgears gives me the following at
startup:
X Error of failed request: BadLength (poly
request too large or internal Xlib length error)
Major opcode of failed request:
On Thu, Nov 13, 2003 at 04:40:30PM -0800, Torrey Lyons wrote:
At 10:01 AM -0800 11/10/03, Ian Romanick wrote:
Frank Gießler wrote:
with my current CVS snapshot (Changelog up to
#530), glxgears gives me the following at
startup:
X Error of failed request: BadLength (poly
request too large or
Hi all,
with my current CVS snapshot (Changelog up to #530), glxgears gives me the following at startup:
X Error of failed request: BadLength (poly request too large or internal Xlib length
error)
Major opcode of failed request: 144 (GLX)
Minor opcode of failed request: 1 (X_GLXRender)
Frank Gießler wrote:
with my current CVS snapshot (Changelog up to #530), glxgears gives me
the following at startup:
X Error of failed request: BadLength (poly request too large or
internal Xlib length error)
Major opcode of failed request: 144 (GLX)
Minor opcode of failed request: 1
