Lines Matching +full:secondary +full:- +full:device
16 * Most important: boot logo :-)
34 box) and matroxfb (for graphics mode). You should not compile-in vesafb
35 unless you have primary display on non-Matrox VBE2.0 device (see
43 -------------
58 -------------------------
73 ----------
86 Non-listed number can be achieved by more complicated command-line, for
93 XF{68,86}_FBDev should work just fine, but it is non-accelerated. On non-intel
97 Running another (accelerated) X-Server like XF86_SVGA works too. But (at least)
100 driver is possible, but you must not enable DRI - if you do, resolution and
110 2,3,7,0x108-0x10C or 0x1C0. At runtime, `fbset -depth 0` does this work.
128 memory usable for on-screen display (i.e. max. 8 MB).
141 it is autodetected for intel's 82437. In this case device does
146 device. You should not use this option, some boards then do not
160 init driver initializes every device it knows about.
165 - 0 -> 2x128Kx32 chips, 2MB onboard, probably sgram
166 - 1 -> 2x128Kx32 chips, 4MB onboard, probably sgram
167 - 2 -> 2x256Kx32 chips, 4MB onboard, probably sgram
168 - 3 -> 2x256Kx32 chips, 8MB onboard, probably sgram
169 - 4 -> 2x512Kx16 chips, 8/16MB onboard, probably sdram only
170 - 5 -> same as above
171 - 6 -> 4x128Kx32 chips, 4MB onboard, probably sgram
172 - 7 -> 4x128Kx32 chips, 8MB onboard, probably sgram
174 - 0 -> 2x512Kx16 SDRAM, 16/32MB
175 - 2x512Kx32 SGRAM, 16/32MB
176 - 1 -> 2x256Kx32 SGRAM, 8/16MB
177 - 2 -> 4x128Kx32 SGRAM, 8/16MB
178 - 3 -> 4x512Kx32 SDRAM, 32MB
179 - 4 -> 4x256Kx32 SGRAM, 16/32MB
180 - 5 -> 2x1Mx32 SDRAM, 32MB
181 - 6 -> reserved
182 - 7 -> reserved
203 dev:X bind driver to device X. Driver numbers device from 0 up to N,
204 where device 0 is first `known` device found, 1 second and so on.
206 Default is `every` known device.
209 non-accelerated mode (`noaccel` or `fbset -accel false`), software
224 non-Millennium.
231 with secondary (TV) output - if DFP is active, TV output must be
239 or panel. Default value is now read back from hardware - so you
245 secondary analog output and third letter to the DVI output.
279 sync:X sync. pulse - bit 0 inverts HSYNC polarity, bit 1 VSYNC polarity.
310 - SVGALib does not restore screen on exit
311 - generic fbcon-cfbX procedures do not work on Alphas. Due to this,
314 access to `/dev/fb*` - everyone with access to this device can destroy
316 - 24bpp does not support correctly XF-FBDev on big-endian architectures.
317 - interlaced text mode is not supported; it looks like hardware limitation,
319 - Gxx0 SGRAM/SDRAM is not autodetected.
320 - maybe more...
324 - SVGALib does not restore screen on exit.
325 - pixclock for text modes is limited by hardware to
327 - 83 MHz on G200
328 - 66 MHz on Millennium I
329 - 60 MHz on Millennium II
334 pretty effects on screen. Device was not destroyed during tests. :-)
335 - my Millennium G200 oscillator has frequency range from 35 MHz to 380 MHz
337 But Matrox says on product sheet that VCO limit is 50-250 MHz, so I believe
340 - special mixed video/graphics videomodes of Mystique and Gx00 - 2G8V16 and
342 - color keying is not supported
343 - feature connector of Mystique and Gx00 is set to VGA mode (it is disabled
345 - DDC (monitor detection) is supported through dualhead driver
346 - some check for input values are not so strict how it should be (you can
348 - maybe more...
352 - 4bpp is available only on Millennium I and Millennium II. It is hardware
354 - selection between 1:5:5:5 and 5:6:5 16bpp videomode is done by -rgba
355 option of fbset: "fbset -depth 16 -rgba 5,5,5" selects 1:5:5:5, anything
357 - text mode uses 6 bit VGA palette instead of 8 bit (one of 262144 colors
369 faster, it is kernel-space only time on P-II/350 MHz, Millennium I in 33 MHz
407 + secondary head shares videomemory with primary head. It is not problem
411 + due to hardware limitation, secondary head can use only 16 and 32bpp
413 + secondary head is not accelerated. There were bad problems with accelerated
414 XFree when secondary head used to use acceleration.
415 + secondary head always powerups in 640x480@60-32 videomode. You have to use
417 + secondary head always powerups in monitor mode. You have to use fbmatroxset
421 + if you compiled it as module, you must insert i2c-matroxfb, matroxfb_maven
428 + secondary head shares videomemory with primary head. It is not problem
431 + due to hardware limitation, secondary head can use only 16 and 32bpp
433 + secondary head is not accelerated.
434 + secondary head always powerups in 640x480@60-32 videomode. You have to use