Jacek Rosik wrote: > Michel Dänzer wrote: > >> On Wed, 2002-06-26 at 02:35, Jacek Rosik wrote: >> >>> BTW: Why in function radeon_emit_clip_rect >>> (xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel/radeon_state.c) >>> line: >>> /* OUT_RING( ((box->y2 - 1) << 16) | (box->x2 - 1) );*/ >>> is conmmented? I think it's correct, following line: >>> OUT_RING( (box->y2 << 16) | box->x2 ); >>> results in OpenGL rendering primitives into other windows (cliprect >>> one pixel too wide and high) clearing is OK in both cases. >> >> >> >> I have only been able to reproduce the problem in BillardGL, do you have >> other test cases and an explanation why other apps don't show the >> problem? >> > > Sorry for not answering immidiately but I was abroad. > > I think it's general problem of all OpenGL apps when pageflip is > enabled. For example here is atlantis (xscreensaver). > > http://stud.ics.p.lodz.pl/~paproch/dri/border.jpg > > And another strange thing after shading window: > > http://stud.ics.p.lodz.pl/~paproch/dri/shaded.jpg > > those sharks are moving. The same with glxgears and other apps.
It looks like the 'zero cliprects' case doesn't work -- it keeps on using the last-set cliprect -- ie whatever's in hardware. Previously you didn't see these droppings because they were never blitted to the front buffer. It shouldn't be too hard to fix. Keith ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
