Comment 4 for bug 670790

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?