Savage XV problems

Alex Deucher alexdeucher at
Fri Aug 25 20:33:19 PDT 2006

On 8/23/06, Louai Al-Khanji <louai.khanji at> wrote:
> Hello,
> I've recently acquired an IBM T22 thinkpad, with a savage card. More
> specifically a Savage IX-MV. There are a few bugs I'd like to look into if
> someone can give me a hand, mostly concerning Xv support. This is all with
> the latest git version of the driver.

Feel free to try and fix the streams support in the savage driver.
I'll help you as much as I can, but I warn you, the "streams" engine
pretty awful.

> Bug 1) Occasionally I get weird stripes across the upper part of the video,
> somewhat akin to the image in this bug report:
> I can make the corruption
> disappear in eg kaffeine if I make a tooltip appear over the video stream.
> Also, this goes away when switching to full screen.

I see these some times as well.  I think it comes from starting and
stopping the streams engine when when playing a video rather than
leaving streams on all the time.  if you leave streams on all the
time, it kills 3D performance because it eats bandwith and I've never
had much luck with leaving streams on all the time.  It tends to stop
working after a mode change and never come back.  streams should
really be tied into the mode setting code, but it's a lot of work.  I
may get to it someday.  I've figured out most of what I need for
non-bios dualhead and I may re-implement large amounts of the savage
driver at somepoint if I have time.

> Bug 2) When changing resolution with xrandr and subsequently watching a video,
> not the whole Xv viewport is updated. Rather, only slightly less than half of
> the left side contains any video. The right hand side is blue, like when
> taking a screen capture of Xv video.

probably related to either the panel scaler or a bad offset after a
mode change.  do you get similar problems when using a CRT only?

> So it seems there is some error in either Xv window setup, or content update.
> If someone could tell me at which functions to look, I could play around a
> bit and see what happens, hopefully leading to a good bug report and/or a
> solution.

Take a look at savage_streams.c/h, savage_video.c, and savage_regs.h.
If you have any questions about how the streams engine is supposed to
work let me know.


> Thanks,
> Louai

More information about the xorg mailing list