Lines Matching refs:on
6 This is a driver for a graphic framebuffer for Matrox devices on
13 * You can run XF{68,86}_FBDev or XFree86 fbdev driver on top of /dev/fb0
33 unless you have primary display on non-Matrox VBE2.0 device (see
87 XFree servers have big troubles in multihead configurations (even on first
97 Driver contains SVGALib compatibility code. It is turned on by choosing textual
116 memory usable for on-screen display (i.e. max. 8 MB).
122 noaccel - do not use acceleration engine. It does not work on Alphas.
146 strange pattern on screen and so on. Devices not enabled by BIOS
170 nomtrr - disables write combining on frame buffer. This slows down driver but
173 mtrr - enables write combining on frame buffer. It speeds up video accesses
180 inv24 - change timings parameters for 24bpp modes on Millenium and
184 inverse - invert colors on screen (for LCD displays)
185 noinverse - show true colors on screen. It is default.
187 where device 0 is first `known' device found, 1 second and so on.
202 It is faster on Gx00 series, but slower on older cards.
231 111 for G450 and G550. You can set mapping only on first card,
262 generated. If bit 5 (value 0x20) is set, sync on green is turned on.
263 Do not forget that if you want sync on green, you also probably
265 Default depends on `vesa'.
266 depth:X - Bits per pixel: 0=text, 4,8,15,16,24 or 32. Default depends on
287 + SVGALib does not restore screen on exit
288 + generic fbcon-cfbX procedures do not work on Alphas. Due to this,
289 `noaccel' (and cfb4 accel) driver does not work on Alpha. So everyone
290 with access to /dev/fb* on Alpha can hang machine (you should restrict
293 + 24bpp does not support correctly XF-FBDev on big-endian architectures.
301 + SVGALib does not restore screen on exit.
303 83 MHz on G200
304 66 MHz on Millennium I
305 60 MHz on Millennium II
309 pretty effects on screen. Device was not destroyed during tests. :-)
311 (and it works with 8bpp on about 320 MHz dotclocks (and changed mclk)).
312 But Matrox says on product sheet that VCO limit is 50-250 MHz, so I believe
322 specify vslen=4000 and so on).
325 + 4bpp is available only on Millennium I and Millennium II. It is hardware
338 time for draw 6144000 characters on screen through /dev/vcsa
342 faster, it is kernel-space only time on P-II/350 MHz, Millennium I in 33 MHz