• Home
  • Raw
  • Download

Lines Matching full:not

20  * graphic mode is slower than text mode... but you should not notice
34 box) and matroxfb (for graphics mode). You should not compile-in vesafb
99 head, not even talking about second). Running XFree86 4.x accelerated mga
100 driver is possible, but you must not enable DRI - if you do, resolution and
113 problem and not mine, but I'm not sure.
129 disabled do not load driver; you can use also `off`, but `disabled`
134 noaccel do not use acceleration engine. It does not work on Alphas.
142 not comply to PCI 2.1 specs (it will not guarantee that every
145 novga disables VGA I/O ports. It is default if BIOS did not enable
146 device. You should not use this option, some boards then do not
148 vga preserve state of VGA I/O ports. It is default. Driver does not
149 enable VGA I/O if BIOS did not it (it is not safe to enable it in
151 nobios disables BIOS ROM. It is default if BIOS did not enable BIOS
152 itself. You should not use this option, some boards then do not
154 bios preserve state of BIOS ROM. It is default. Driver does not enable
155 BIOS if BIOS was not enabled before.
158 strange pattern on screen and so on. Devices not enabled by BIOS
225 nocross4MB pixel line must not cross 4MB boundary. It is default for
227 limitations which do not allow this. But this option is
228 incompatible with some (if not all yet released) versions of
257 If you are not satisfied with videomode selected by `vesa` option, you
282 on. Do not forget that if you want sync on green, you also probably
310 - SVGALib does not restore screen on exit
311 - generic fbcon-cfbX procedures do not work on Alphas. Due to this,
312 `noaccel` (and cfb4 accel) driver does not work on Alpha. So everyone
316 - 24bpp does not support correctly XF-FBDev on big-endian architectures.
317 - interlaced text mode is not supported; it looks like hardware limitation,
318 but I'm not sure.
319 - Gxx0 SGRAM/SDRAM is not autodetected.
324 - SVGALib does not restore screen on exit.
331 Because I have no access to other devices, I do not know specific
332 frequencies for them. So driver does not check this and allows you to
334 pretty effects on screen. Device was not destroyed during tests. :-)
341 G16V16 are not supported
342 - color keying is not supported
346 - some check for input values are not so strict how it should be (you can
370 PCI slot, G200 in AGP 2x slot. I did not test vgacon::
407 + secondary head shares videomemory with primary head. It is not problem
410 is not possible).
413 + secondary head is not accelerated. There were bad problems with accelerated
420 + kernel is not fully multihead ready. So some things are impossible to do.
428 + secondary head shares videomemory with primary head. It is not problem
433 + secondary head is not accelerated.
436 + TV output is not supported
437 + kernel is not fully multihead ready, so some things are impossible to do.