Am Mittwoch, 2. Juli 2003 18:50 schrieb Ian Romanick:
> I have completed all of the device-independent support (both client-side
> & server-side) for SGI_make_current_read. I wanted to update a couple
> drivers to support this extension before committing it. I was able to
> update the MGA driver without any problems. The Radeon (r100) driver is
> a totally different story.
>
> To test things, I've been using a modified version of our favorite
> glxgears (patch attached) that uses two windows. The usual gears are
> rendered into one window, then the contents of that window are used as a
> texture for a single quad in the other window. The test can run
> properly when either SGI_make_read_current, GLX 1.3, or plain GLX 1.1
> (i.e., no extensions) is supported. On the Radeon, this test fails even
> in GLX 1.1 mode.
>
> In GLX 1.1 mode, the first window is empty (all black), but the second
> window, that uses the contents of the first as a texture, was drawn
> correctly. I tracked this down to a problem in radeonCopyBuffer
> (radeon_ioctl.c, line 807). Even though a __DRIdrawablePrivate is
> passed into this function, it uses the drawable stored in the current
> context. Note the uses of rmesa->dri.drawable. I investigated a bit
> further and discovered that the r200 & r128 drivers all have this problem.
Have you tried with the normal CVS trunk r100/r200 driver?
Some others (e.g. Andreas) and I have reported several times that there is a
"multi-context" (locking) problem.
See:
[Dri-devel] Problem with Radeon 9000 and lockups
and
[Dri-devel] radeon locking doesnt work right
Try two "gears" plus one "ipers" or two "ipers" => boom.
Some xdemos apps show it, too.
"wincopy" isn't working.
Mesa/xdemos> ./wincopy
glXMakeContextCurrent failed in Redraw()
glXMakeContextCurrent failed in Redraw()
glXMakeContextCurrent failed in Redraw()
[-]
"manywin" update only the lasted created window in hardware mode (n<=28). All
additional windows (indirect mode) would be updated simultaneously.
Sometimes it locks X after the second try.
"glthreads" locks X after some seconds, some copies, too.
My former system (single 1 GHz Athlon SlotA, Voodoo5 5500 AGP) could run n=100
(or more) with both.
I see some VTK multi-context ("TaskParallelism", window resizing/overlapping)
problems, too.
And there are some textures/colors missing (ParallelIso, ParallelIsoTest,
PipelineParallelism, TaskParallelismWithPorts).
setenv R200_NO_TCL 1 fix this.
Next one:
"stex3d show a clipping (?) bug.
When I move "stex3d" to the right side of my desktop (1280x1024x24/32) the
torus would be falsely clipped and broken rendered.
I have snapshots.
Last one "celestia":
The earth (Follow Earth [Earth]) show some "flickering" (wrong triangles,
triangel strips) between Southafrica and the Southpole.
Most of these problems are gone with indirect rendering.
Except: wincopy and VTK "TaskParallelism" (window resizing/overlapping).
Regards,
Dieter
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
