[ltp] DVI problem again

[Martin Höfling]

--nextPart1744417.4sgPVHdVh6
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Am Mittwoch, 16. November 2005 15:43 schrieb Alex Deucher:

> right now the digital outputs in the radeon driver (LVDS and TMDS) do
> not allow user modelines to prevent users from damaging their panels,
> however, in some cases, it's advantageous to override the driver's
> mode as per the bug I mentioned above.

All calculation from various tools gave me a dot clock greater than 165.  I=
n=20
the analog case, the mode is set properly:

(II) RADEON(0): Supported additional Video Mode:
(II) RADEON(0): clock: 162.0 MHz   Image Size:  408 x 306 mm
(II) RADEON(0): h_active: 1600  h_sync: 1664  h_sync_end 1856 h_blank_end 2=
160=20
h_border: 0
(II) RADEON(0): v_active: 1200  v_sync: 1201  v_sync_end 1204 v_blanking: 1=
250=20
v_border: 0
(II) RADEON(0): Ranges: V min: 56  V max: 75 Hz, H min: 30  H max: 81 kHz,=
=20
PixClock max 170 MHz

I used a xls sheet in gnumeric to calculate the modelines with reduced=20
blanking times and with this modeline, it should be possible to use the tft=
=20
with 60 Hz and a dot clock < 165MHz.
Is the dot-clock limited in the same way on the analog side? If yes, then
your information corresponds to the problem, that the analog output is set=
=20
independent compared to the TMDS.

Best wishes

	Martin
=2D-=20
Glaubw=FCrdigkeit ist ein soziales Konstrukt, das wesentlich aus
Anerkennung erw=E4chst. (Andreas Peeck in de.admin.news.groups)

--nextPart1744417.4sgPVHdVh6
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1-ecc0.1.6 (GNU/Linux)

iD8DBQBDe2u50Vwi9WwD/JYRAhpNAKC204J7vJizZ5GCxkmQUJiPKSutjwCgpAXu
zJycqYmbTW8VhCn7qBwlnWs=
=9X4V
-----END PGP SIGNATURE-----

--nextPart1744417.4sgPVHdVh6--