Re: [Xpert]Help with CyberBladeXPAi1 (Trident) on a Toshiba 1800-814 laptop
Olivier Fourdan writes: Egbert If trident works it is better as it is accelerated. Vesa uses the BIOS and allows mode switching - but it is unacceled. It may still have quirks. fbdev is so simple it should always work - but unaccelerated. I think I may have found something interesting (thus I copy the list ;-) 1) Using Vesa driver works. 2) Passing vga=790 or vga=791 or even vga=792 at linux kernel and using Trident driver *works* but it's very slooow, a lot slower that Vesa driver, in 24bpp and 16bpp -I didn't try 8bpp- Yes, there is no acceleration. We don't get the docs from trident to implement it. Accel in the XP chipset has just changed enough that the accel support for the earlier chips dosn't work any more. 3) Never use vga=xxx and Vesa XFree driver all together. It seems to be dangerous for the LCD display (use either normal textmode with XFree Vesa driver or fb text mode with XFree trident driver, but *not* fb text mode and Vesa driver !) This is surprising! What's puzzling me is why the trident driver with vga=xxx is so slow. I include my XF86Config file so you can check and see by yourself (note that I define all 3 devices, vesa, trident and fbdev and select the one I want by uncommenting the right line in the screen section) For some reason the driver didn't attempt to register mtrr ranges. I'm investigating. Egbert. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Help with CyberBladeXPAi1 (Trident) on a Toshiba 1800-814 laptop
Egbert If trident works it is better as it is accelerated. Vesa uses the BIOS and allows mode switching - but it is unacceled. It may still have quirks. fbdev is so simple it should always work - but unaccelerated. I think I may have found something interesting (thus I copy the list ;-) 1) Using Vesa driver works. 2) Passing vga=790 or vga=791 or even vga=792 at linux kernel and using Trident driver *works* but it's very slooow, a lot slower that Vesa driver, in 24bpp and 16bpp -I didn't try 8bpp- 3) Never use vga=xxx and Vesa XFree driver all together. It seems to be dangerous for the LCD display (use either normal textmode with XFree Vesa driver or fb text mode with XFree trident driver, but *not* fb text mode and Vesa driver !) What's puzzling me is why the trident driver with vga=xxx is so slow. I include my XF86Config file so you can check and see by yourself (note that I define all 3 devices, vesa, trident and fbdev and select the one I want by uncommenting the right line in the screen section) Section ServerLayout Identifier XFree86 Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Section Files FontPath unix/:7100 EndSection # Module loading section Section Module Load dbe # Double-buffering Load GLcore # OpenGL support Load dri # Direct rendering infrastructure Load glx # OpenGL X protocol interface Load extmod # Misc. required extensions # Load v4l # Video4Linux # Load pex5 # PHIGS for X 3D environment (obsolete) # Load record# X event recorder # Load xie # X Image Extension (obsolete) # You only need the following two modules if you do not use xfs. # Load freetype # TrueType font handler # Load type1 # Adobe Type 1 font handler EndSection Section InputDevice Identifier Keyboard0 Driver keyboard Option XkbLayout fr EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Device /dev/mouse Option Protocol PS/2 Option Emulate3Buttons on Option ZAxisMapping 4 5 EndSection Section Monitor Identifier My Monitor VendorName Unknown ModelName Unknown HorizSync 31.5 - 48.5 VertRefresh 50-70 Option dpms EndSection Section Device Identifier * Generic VESA compatible Driver vesa BoardName Unknown Option UseFBDev EndSection Section Device Identifier Linux Frame Buffer Driver fbdev BoardName Unknown EndSection Section Device Identifier Trident Driver trident BoardName Unknown Option NoAccel false Option ShadowFB false BusID PCI:1:0:0 Option CyberStretch false Option CyberShadow true Option ShadowFB true EndSection Section Screen Identifier Screen0 Device * Generic VESA compatible #Device Linux Frame Buffer #Device Trident Monitor My Monitor DefaultDepth 16 Subsection Display Depth 24 Modes 1024x768 800x600 640x480 EndSubSection Subsection Display Depth 16 Modes 1024x768 800x600 640x480 EndSubSection Subsection Display Depth 8 Modes 1024x768 800x600 640x480 EndSubSection EndSection Section DRI Mode 0666 EndSection ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
