ubuntu-x-swat team mailing list archive

[Tormod Volden <670790@xxxxxxxxxxxxxxxxxx>]

I have had a closer look, and can confirm the issue on my TwisterK
chipset. You should do the same changes in SavageDisplayVideoOld() which
is used for the MOBILE_TWISTER chipset series. After doing this, I could
confirm that the (extrapolated) patch fixes the issue. I could not see
any difference by leaving the +7 out though. Maybe this depends on the
location of the video window. Also, I noted that in the original code
the calculation is done with floats in SavageDisplayVideoOld but
integers in SavageDisplayVideoNew. Could this be related? Can you please
check if using floats is better anyway?

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-savage in Ubuntu.
https://bugs.launchpad.net/bugs/670790

Title:
  Xv / XVideo accelerated video width is limited by / depending on the
  screen resolution on S3 Savage, but only if the laptop LCD is the
  primary screen