From: Fredrik Noring <hidden> Date: 2003-01-24 23:16:36
I've been digging around in the rivafb module to find out why some
modes converted from XFree86 4.2 don't work on some display devices.
Here's a funny part of the riva_load_video_mode function (Linux
2.4.21-pre2):
hStart = (hDisplaySize + video_mode->right_margin) / 8 + 2;
hEnd = (hDisplaySize + video_mode->right_margin +
video_mode->hsync_len) / 8 - 1;
Please notice how "hsync_len" does not actually represent the length
of the sync. Rather, it's compensated with 24 pixels. The corresponding
code in the XFree86 4.2 (nv_dac.c) contains no such compensation:
int horizStart = (mode->CrtcHSyncStart/8) - 1;
int horizEnd = (mode->CrtcHSyncEnd/8) - 1;
The difference seems to be almost insignificant for modern multisync
screens, but devices such as TV:s get confused by the current version.
Is there a reason for the difference in calculations?
The attached patch corrects the calculations in accordance with XFree86
and works better with the modelines I've tested.
Please give it a try. Thanks,
Fredrik
From: James Simmons <hidden> Date: 2003-01-25 19:13:58
I've been digging around in the rivafb module to find out why some
modes converted from XFree86 4.2 don't work on some display devices.
Here's a funny part of the riva_load_video_mode function (Linux
2.4.21-pre2):
hStart = (hDisplaySize + video_mode->right_margin) / 8 + 2;
hEnd = (hDisplaySize + video_mode->right_margin +
video_mode->hsync_len) / 8 - 1;
Please notice how "hsync_len" does not actually represent the length
of the sync. Rather, it's compensated with 24 pixels. The corresponding
code in the XFree86 4.2 (nv_dac.c) contains no such compensation:
int horizStart = (mode->CrtcHSyncStart/8) - 1;
int horizEnd = (mode->CrtcHSyncEnd/8) - 1;
The difference seems to be almost insignificant for modern multisync
screens, but devices such as TV:s get confused by the current version.
Is there a reason for the difference in calculations?
The attached patch corrects the calculations in accordance with XFree86
and works better with the modelines I've tested.
Please give it a try. Thanks,
Works fine. I applied it to the 2.5.X tree.
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
From: Fredrik Noring <hidden> Date: 2003-01-25 23:18:02
Works fine. I applied it to the 2.5.X tree.
Has anyone got Riva 128 or TNT cards working with 2.5.59 or
later? My cards freeze up completely with the new driver when
loading fbcon.
Fredrik
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
From: James Simmons <hidden> Date: 2003-01-28 19:20:56
quoted
Works fine. I applied it to the 2.5.X tree.
Has anyone got Riva 128 or TNT cards working with 2.5.59 or
later? My cards freeze up completely with the new driver when
loading fbcon.
The card I have is a Diamond Multimedia Systems Viper V730.
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
On Sun, 2003-01-26 at 07:18, Fredrik Noring wrote:
quoted
Works fine. I applied it to the 2.5.X tree.
Has anyone got Riva 128 or TNT cards working with 2.5.59 or
later? My cards freeze up completely with the new driver when
loading fbcon.
Fredrik
Works for STB Velocity 128 PCI (Riva 128)
Tony
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
From: James Simmons <hidden> Date: 2003-02-12 18:42:26
Applied.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf