old-www/HOWTO/XFree86-Video-Timings-HOWTO/sizes.html

181 lines
3.9 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML
><HEAD
><TITLE
>Memory Requirements</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="Tradeoffs in Configuring your System"
HREF="tradeoffs.html"><LINK
REL="NEXT"
TITLE="Computing Frame Sizes"
HREF="framesizes.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="tradeoffs.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="framesizes.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="sizes"
></A
>9. Memory Requirements</H1
><P
>Available frame-buffer RAM may limit the resolution you can
achieve on color or gray-scale displays. It probably isn't a factor
on displays that have only two colors, white and black with no shades
of gray in between.</P
><P
>For 256-color displays, a byte of video memory is required for each
visible dot to be shown. This byte contains the information that
determines what mix of red, green, and blue is generated for its dot.
To get the amount of memory required, multiply the number of visible
dots per line by the number of visible lines. For a display with a
resolution of 1024x768, this would be 1024 x 768 = 786432, which is
the number of visible dots on the display. This is also, at one byte
per dot, the number of bytes of video memory that will be necessary on
your adapter card.</P
><P
>Thus, your memory requirement will typically be (HR * VR)/1024
Kbytes of VRAM, rounded up (it would come to 768K exactly in this
example). If you have more memory than strictly required, you'll have
extra for virtual-screen panning.</P
><P
>However, if you only have 512K on board yor video card, then you won't
be able to use this resolution. Even if you have a good monitor,
without enough video RAM, you can't take advantage of your monitor's
potential. On the other hand, if your SVGA has one meg, but your
monitor can display at most 800x600, then high resolution is beyond
your reach anyway (see <A
HREF="inter.html"
>Using Interlaced Modes</A
>
for a possible remedy).</P
><P
>Don't worry if you have more memory than required; the X server
will make use of it by allowing you to scroll your viewable area (see
the Xconfig file documentation on the virtual screen size parameter).
Remember also that a card with 512K bytes of memory really doesn't
have 512,000 bytes installed, it has 512 x 1024 = 524,288
bytes.</P
><P
>If you're running X/Inside using an S3 card, and are willing to live
with 16 colors (4 bits per pixel), you can set depth 4 in Xconfig and
effectively double the resolution your card can handle. S3 cards, for
example, normally do 1024x768x256. You can make them do 1280x1024x16
with depth 4.</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="tradeoffs.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="framesizes.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Tradeoffs in Configuring your System</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Computing Frame Sizes</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>