Re: [Dri-users] Merged fb with Radeon Mobility 9000 and Xscreensaver

[Faisal P. <fai...@gm...>]

Hi,

I see a similar problem with my Radeon IGP 340M (IBM thinkpad - R40e).
Although the max resolution I can get on my LCD is 1024x768, I see
something very similar when I switch depths to 24 bit. At 16 bit depth
it works just fine. I'm using mergedfb as well. Any suggestions ?

thanks,
Faisal.


On Fri, 13 Aug 2004 09:16:05 -0400, Alex Deucher <ale...@gm...> wrote:
> 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
> >
> 
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> --
> _______________________________________________
> Dri-users mailing list
> Dri...@li...
> https://lists.sourceforge.net/lists/listinfo/dri-users
>