Re: [Dri-devel] Re: [PATCH] Savage streams re-work

2004-03-22 Thread Felix Kühling
On Sun, 21 Mar 2004 14:24:41 -0800 (PST) Alex Deucher [EMAIL PROTECTED] wrote: --- Felix K_hling [EMAIL PROTECTED] wrote: On the Savage IX it freezes now, when the 3D window gets too close to the bottom of the screen. There is an extra allocation of 128kb at the end of the frame buffer

[Dri-devel] Re: [PATCH] Savage streams re-work

2004-03-21 Thread Felix Kühling
On the Savage IX it freezes now, when the 3D window gets too close to the bottom of the screen. There is an extra allocation of 128kb at the end of the frame buffer that is not included in RamNeedeFor3D. It doesn't seem to be used though. Also the computation of the HW cursor location is off by

Re: [Dri-devel] Re: [PATCH] Savage streams re-work

2004-03-21 Thread Alex Deucher
--- Felix Kühling [EMAIL PROTECTED] wrote: On the Savage IX it freezes now, when the 3D window gets too close to the bottom of the screen. There is an extra allocation of 128kb at the end of the frame buffer that is not included in RamNeedeFor3D. It doesn't seem to be used though. Also the

[Dri-devel] Re: [PATCH] Savage streams re-work

2004-03-20 Thread Felix Kühling
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

[Dri-devel] Re: [PATCH] Savage streams re-work

2004-03-20 Thread Alex Deucher
--- Felix Kühling [EMAIL PROTECTED] wrote: 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

[Dri-devel] Re: [PATCH] Savage streams re-work

2004-03-20 Thread Alex Deucher
--- Felix Kühling [EMAIL PROTECTED] wrote: On Sat, 20 Mar 2004 09:07:55 -0800 (PST) Alex Deucher [EMAIL PROTECTED] wrote: [snip] No artifacts. The video is absolutely stable. Cool. I've enabled it by default for prosavages and twisters. you can still disable it with the BCIforXv

[Dri-devel] Re: [PATCH] Savage streams re-work

2004-03-20 Thread Felix Kühling
Alex, I took another close look at your patch while I was tracking down another problem that was previously masked by the missing COB. In the end it turned out that it was not your fault. ;-) But still, I think this line is wrong: /* align cob to 128k */ - psav-cobOffset = ((endfb -

[Dri-devel] Re: [PATCH] Savage streams re-work

2004-03-19 Thread Felix Kühling
On Fri, 19 Mar 2004 12:51:14 -0800 (PST) Alex Deucher [EMAIL PROTECTED] wrote: I've re-worked the non-Xv streams code and a few other things. I added a new streams reset function that seems to fix the occasional console corruption I got on my IX. I enabled the COB on savage4 and newer chips

[Dri-devel] Re: [PATCH] Savage streams re-work

2004-03-19 Thread Alex Deucher
--- Felix Kühling [EMAIL PROTECTED] wrote: On Fri, 19 Mar 2004 12:51:14 -0800 (PST) Alex Deucher [EMAIL PROTECTED] wrote: I've re-worked the non-Xv streams code and a few other things. I added a new streams reset function that seems to fix the occasional console corruption I got on my

[Dri-devel] Re: [PATCH] Savage streams re-work

2004-03-19 Thread Alex Deucher
--- Felix Kühling [EMAIL PROTECTED] wrote: On Fri, 19 Mar 2004 12:51:14 -0800 (PST) Alex Deucher [EMAIL PROTECTED] wrote: I've re-worked the non-Xv streams code and a few other things. I added a new streams reset function that seems to fix the occasional console corruption I got on my