On Fri, 19 Mar 2004 15:21:14 -0800 (PST) Alex Deucher <[EMAIL PROTECTED]> wrote:
[snip] > > There's still one problem. The hardware cursor is corrupted when 3D > > apps > > are active. It looks like the COB is scribbling over the memory that > > stores the hardware cursor bitmasks. With glxgears the pattern > > changes > > very frequently, with flightgear it takes between half a second and a > > second between "updates". ;-) > > UGH... I looked into the cursor/cob problem. apparently different > versions of the savage 4 and newer savages have a different meaning for > the cobIndex bitfield of register 0x48C14 and I'm not sure which are > affected. The old code also didn't align the cob properly. Try the > new patch I've attached. If you are still having problems with the > cursor, try setting the cobIndex to 2 rather than 7 for your chip. Your new patch still has the same problem. cobIndex 2 fixes it. > [snip] > > Do you see any corruption when you move the output window around? It > leaves artifacts on savage4. If not, perhaps we can enable the BCI for > Xv on prosavages and twisters. No artifacts. The video is absolutely stable. > [snip] ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
