From: Alex D. <ale...@gm...> - 2004-08-13 13:16:10
|
On Fri, 13 Aug 2004 00:47:16 +0200, Roland Scheidegger <rsc...@hi...> wrote: > > > lyn...@fr... wrote: > > I have a laptop with a radion mobility 9000 graphics card and managed to get a > > merged frame buffer working for dual head and 3D-acceleration. (Many thanks to > > the team for the great driver.) > > Then I noticed that some xscreensaver gl-hacks work perfectly like glmatirx, > > speed mine and the solid hypertorus but all other gl-based hacks only show up > > on the main screen and on the other are small fragments of the polygons > > sometimes. Strangely the striped hypertorus does also not work on both > > screens. > > As some hacks work I thought it won't be a problem with the dri-driver that > > gives the merged fb but the author of xscreensaver Jamie Zawinski told me > > that it must have something to do with the video layer because "all GL code > > code in the various hacks operates essentially the same way." Now I wonder > > whether my problem is just a misconfiguration of my system or really a bug in > > the driver. Can anybody help me with this? > > Looks like a driver bug to me. What version are you using? > I think there was once a bug so it worked only up to 2047x2047 instead > of 2048x2048 (which is the maximum at least for now), though I don't > remember if this was fixed or not. Does it work correctly at lower > resolutions? Roland's right. When I was writting mergedfb support I noticed the same problem if a 3D app hits the 2048 limit. I wasn't able to track down the problem at the time (possibly an off by 1 error somewhere?). Also as Roland said, the limits of the 3D engine are 2048x2048. In order to have 3D work for larger resolutions we would need to iterate over the cliprects in blocks below the 2048 limit, much like the new render accel code does. Alex > > Roland > |