167 lines
3.3 KiB
HTML
167 lines
3.3 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
|
<HTML
|
|
><HEAD
|
|
><TITLE
|
|
>Overdriving Your Monitor</TITLE
|
|
><META
|
|
NAME="GENERATOR"
|
|
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
|
|
REL="HOME"
|
|
TITLE="X.org/XFree86 Video Timings HOWTO"
|
|
HREF="index.html"><LINK
|
|
REL="PREVIOUS"
|
|
TITLE="Putting it All Together"
|
|
HREF="synth.html"><LINK
|
|
REL="NEXT"
|
|
TITLE="Using Interlaced Modes"
|
|
HREF="inter.html"></HEAD
|
|
><BODY
|
|
CLASS="sect1"
|
|
BGCOLOR="#FFFFFF"
|
|
TEXT="#000000"
|
|
LINK="#0000FF"
|
|
VLINK="#840084"
|
|
ALINK="#0000FF"
|
|
><DIV
|
|
CLASS="NAVHEADER"
|
|
><TABLE
|
|
SUMMARY="Header navigation table"
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TH
|
|
COLSPAN="3"
|
|
ALIGN="center"
|
|
>X.org/XFree86 Video Timings HOWTO</TH
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="left"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="synth.html"
|
|
ACCESSKEY="P"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="80%"
|
|
ALIGN="center"
|
|
VALIGN="bottom"
|
|
></TD
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="right"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="inter.html"
|
|
ACCESSKEY="N"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"></DIV
|
|
><DIV
|
|
CLASS="sect1"
|
|
><H1
|
|
CLASS="sect1"
|
|
><A
|
|
NAME="overd"
|
|
></A
|
|
>13. Overdriving Your Monitor</H1
|
|
><P
|
|
>You should absolutely <EM
|
|
>not</EM
|
|
> try exceeding your
|
|
monitor's scan rates if it's a fixed-frequency type. You can smoke
|
|
your hardware doing this! There are potentially subtler problems with
|
|
overdriving a multisync monitor which you should be aware of.</P
|
|
><P
|
|
>Having a pixel clock higher than the monitor's maximum bandwidth is
|
|
rather harmless, in contrast. It's exceeding the rated maximum sync
|
|
frequencies that's problematic. Some modern monitors might have
|
|
protection circuitry that shuts the monitor down at dangerous scan
|
|
rates, but don't rely on it. In particular there are older multisync
|
|
monitors (like the Multisync II) which use just one horizontal
|
|
transformer. These monitors will not have much protection against
|
|
overdriving them. While you necessarily have high voltage regulation
|
|
circuitry (which can be absent in fixed frequency monitors), it will
|
|
not necessarily cover every conceivable frequency range, especially in
|
|
cheaper models. This not only implies more wear on the circuitry, it
|
|
can also cause the screen phosphors to age faster, and cause more than
|
|
the specified radiation (including X-rays) to be emitted from the
|
|
monitor.</P
|
|
><P
|
|
>However, the basic problematic magnitude in question here is the slew
|
|
rate (the steepness of the video signals) of the video output drivers,
|
|
and that is usually independent of the actual pixel frequency, but
|
|
(if your board manufacturer cares about such problems) related
|
|
to the maximum pixel frequency of the board.</P
|
|
><P
|
|
>So be careful out there...</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="NAVFOOTER"
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"><TABLE
|
|
SUMMARY="Footer navigation table"
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="synth.html"
|
|
ACCESSKEY="P"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="index.html"
|
|
ACCESSKEY="H"
|
|
>Home</A
|
|
></TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="inter.html"
|
|
ACCESSKEY="N"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
>Putting it All Together</TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
> </TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
>Using Interlaced Modes</TD
|
|
></TR
|
|
></TABLE
|
|
></DIV
|
|
></BODY
|
|
></HTML
|
|
> |