Re: [Dri-devel] Broken context sharing/copying

2002-06-15 Thread Brian Paul
Joe Krahn wrote: I am trying to draw to two windows using one context. It works for Mesa, but gives severe artifacts with DRI. It would work to instead use glXCopyContext, but this still doesn't work for DRI, and it crashes the server with indirect rendering. I am using ATI Rage and

Re: [Dri-devel] Broken context sharing/copying

2002-06-15 Thread Brian Paul
Joe Krahn wrote: [...] Another unrelated thing, not actually DRI: glDrawPixels with GL_BITMAP and an incorrect format correctly gives an error in DRI, but indirect results in an Xlib error: http://home.nc.rr.com/krahnfamily/source/bitmap_bug.c OK, I found the problem here. I fixed it by

Re: [Dri-devel] Broken context sharing/copying

2002-06-13 Thread Jens Owen
Brian, do these tests look reasonable to you? We certainly shouldn't crash the server, even if they are unreasonable. Joe, can your try with the DRI CVS trunk? Joe Krahn wrote: I am trying to draw to two windows using one context. It works for Mesa, but gives severe artifacts with DRI. It

Re: [Dri-devel] Broken context sharing/copying

2002-06-13 Thread Brian Paul
I intend to look into this problem, probably over the weekend. I've got at least one test program of my own to exercise this. Agreed, we shouldn't crash. -Brian Jens Owen wrote: Brian, do these tests look reasonable to you? We certainly shouldn't crash the server, even if they are

[Dri-devel] Broken context sharing/copying

2002-06-11 Thread Joe Krahn
I am trying to draw to two windows using one context. It works for Mesa, but gives severe artifacts with DRI. It would work to instead use glXCopyContext, but this still doesn't work for DRI, and it crashes the server with indirect rendering. I am using ATI Rage and Radeon, with XFree86 CVS.