Package: libsvga1 Version: 1:1.4.3-22 Severity: minor Tags: patch
Found some typos in '/usr/share/man/man7/svgalib.mach32.7.gz', see attached '.diff'. Hope this helps... -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Versions of packages libsvga1 depends on: ii libc6 2.3.6-3 GNU C Library: Shared libraries an libsvga1 recommends no packages. -- no debconf information
--- svgalib.mach32.7 2001-05-30 08:02:48.000000000 -0400 +++ /tmp/svgalib.mach32.7 2006-03-14 04:05:31.000000000 -0500 @@ -236,7 +236,7 @@ is only used for some DAC fine tuning (actually the setting you can fine tune with the .B blank -command) which is only of barely noticable effect to the screen. +command) which is only of barely noticeable effect to the screen. The following configuration commands exist to support AST cards: @@ -332,7 +332,7 @@ .IP .I memory -is the amount of videomemory in KB. +is the amount of video memory in KB. .PP Note that the type of the ramdac can be set more conveniently with the .B ramdac @@ -672,7 +672,7 @@ to find the address in .B MEM_CFG. Then, -.BR "if it is a senseable setting for your system" , +.BR "if it is a sensible setting for your system" , enable a 4MB aperture at that address with .BR setuplinear . Ensure that no other card or memory uses the address range you choose. @@ -717,14 +717,14 @@ Thus if you setup some mode yourself try to use one of the divided clocks in your timings and I can use the undivided clocks internally. -It is a real restriction for 16M colors. ATI themself only supports 25MHz +It is a real restriction for 16M colors. ATI itself only supports 25MHz (640x480) here by use of a 75MHz clock. Depending on your clock chip other values may be usable as well. Even the doubled/tripled clocks have to be less than the magic 80 MHz. However the driver does all this itself. It may just happen that some of the predefined or one of your handmade mode-timings can't be used because the clock that is used cannot be doubled/tripled. Even though there is already some tolerance in the driver you may fix that by -slighty changing the clock values that you set with the +slightly changing the clock values that you set with the .B clocks command. But note that this will as well affect the ability of the driver to calculate
