 |
|
 |
|
 |
| Framebuffer HOWTO英文 |
热 ★★★★ |
| Framebuffer HOWTO英文 |
|
作者：4Lzx.com 文章来源：bbs.4Lzx.com 点击数： 更新时间：2005-9-4 18:51:58  |
file to enable the pm2fb device. The quickest and simplest way is re-use the following
# LILO configuration fileboot = /dev/hda3delay = 30 promptvga = 792 # You need to do this so it boots up in a sane state# Linux bootable partition config beginsimage = /vmlinuz append = "video=pm2fb:mode:1024x768-75,font:SUN12x22,ypan" # then switch to pm2fb root = /dev/hda3 label = Linux read-only # Non-UMSDOS filesystems should be mounted read-only for checking
The line "pm2fb:mode:1024x768-75,font:SUN12x22,ypan" indicates you are selectinga 1024x768 mode at 75Hz, with the SUN12x22 font selected (if you did select it),including ypan for scrollback support. You may select other modes if you desire.
Lastly, you'll need to create the framebuffer device in /dev. You need one perframebuffer device, so all you need to do is to type in mknod /dev/fb0 c 29 0for the first one. Subsequent ones would be in multiples of 32, so for exampleto create /dev/fb1, you would need to type in mknod /dev/fb1 c 29 32, and so onup to the eight framebuffer device (mknod /dev/fb7 c 29 224)
For more information on the other features of the Permedia framebuffer driver, point your browser at:
http://www.cs.unibo.it/~nardinoc/pm2fb/index.html
video=pm2fb:[option[,option[,option...]]]
where option is one of the following
* off to disable the driver.
* mode:resolution to set the console resolution. The modes have beentaken from the fb.modes.ATI file in Geert's fbset package. The depth forall the modes is 8bpp. This is the list of the available modes:
o 640x480-(60,72,75,90,100)
o 800x600-(56,60,70,72,75,90,100)
o 1024x768-(60,70,72,75,90,100,illo) illo=80KHz 100Hz
o 1152x864-(60,70,75,80)
o 1280x1024-(60,70,74,75)
o 1600x1200-(60,66,76)
* The default resolution is 640x480-60.
* font:font name to set the console font. Example: font:SUN12x22
* ypan sets the current virtual height as big as video memory size permits.
* oldmem this option is for CybervisionPPC users only. Specify this ifyour board has Fujitsu SGRAMs mounted on (all CVisionPPCs before 30-Dec-1998).
* virtual (temporary) specify this if the kernel remaps the PCI regionson your platform.
5.6 Got a ATI card?
[Note: This information is at best, only second-hand or third-hand, since I don't have an ATI card to test it with. Feel free to correct me if I am wrong or flame me!] 8)
ATI cards can be used with the vesafb driver, but you may or may not have problems, depending on how horribly broken the card is. Fortunately, there is the atyfb framebuffer driver available to use. Assuming you are using menuconfig, do the following:
Go into the Code Maturity Level menu, and enable the prompt fordevelopment and/or incomplete drivers [note this may change for futurekernels - when this happens, this HOWTO will be revised]
Go into the Console Drivers menu and select the following:
* VGA Text Console
* Video Selection Support
* Support for frame buffer devices (experimental)
* ATI Mach64 display support
* Advanced Low Level Drivers
* Select Mono, 2bpp, 4bpp, 8bpp, 16bpp, 24bpp and 32bpp packed pixel drivers
* Optionally, select the following, if you wish to use the compiled in fonts
o Select compiled-in fonts
o Select Sparc console 12x22 font
Rebuild your kernel. Then you will need to modify your lilo.conf file toenable the atyfb device. The quickest and simplest way is re-use the following
# LILO configuration fileboot = /dev/hda3delay = 30promptvga = 792 # You need to do this so it boots up in a sane state# Linux bootable partition config beginsimage = /vmlinuz append = "video=atyfb:mode:1024x768,font:SUN12x22" root = /dev/hda3 label = Linux read-only # Non-UMSDOS filesystems should be mounted read-only for checking
The line "atyfb:mode:1024x768,font:SUN12x22" indicates you are selectinga 1024x768 mode.
Lastly, you'll need to create the framebuffer device in /dev. You need one perframebuffer device, so all you need to do is to type in mknod /dev/fb0 c 29 0for the first one. Subsequent ones would be in multiples of 32, so for exampleto create /dev/fb1, you would need to type in mknod /dev/fb1 c 29 32, and so onup to the eight framebuffer device (mknod /dev/fb7 c 29 224)
video=atyfb:[option[,option[,option...]]]
where option is one of the following
* font:STRING selects the built-in font (compiled into the kernel)
* noblink Turns off blinking
* noaccel Disables acceleration
* vram:ULONG Tells the atyfb driver how much memory you have
* pll:ULONG Unknown
* mclk:ULONG Unknown
* vmode:ULONG Unknown
* cmode:ULONG - sets depth - 0, 8, 15, 16, 24 and 32
5.7 Which graphic cards are VESA 2.0 compliant?
This lists all the graphic cards that are known to work with the vesafbdevice:
* ATI PCI VideoExpression 2MB (max. 1280x1024 @ 8bit)
* ATI PCI All-in-Wonder
* Matrox Millennium PCI - BIOS v3.0
* Matrox Millennium II PCI - BIOS v1.5
* Matrox Millennium II AGP - BIOS v1.4
* Matrox Millennium G200 AGP - BIOS v1.3
* Matrox Mystique & Mystique 220 PCI - BIOS v1.8
* Matrox Mystique G200 AGP - BIOS v1.3
* Matrox Productiva G100 AGP - BIOS v1.4
* All Riva 128 based cards
* Diamond Viper V330 PCI 4MB
* Genoa Phantom 3D/S3 ViRGE/DX
* Hercules Stingray 128/3D with TV output
* Hercules Stingray 128/3D without TV output - needs BIOS upgrade(free from support@hercules.com)
* SiS 6326 PCI/AGP 4MB
* STB Lightspeed 128 (Nvida Riva 128 based) PCI
* STB Velocity 128 (Nvida Riva 128 based) PCI
* Jaton Video-58P ET6000 PCI 2MB-4MB (max. 1600x1200 @ 8bit)
* Voodoo2 2000
This list is composed of on-board chipsets on systems' motherboards:
* Trident Cyber9397
* SiS 5598
This list below blacklists graphic cards that doesn't work with the vesafbdevice:
* TBA
5.8 Can I make vesafb as a module?
As far as is known, vesafb can't be modularised, although at some pointin time, the developer of vesafb may decide to modify the sources formodularising. Note that even if modularising is possible, at boot timeyou will not be able to see any output on the display until vesafb ismodprobed. It's probably a lot wiser to leave it in the kernel, forthese cases when there are booting problems.
5.9 How do I modify the cursor?
[Taken from VGA-softcursor.txt - thanks Martin Mares!]
Linux now has some ability to manipulate cursor appearance. Normally,you can set the size of hardware cursor (and also work around some uglybugs in those miserable Trident cards--see #define TRIDENT_GLITCH indrivers/char/ vga.c). In case you enable "Software generated cursor" inthe system configuration, you can play a few new tricks: you can makeyour cursor look like a non-blinking red block, make it inversebackground of the character it's over or to highlight that character andstill choose whether the original hardware cursor should remain visibleor not. There may be other things I have never thought of.
The cursor appearance is controlled by a
<ESC>[?1;2;3c
escapesequence where 1, 2 and 3 are parameters described below. If you omit anyof them, they will default to zeroes.
Parameter 1 specifies cursor size (0=default, 1=invisible, 2=underline,..., 8=full block) + 16 if you want the software cursor to be applied + 32if you want to always change the background colour + 64 if you dislikehaving the background the same as the foreground. Highlights are ignoredfor the last two flags.
The second parameter selects character attribute bits you want to change(by simply XORing them with the value of this parameter). On standard VGA,the high four bits specify background and the low four the foreground. Inboth groups, low three bits set colour (as in normal colour codes used bythe console) and the most significant one turns on highlight (or sometimesblinking--it depends on the configuration of your VGA).
The third parameter consists of character attribute bits you want to set.Bit setting takes place before bit toggling, so you can simply clear a bitby including it in both the set mask and the toggle mask.
To get normal blinking underline, use: echo -e '\033[?2c'To get blinking block, use: echo -e '\033[?6c'To get red non-blinking block, use: echo -e '\033[?17;0;64c'
6. Using framebuffer devices on Atari m68k platforms
This section describes framebuffer options on Atari m68k platforms.
6.1 What modes are available on Atari m68k platforms?
Colours 320x200 320x480 640x200 640x400 640x480 896x608 1280x960--------+--------------------------------------------------------- 1 bit | sthigh vga2 falh2 tthigh 2 bits | stmid vga4 4 bits | stlow ttmid/vga16 falh16 8 bits | ttlow vga256
ttlow, ttmid and tthigh are only used by the TT, whilst vga2,vga4, vga15, vga256, falh3 and falh16 are only used by the Falcon.
When used with the kernel option video=xxx, and no suboption isgiven, the kernel will probe for the modes in the following order untilit finds a mode that is possible with the given hardware:
* ttmid
* tthigh
* vga16
* sthigh
* stmid
You may specify the particular mode you wish to use, if you don't wish toauto-probe for the modes you desire. For example, video=vga16 givesyou a 4 bit 640x480 display.
6.2 Additional suboptions on Atari m68k platforms
There are a number of suboptions avail上一页 [1] [2] [3] [4] [5] [6] [7] 下一页 |
| 学院录入：4Lzx.com 责任编辑：4Lzx.com |
|
上一篇学院： FRramebuffer HOWTO英文(续)
下一篇学院： 在Linux下安装Oracle Database 9i |
| 【字体：小 大】【发表评论】【加入收藏】【告诉好友】【打印此文】【关闭窗口】 |
 网友评论：（评论内容只代表网友观点，与本站立场无关！） |
| |
|
 |
|
|
