linux Framebuffer分类（uvesafb、vesafb、sisfb）

http://blog.csdn.net/tangy110/article/details/6341922

   A framebuffer enables the kernel to display graphics on an otherwise text only console. These drivers can also be used for other things, such as running a non-accelerated X server or playing video in media players with framebuffer support. Framebuffer support is a requirement for applications like Fbsplash andQingy.

 

---

 

uvesafb

Some tinkering is involved to get the uvesafb driver working. You will need to enable Connector - unified userspace <-> kernelspace linker and Userspace VESA VGA graphics support.

Linux Kernel Configuration: uvesafb kernel configuration

Device Drivers ->
	<*> Connector - unified userspace <-> kernelspace linker  --->
	Graphics support ->
		[*] Support for frame buffer devices  --->
			[*] Enable firmware EDID
			...
			<*> Userspace VESA VGA graphics support

Rebuild the kernel, but don't install it just yet. The reason we first needed to build the kernel is that we need klibc to compile against a kernel withConnector - unified userspace <-> kernelspace linker and Userspace VESA VGA graphics support enabled. Next we need the sys-apps/v86d userspace helper,

emerge -av v86d

Now, read the initramfs kernel configuration chapter for instruction on enabling initramfs support, which is needed to include bits of sys-apps/v86d in the kernel. Set the Initramfs source file(s) to /usr/share/v86d/initramfs,

Note: If you need to add v86d to an already existing initramfs source directory, look in /usr/share/v86d/initramfsand copy the files listed there.

Linux Kernel Configuration: uvesafb initramfs configuration

General Setup ->
	(/usr/share/v86d/initramfs) Initramfs source file(s)

Rebuild the kernel yet again and finally install it.

vesafb

The vesafb driver is a generic VESA driver that works with most VESA compatible cards.

Linux Kernel Configuration: vesafb kernel configuration

Device Drivers ->
	<*> Connector - unified userspace <-> kernelspace linker  --->
	Graphics support ->
		[*] Support for frame buffer devices  --->
			[*] Enable firmware EDID
			...
			[*] VESA VGA graphics support

sisfb

For users with a SiS card, you want the sisfb driver.

Linux Kernel Configuration: sisfb kernel configuration

Device Drivers ->
	Graphics support ->
		[*] Support for frame buffer devices  --->
			[*] Enable firmware EDID
			...
			[*] SiS/XGI display support

This driver supports the following SiS cards:

• SiS 300 series: SiS 300/305, 540, 630(S), 730(S)
• SiS 315 series: SiS 315/H/PRO, 55x, (M)65x, 740, (M)661(F/M)X, (M)741(GX)
• SiS 330 series: SiS 330 ("Xabre"), (M)760

Kernel Command Line Options

The kernel will only use the framebuffer if it is specifically told to do so. The required kernel command line option here is video= followed by the desired driver, a set of options, resolution, color depth and refresh rate.

uvesafb

Add to the kernel line of your /boot/grub/grub.conf, substituting the options to your liking,

video=uvesafb:mtrr:3,ywrap,1024x768-24@60

You can also create an entry disabling uvesafb using the following,

video=uvesafb:off

One reason for disabling UVesaFB, is to avoid known conflicts when using the binary NVidia driver with hibernate/suspend feature.

A uvesafb example is shown below, but keep in mind that how the kernel is told to use the framebuffer differs from driver to driver.

File: /boot/grub/grub.conf

...
title=Gentoo Linux
root(hd0,0)
kernel /boot/bzImage root=/dev/hda3 video=uvesafb:ywrap,mtrr:3,1024x768-32@70
...

Here we told the kernel to use the uvesafb driver with the ywrap and mtrr:3 options, set the resolution to 1024x768 with a color depth of 32 bits and a refresh rate of 70Hz.

vesafb

If you use the vesafb driver you will need to omit the resolution, color depth and refresh rate from the video= and follow with a vga= parameter. The vga= takes a decimal value (with no preceding 0x), or ask. Setting vga=ask is a good idea if you are unsure what to use, as the kernel will stop and ask you for the desired resolution and color depth. The Linux video mode numbers can be found here, but you should be aware that these number might not work on your particular hardware. A better way to see the modes you can set is to run:

hwinfo --vbe|grep Mode

So a vesafb example would be,

video=vesafb:mtrr:3,ywrap vga=792

which would be equivalent to a uvesafb of:

video=uvesafb:mtrr:3,ywrap,1024x768-24@60

To create a profile for disabling framebuffer, use either vga=normal or vga=nofb, or just omit vga= entirely.

sisfb

The video= parameter differs from other drivers.

The uvesafb driver entry,

video=uvesafb:ypan,mtrr:3,1024x768-32@70

would, using sisfb be,

video=sisfb:mode:1024x768x32,rate:70,mem:4096

Make sure you set the memory size of your card in KiB using the mem: option.

Other Options

MTRR

The mtrr option defaults to mtrr:0, meaning that MTRR will be disabled — equivalent to the nomtrr option. The safest option is probably to use mtrr:1 and the most optimal option is most likely mtrr:3. The values represent:

0 - Disabled (equivalent to nomtrr) (default)
1 - Uncacheable
2 - Write-back
3 - Write-combining
4 - Write-through

Review the kernel documentation for more information.

ypan, ywrap and redraw

The ypan, ywrap and redraw are scrolling options. They set the way the kernel will handle the scrolling and panning of the framebuffer. If none of these are specified, the redraw option will be used, this is the safest but slowest option. Most modern hardware can handle ywrap, so this is most likely the option you want to use. If that fails you could try ypan, expect flickering using this though.

To clarify, a complete kernel command line in /boot/grub/grub.conf, using the uvesafb driver, with the mtrr:3 and ywrap options using a resolution of 1600x1200, a color depth of 32 bits and a refresh rate of 70 Hz would be:

File: /boot/grub/grub.conf

...
kernel /boot/bzImage root=/dev/hda3 video=uvesafb:1600x1200-32@70,mtrr:3,ywrap
...

Review the Kernel Documentation for more information.