The modes
line in the XF86Config
file is now handled
differently.
The virtual line is now ignored entirely. Each mode on the mode
line is looked at and the first usable mode is selected (ie the first
one which works with available memory, etc). Any other modes which
are valid and have the same dimensions are also used. And other modes
are ignored.
The current supported keywords in the Device
section
of the XF86Config
file are:
1024 or 2048 (use 2048 for ``3MB'' Orchid P9000's)
"vipervlb"
or "viperpci"
or
"orchid_p9000"
0xA0000000 or 0x20000000 or 0x80000000 (0x80000000 is default if none spec'd)
0xC0000000 or 0xD0000000 or 0xE0000000 (this MUST be set to correspond to the jumpers)
any value corresponding to the output
of PCIDUMP.EXE
any value corresponding to the output
of PCIDUMP.EXE
unused
any values between 25 and 135 corresponding to the clocks for the mode entries being used. This line may now be omitted and clocks will be matched automatically.
use software cursor
use if you have 1024K VRAM in 128Kx8 SIMMS
generate sync pulses on the green signal. Most (all?) P9000 based boards don't support this.
do not do hardware acceleration if it's causing problems for you
almost any valid mode (there are constraints on the horiz res so not all values are possible)
XF86Config
file are:
use 8 bits per pixel for 256 colors (default)
use 16 bits per pixel for up to 65K colors
use 32 bits per pixel (sparse 24 bpp) for up to 16 million colors
555 or 565 if Depth is 15 or 16. Otherwise this is ignored. These are the Red, Green, and Blue bits per pixel (default=565)
XF86Config
file for the Viper VLB:
Section "Device" Identifier "ViperVLB" VendorName "Diamond" BoardName "Viper VLB" Videoram 2048 # This is mandatory Membase 0x80000000 # This is mandatory on non-ViperVLB's IOBase 0xe000 # Use this ONLY on ViperPCI's EndSection Section "Screen" Driver "accel" Device "ViperVLB" Monitor "NEC4FGe" Subsection "Display" Depth 8 # This line is optional Modes "1024x768" "800x600" EndSubsection EndSection