Package: libsvga1 Version: 1:1.4.3-25 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: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Shell: /bin/sh linked to /bin/dash Versions of packages libsvga1 depends on: ii libc6 2.7-11 GNU C Library: Shared libraries ii libx86-1 0.99+ds1-2 x86 real-mode library libsvga1 recommends no packages. -- no debconf information
--- svgalib.mach32.7 2007-12-18 23:29:31.000000000 -0500 +++ /tmp/svgalib.mach32.7 2008-05-20 00:37:35.000000000 -0400 @@ -13,7 +13,7 @@ .br .BR " 4. " "Third party cards" .br -.BR " 5. " "Logical linewidth" +.BR " 5. " "Logical line width" .br .BR " 6. " "Noisy video signals" .br @@ -195,7 +195,7 @@ I had to learn that those cards seem to use not only non standard clocks for the Mach32, but also for the included SVGA. However, since people often like to use proprietary, non standard VGA -(read 80x25) textmodes, the Mach32 driver has to set the included SVGA to +(read 80x25) text modes, the Mach32 driver has to set the included SVGA to a VGA compatible clock frequency. Otherwise svgalib has problems using plain VGA modes. This screws VGA modes up if these clocks have different values on third party Mach32 cards. @@ -224,7 +224,7 @@ is special in that the driver will not touch any SVGA timings. This requires the Mach32 SVGA part to be in a VGA compatible mode when the svgalib application is started, that is, -you must use 80x25 (maybe 80x50) console textmodes. +you must use 80x25 (maybe 80x50) console text modes. .PP As I mentioned already, @@ -340,19 +340,19 @@ .SH 5. LOGICAL LINEWIDTH At least my VRAM card seems to be very peculiar about logical -linewidths. From my experience a multiple of 64 pels is needed. +line widths. From my experience a multiple of 64 pels is needed. Your mileage may vary. Use the config file options to adjust it and tell me if your card needs a different value. Include the name and model number of the card and what the correct numbers should be. This is so that I can correct the auto configuration of the driver. If some svgalib application has problems, note that you can -force the logical linewidth to the default value from the -configfile. Probably this will lead to glitches in some 800x600 +force the logical line width to the default value from the +config file. Probably this will lead to glitches in some 800x600 resolutions. You can .B inhibit -these resolutions from the configfile -as well. Apropos glitches, I found no guidelines as to what clockrates +these resolutions from the config file +as well. Apropos glitches, I found no guidelines as to what clock rates to use due to memory restrictions. I adjusted the driver, such that I get a stable pic in all resolutions. However sometimes the screen is disturbed by heavy video memory accesses. If you don't like that, @@ -514,7 +514,7 @@ .B mach32eeprom ignore usetimings -to use the videomodes that are defined in the EEPROM (if no better modes are +to use the video modes that are defined in the EEPROM (if no better modes are known by the driver). This is usually safe, because the driver knows which modes are safe for your hardware (if .BR clocks ", " monitor " and " ramdac @@ -589,17 +589,17 @@ Don't complain about checksum and don't use any EEPROM contents. .TP .B useaperture -Use the configuration for the memoryaperture given in the EEPROM. +Use the configuration for the memory aperture given in the EEPROM. .TP .B usetimings -Use videomodes found in the EEPROM of the board. +Use video modes found in the EEPROM of the board. .TP .B nofile Forget about any filename that maybe was already configured. Don't read a file, don't create one. .TP .BI "file " filename -Newstyle form to specify the +New style form to specify the .IR filename ; On contrary to the .BI "mach32eeprom " filename
