I don't think there are any issues with the blit engine at 16 bit. I think the problem has something to do with the way multi-line pixmap cache's are stored in the offscreen memory. The pitch in the Xaa functions is set to be the same pitch as the framebuffer, which may not be the case.
If you can track down the code that puts the cached pixmaps in the offscreen memory you can probably determine how they are being arranged in that memory. Perhaps that code is unaware of the pitch != width case. (Is Xaa used to blit from on-screen locations to the offscreen cache?) -Matt -----Original Message----- From: Bill Soudan [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 25, 2002 9:42 AM To: [EMAIL PROTECTED] Subject: Re: [Xpert]KDE3/i810 corruption - source pointers? On Wed, 25 Sep 2002, Bill Soudan wrote: > http://www.xfree86.org/pipermail/xpert/2002-June/018208.html Why changing the resolution to 24bpp 'solves' the problem: xc/programs/Xserver/hw/xfree86/drivers/i810/i810_accel.c: /* There is a bit blt bug in 24 bpp. This is a problem, but at least without the pixmap cache we can pass the test suite */ if(pScrn->depth != 24) infoPtr->Flags |= PIXMAP_CACHE; I believe this indicates to the Xserver that the driver can't do a pixmap cache, which has the same effect as enabling the XaaNoPixmapCache flag. Maybe this is actually a hardware bug then (ugh)? More pronounced at 24bpp but still exists at the other depths? Maybe I'll remove the check and try 24bpp with a pixmap cache just to see what happens... Bill _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
