Lines Matching +full:pulse +full:- +full:code
2 matroxfb - Framebuffer driver for Matrox devices
13 * Most important: boot logo :-)
31 box) and matroxfb (for graphics mode). You should not compile-in vesafb
32 unless you have primary display on non-Matrox VBE2.0 device (see
36 has [as addon] compatibility code):
40 -------------
55 -------------------------
70 ----------
83 Non-listed number can be achieved by more complicated command-line, for
90 XF{68,86}_FBDev should work just fine, but it is non-accelerated. On non-intel
94 Running another (accelerated) X-Server like XF86_SVGA works too. But (at least)
97 driver is possible, but you must not enable DRI - if you do, resolution and
105 Driver contains SVGALib compatibility code. It is turned on by choosing textual
107 2,3,7,0x108-0x10C or 0x1C0. At runtime, `fbset -depth 0` does this work.
125 memory usable for on-screen display (i.e. max. 8 MB).
162 - 0 -> 2x128Kx32 chips, 2MB onboard, probably sgram
163 - 1 -> 2x128Kx32 chips, 4MB onboard, probably sgram
164 - 2 -> 2x256Kx32 chips, 4MB onboard, probably sgram
165 - 3 -> 2x256Kx32 chips, 8MB onboard, probably sgram
166 - 4 -> 2x512Kx16 chips, 8/16MB onboard, probably sdram only
167 - 5 -> same as above
168 - 6 -> 4x128Kx32 chips, 4MB onboard, probably sgram
169 - 7 -> 4x128Kx32 chips, 8MB onboard, probably sgram
171 - 0 -> 2x512Kx16 SDRAM, 16/32MB
172 - 2x512Kx32 SGRAM, 16/32MB
173 - 1 -> 2x256Kx32 SGRAM, 8/16MB
174 - 2 -> 4x128Kx32 SGRAM, 8/16MB
175 - 3 -> 4x512Kx32 SDRAM, 32MB
176 - 4 -> 4x256Kx32 SGRAM, 16/32MB
177 - 5 -> 2x1Mx32 SDRAM, 32MB
178 - 6 -> reserved
179 - 7 -> reserved
206 non-accelerated mode (`noaccel` or `fbset -accel false`), software
221 non-Millennium.
228 with secondary (TV) output - if DFP is active, TV output must be
236 or panel. Default value is now read back from hardware - so you
262 upper:X top boundary: lines between end of VSYNC pulse and start of first
265 pulse. Default is derived from `vesa` option.
266 vslen:X length of VSYNC pulse, in lines. Default is derived from `vesa`
268 left:X left boundary: pixels between end of HSYNC pulse and first pixel.
271 pulse. Default is derived from `vesa` option.
272 hslen:X length of HSYNC pulse, in pixels. Default is derived from `vesa`
276 sync:X sync. pulse - bit 0 inverts HSYNC polarity, bit 1 VSYNC polarity.
307 - SVGALib does not restore screen on exit
308 - generic fbcon-cfbX procedures do not work on Alphas. Due to this,
311 access to `/dev/fb*` - everyone with access to this device can destroy
313 - 24bpp does not support correctly XF-FBDev on big-endian architectures.
314 - interlaced text mode is not supported; it looks like hardware limitation,
316 - Gxx0 SGRAM/SDRAM is not autodetected.
317 - maybe more...
321 - SVGALib does not restore screen on exit.
322 - pixclock for text modes is limited by hardware to
324 - 83 MHz on G200
325 - 66 MHz on Millennium I
326 - 60 MHz on Millennium II
331 pretty effects on screen. Device was not destroyed during tests. :-)
332 - my Millennium G200 oscillator has frequency range from 35 MHz to 380 MHz
334 But Matrox says on product sheet that VCO limit is 50-250 MHz, so I believe
337 - special mixed video/graphics videomodes of Mystique and Gx00 - 2G8V16 and
339 - color keying is not supported
340 - feature connector of Mystique and Gx00 is set to VGA mode (it is disabled
342 - DDC (monitor detection) is supported through dualhead driver
343 - some check for input values are not so strict how it should be (you can
345 - maybe more...
349 - 4bpp is available only on Millennium I and Millennium II. It is hardware
351 - selection between 1:5:5:5 and 5:6:5 16bpp videomode is done by -rgba
352 option of fbset: "fbset -depth 16 -rgba 5,5,5" selects 1:5:5:5, anything
354 - text mode uses 6 bit VGA palette instead of 8 bit (one of 262144 colors
366 faster, it is kernel-space only time on P-II/350 MHz, Millennium I in 33 MHz
412 + secondary head always powerups in 640x480@60-32 videomode. You have to use
418 + if you compiled it as module, you must insert i2c-matroxfb, matroxfb_maven
431 + secondary head always powerups in 640x480@60-32 videomode. You have to use