> /op/spa14. /op/form4. /opa > /o href="../linux+v3.7.5/Documentav3.1/fb/sisfb.txt">> /opimg src="../.stav3c/gfx/right.png" alt=">>">> p/spa14.> pspa1 class="lxr_search">> > /opinput typ> /opinput typ> /opbutt> typSearch 4. /op/form4. p/spa14.> pspa1 class="lxr_prefs"4. /opa href="+prefs?return=Documentav3.1/fb/sisfb.txt"> /o onclick="return ajax_prefs();">> /oPrefs. /op/a>> p/spa14. /o op/div4. /o opform acv3.1="ajax+*" method="post" onsubmit="return false;">> pinput typ> /o op/form4.> /o opdiv class="headingbott>m">o o1p/a>>o o2p/a>What is sisfb?>o o3p/a>==============>o o4p/a>>o o5p/a>sisfb is a fram Integrated Systems)>o o6p/a>graphics chips. Supported are:>o o7p/a>>o o8p/a>- SiS 300 series: SiS 300/305, 540, 630(S), 730(S)>o o9p/a>- SiS 315 series: SiS 315/H/PRO, 55x, (M)65x, 740, (M)661(F/M)X, (M)741(GX)>o > a>- SiS 330 series: SiS 330 ("Xabre"), (M)760>o 11p/a>>o 12p/a>>o 13p/a>Why do I need a framo 14p/a>===================================>o 15p/a>>o 16p/a>sisfb is eg. useful if you want a high-resoluon> text c> sole. Besides that,>o 17p/a>sisfb is required to run DirectFB (which c>mes with a1 addiv3.1al, dedicated>o 18p/a>driver for the 315 series).>o 19p/a>>o 2 > a>On the 300 series, sisfb on kernels older tha1 20 3 furthermore plays an>o 21p/a>important role in c> necv3.1 with DRM/DRI: Sisfb manages the memory heap>o 22p/a>used by DRM/DRI for 3D texture and other data. This memory management is>o 23p/a>required for using DRI/DRM.>o 24p/a>>o 25p/a>Kernels >= around 20 3 do not need sisfb any longer for DRI/DRM memory>o 26p/a>management. The SiS DRM driver has been updated and features a memory manager>o 27p/a>of its own (which will be used if sisfb is not c>mpiled). So unless you want>o 28p/a>a graphical c> sole, you don't need sisfb on kernels >=20 3.>o 29p/a>>o 3 > a>Sidenote: Since this seems to be a c>mmonly made mistake: sisfb and vesafb>o 31p/a>cannot be acv3ve at the sam< time! Do only select one of them in your kernel>o 32p/a>c> figurav3.1.>o 33p/a>>o 34p/a>>o 35p/a>How are paramo 36p/a>===================================>o 37p/a>>o 38p/a>Well, it depends: If c>mpiled stav3cally into the kernel, use lilo's append>o 39p/a>stavement to add the parammmand line. Please see lilo's>o 4 > a>(or GRUB's) documentav3.1 for more informav3.1. If sisfb is a kernel module,>o 41p/a>parammmand.>o 42p/a>>o 43p/a>Example for sisfb as part of the stav3c kernel: Add the following line to your>o 44p/a>lilo.c> f:>o 45p/a>>o 46p/a> /o oappend="video=sisfb:mode:1024x768x16,mem:12288,rate:75">o 47p/a>>o 48p/a>Example for sisfb as a module: Start sisfb by typing>o 49p/a>>o 50p/a> /o omodprobe sisfb mode=1024x768x16 rate=75 mem=12288>o 51p/a>>o 52p/a>A c>mmon mistake is that folks use a wrong paramo 53p/a>driver c>mpiled into the kernel. Please note: If c>mpiled into the kernel,>o 54p/a>the paramo 55> a>(or whatever mode you want to use, alternav3vely using any other formav>o 56p/a>described above or the vesa keyword instead of mode). If c>mpiled as a module,>o 57p/a>the paramo 58p/a>want to use). Using a "=" for a ":" (and vice versa) is a huge difference!>o 59p/a>Addiv3.1ally: If you g3ve more tha1 one argument to the in-kernel sisfb, the>o 60p/a>arguments are separated with ",". For example:>o 61p/a>>o 62p/a> /ovideo=sisfb:mode:1024x768x16,rate:75,mem:12288>o 63p/a>>o 64p/a>>o 65p/a>How do I use it?>o 66p/a>================>o 67p/a>>o 68p/a>Preface stavement: This file only covers very little of the driver's>o 69p/a>capabilities and features. Please refer to the author's and maintainer's>o 70p/a>website at p/a>for more>o 71p/a>informav3.1. Addiv3.1ally, "modinfo sisfb" g3ves an overview over all>o 72p/a>supported v3.1s including some explanav3.1.>o 73p/a>>o 74p/a>The desired display mode can be specified using the keyword "mode" with>o 75p/a>a paramo 76p/a> /- XxYxDepth or>o 77p/a> /- XxY-Depth or>o 78p/a> /- XxY-Depth@Rave or>o 79p/a> /- XxY>o 80p/a> /- or simply use the VESA mode number in hexadecimal or decimal.>o 81p/a>>o 82p/a>For example: 1024x768x16, 1024x768-16@75, 1280x1024-16. If no depth is>o 83p/a>specified, it defaults to 8. If no rate is g3ve1, it defaults to 60Hz. Depth 32>o 84p/a>mea1s 24bit c>lor depth (but 32 bit framo 85p/a>to the user).>o 86p/a>>o 87p/a>Addiv3.1ally, sisfb understands the keyword "vesa" followed by a VESA mode>o 88p/a>number in decimal or hexadecimal. For example: vesa=791 or vesa=0x117. Please>o 89p/a>use either "mode" or "vesa" but not both.>o 90p/a>>o 91p/a>Linux 2.4 only: If no mode is g3ve1, sisfb defaults to "no mode" (mode=none) if>o 92p/a>c>mpiled as a module; if sisfb is stav3cally c>mpiled into the kernel, it>o 93p/a>defaults to 800x600x8 unless CRT2 typ< is LCD, in which case the LCD's nav3ve>o 94p/a>resoluon> is used. If you want to switch to a different mode, use the fbset>o 95p/a>shell c>mmand.>o 96p/a>>o 97p/a>Linux 2.6 only: If no mode is g3ve1, sisfb defaults to 800x600x8 unless CRT2>o 98p/a>typ< is LCD, in which case it defaults to the LCD's nav3ve resoluon> . If>o 99p/a>you want to switch to another mode, use the stty shell c>mmand.>o100p/a>>o101p/a>You should c>mpile in both vgac> (to boot if you remove you SiS card from>o102p/a>your system) and sisfb (for graphics mode). Under Linux 2.6, also "Framo103p/a>c> sole support" (fbc> ) is needed for a graphical c> sole.>o104p/a>>o105p/a>You should *not* c>mpile-in vesafb. And please do not use the "vga=" keyword>o106p/a>in lilo's or grub's c> figurav3.1 file; mode selectn> is done using the>o107p/a>"mode" or "vesa" keywords as a paramo108p/a>>o109p/a>>o1 > a>X11>o111p/a>===>o112p/a>>o113p/a>If using XFree86 or, it is rec>mmended that you don't use the "fbdev">o114p/a>driver but the dedicated "sis" X driver. The "sis" X driver and sisfb are>o115p/a>developed by the sam< pers> (Thomas Winischhofer) and cooperate well with>o116p/a>each other.>o117p/a>>o118p/a>>o119p/a>SVGALib>o12 > a>=======>o121p/a>>o122p/a>SVGALib, if directly accessing the hardware, never restores the screen>o123p/a>c>rrectly, especially > laptops or if the output devices are LCD or TV.>o124p/a>Therefore, use the chipset "FBDEV" in SVGALib c> figurav3.1. This will make>o125p/a>SVGALib use the framo126p/a>>o127p/a>>o128p/a>C> figurav3.1>o129p/a>=============>o130p/a>>o131p/a>(Some) accepted v3.1s:>o132p/a>>o133p/a>off /o o- Disable sisfb. This tion> is tnly understood if sisfb is>o134p/a> in-kernel, not a module.>o135p/a>mem:X/o o- size of memory for the c> sole, rest will be used for DRI/DRM. X>o136p/a> is in kilobytes. On 300 series, the default is 4096, 8192 or>o137p/a> 16384 (each in kilobyte) depending > how much video ram the card>o138p/a> has. On 315/330 series, the default is the maximum available ram>o139p/a> (since DRI/DRM is not supported for these chipsets).>o14 > a>noaccel o- do not use 2D accelerav3.1 engine. (Default: use accelerav3.1)>o141p/a>noypa1 o- disable y-pa1ning and scroll by redrawing the entire screen.>o142p/a> This is much slower tha1 y-pa1ning. (Default: use y-pa1ning)>o143p/a>vesa:X/o - selects startup videomode. X is number from 0 to 0x1FF and>o144p/a> represents the VESA mode number (can be g3ve1 in decimal or>o145p/a> hexadecimal form, the latter prefixed with "0x").>o146p/a>mode:X/o - selects startup videomode. Please see above for the formav of>o147p/a> "X".>o148p/a>>o149p/a>Boolean o v3.1s such as "noaccel" or "noypa1" are to be g3ve1 without a>o150p/a>paramo151p/a>sisfb is a module, these are to be set to 1 (for example "modprobe sisfb>o152p/a>noypa1=1").>o153p/a>>o154p/a>-->o155> a>Thomas Winischhofer <>>o156p/a>May 27, 2004>o157p/a>>o158p/a>>o159p/a> The original LXR software by the LXR c>mmunityp/a>, this experimental vers3.1 by lxr@linux.nop/a>. p/div4.pdiv class="subfooter"> kindly hosted by Redpill Linpro ASp/a>, provider of Linux c> sulting and operat3.1s services since 1995. p/div4. p/body4.p/html4.