Gecko [ lorencats.com ]

Name	Size	Permission
api.txt.gz	3.81 KB	-rw-r--r--
arkfb.txt	1.98 KB	-rw-r--r--
aty128fb.txt	2.07 KB	-rw-r--r--
cirrusfb.txt	1.89 KB	-rw-r--r--
cmap_xfbdev.txt	1.88 KB	-rw-r--r--
deferred_io.txt	2.96 KB	-rw-r--r--
efifb.txt	593 B	-rw-r--r--
ep93xx-fb.txt.gz	1.68 KB	-rw-r--r--
fbcon.txt.gz	4.27 KB	-rw-r--r--
framebuffer.txt.gz	4.84 KB	-rw-r--r--
gxfb.txt	1.19 KB	-rw-r--r--
imacfb.txt	600 B	-rw-r--r--
intel810.txt.gz	3.48 KB	-rw-r--r--
intelfb.txt	3.66 KB	-rw-r--r--
internals.txt	2.58 KB	-rw-r--r--
lxfb.txt	1.19 KB	-rw-r--r--
matroxfb.txt.gz	7.02 KB	-rw-r--r--
metronomefb.txt	1.95 KB	-rw-r--r--
modedb.txt.gz	2.87 KB	-rw-r--r--
pvr2fb.txt	2.19 KB	-rw-r--r--
pxafb.txt.gz	2.1 KB	-rw-r--r--
s3fb.txt	2.55 KB	-rw-r--r--
sa1100fb.txt	1.34 KB	-rw-r--r--
sh7760fb.txt.gz	1.95 KB	-rw-r--r--
sisfb.txt.gz	2.73 KB	-rw-r--r--
sm501.txt	290 B	-rw-r--r--
sm712fb.txt	752 B	-rw-r--r--
sstfb.txt.gz	3.19 KB	-rw-r--r--
tgafb.txt	2.37 KB	-rw-r--r--
tridentfb.txt	2.59 KB	-rw-r--r--
udlfb.txt.gz	3.09 KB	-rw-r--r--
uvesafb.txt.gz	2.83 KB	-rw-r--r--
vesafb.txt.gz	2.77 KB	-rw-r--r--
viafb.txt.gz	3.07 KB	-rw-r--r--
vt8623fb.txt	1.8 KB	-rw-r--r--

Code Editor : tridentfb.txt

Tridentfb is a framebuffer driver for some Trident chip based cards.

The following list of chips is thought to be supported although not all are
tested:

those from the TGUI series 9440/96XX and with Cyber in their names
those from the Image series and with Cyber in their names
those with Blade in their names (Blade3D,CyberBlade...)
the newer CyberBladeXP family

All families are accelerated. Only PCI/AGP based cards are supported,
none of the older Tridents.
The driver supports 8, 16 and 32 bits per pixel depths.
The TGUI family requires a line length to be power of 2 if acceleration
is enabled. This means that range of possible resolutions and bpp is
limited comparing to the range if acceleration is disabled (see list
of parameters below).

Known bugs:
1. The driver randomly locks up on 3DImage975 chip with acceleration
   enabled. The same happens in X11 (Xorg).
2. The ramdac speeds require some more fine tuning. It is possible to
   switch resolution which the chip does not support at some depths for
   older chips.

How to use it?
==============

When booting you can pass the video parameter.
video=tridentfb

The parameters for tridentfb are concatenated with a ':' as in this example.

video=tridentfb:800x600-16@75,noaccel

The second level parameters that tridentfb understands are:

noaccel - turns off acceleration (when it doesn't work for your card)

fp	- use flat panel related stuff
crt 	- assume monitor is present instead of fp

center 	- for flat panels and resolutions smaller than native size center the
	  image, otherwise use
stretch

memsize - integer value in KB, use if your card's memory size is misdetected.
	  look at the driver output to see what it says when initializing.

memdiff - integer value in KB, should be nonzero if your card reports
	  more memory than it actually has. For instance mine is 192K less than
	  detection says in all three BIOS selectable situations 2M, 4M, 8M.
	  Only use if your video memory is taken from main memory hence of
	  configurable size. Otherwise use memsize.
	  If in some modes which barely fit the memory you see garbage
	  at the bottom this might help by not letting change to that mode
	  anymore.

nativex - the width in pixels of the flat panel.If you know it (usually 1024
	  800 or 1280) and it is not what the driver seems to detect use it.

bpp	- bits per pixel (8,16 or 32)
mode	- a mode name like 800x600-8@75 as described in
	  Documentation/fb/modedb.txt

Using insane values for the above parameters will probably result in driver
misbehaviour so take care(for instance memsize=12345678 or memdiff=23784 or
nativex=93)

Contact: jani@astechnix.ro

${this.title}

Code Editor : tridentfb.txt