 |
|
 |
|
 |
| Framebuffer HOWTO英文 |
热 ★★★★ |
| Framebuffer HOWTO英文 |
|
作者：4Lzx.com 文章来源：bbs.4Lzx.com 点击数： 更新时间：2005-9-4 18:51:58  |
on to use the PROM to output characters to the display orto a serial console.
Also, have a look at the Sparc Frame Buffer FAQ at
http://c3-a.snvl1.sfba.home.com/Framebuffer.html
11.2 Configuring the framebuffer devices
During make config, you need to choose whether to compile promconand/or fbcon. You can select both, but if you do this, you will needto set the kernel flags to select the device. fbcon always takesprecedence if not set. If promcon is not selected in, on boot up, itdefaults to dummycon. If promcon is selected, it will use thisdevice. Once the buses are booted, and fbcon is compiled in, thekernel probes for the above framebuffers and will use fbcon. If thereis no framebuffer devices, it will default to promcon.
Here are the kernel options
video=sbus:options where options is a comma separated list: nomargins sets margins to 0,0 margins=12x24 sets margins to 12,24 (default is computedfrom resolution) off don't probe for any SBus/UPA framebuffers font=SUN12x22 use a specific font
So for example, booting with
video=sbus:nomargins,font=SUN12x22
gives you a nice fast text console with a text resolution of96x40, looks similar to a Solaris console but with colours and virtualterminals just like on the Intel platform.
If you want to use the SUN12x22 font, you need to enable it duringmake config (disable the fontwidth != 8 option). The acceleratedframebuffers can support any font width between 1 to 16 pixels, whilstdumb frame buffers only supports 4, 8, 12 and 16 pixel font widths.
It is recommended that you grab a recent consoletools packages.
12. Using framebuffer devices on MIPS platforms
There is no need to change anything for this platform, this is all handledfor you automatically. Indys in particular are hardwired to use a consolesize of 160x64. However, moves are afoot to rewrite the console code forthese Indys, so keep an eye on this section.
13. Using framebuffer devices on ARM platforms
13.1 Netwinders
For the Netwinders (which uses the ARM SA110 RISC chip - a lovely British processor), there are two versions of the Cyber2000 framebuffer driver -one for 2.0.x kernels and one for 2.2.x kernels. It is quite straightforwardto enable and use this driver on both kernels, however, the older version ishardcoded for depth and resolution (blech), but the good news is that the newerversion in the 2.2.x kernels is much more flexible, but currently in a stateof flux as it is still in development. To get this up and running, your best bet is to read the documentation that comes with the ARM port of the kernelsources.
The Netwinders uses a VGA compatible chipset, but unfortunately noone has ported vgafb to it yet. That might happen if someone has some time on their hands. [I would do it if someone would give me a NetWinder to play with]
13.2 Acorn Archimedes
Acorns have always had framebuffer support since the Linux 1.9.x days. However the Acornfb driver in 2.2.x is totally new since the generic framebuffer interface changed during the development of 2.1.x kernels (which, of course, became 2.2.x). As previously, it is a simple matter to activate the driver andset depths and resolutions.
13.3 Other ARM ports (SA 7110s et. al)
Surprisingly, there is even a framebuffer driver for the Psion 5 and the Geofox!I have been told that it displays the Penguin quite well. [Someone please donateme a Psion 5!]
14. Using multi-headed framebuffers
This part of the document was very kindly donated by Frederick A. Niles,who retains all rights to the information contained herewith this section of the HOWTO.
14.1 Introduction
The main goal of this document is to get you started with running adual head configuration of Linux. While this process is prettystraight forward there are numerous things that one can do wrongalong the way.
The example I concentrate on is getting an X-server running on asecond monitor. I find this nice as you can usually find old large19" to 21" fixed frequency monitors around that people are givingaway because they can't use them. This way you can boot off a smallmultisync and then use X on a nice big monitor.
Please understand dual head support is currently developing so thisinformation changes rapidly. Anything in this document could be outof date or just plain incorrect by the time you are reading this.
** WARNING ** This document was written before any XFree86 4.0release. If you are reading this and XFree86 4.0 is alreadyreleased many things may have changed. Try getting a newer versionof this document if it's available.
14.2 Feedback
Feedback is most certainly welcome for this document. Without yoursubmissions and input, this document wouldn't exist. So, please postyour additions, comments and criticisms to:Frederick.A.Niles@gsfc.nasa.gov.
14.3 Contributors
The following people have contributed to this mini-HOWTO.
* Petr Vandrovec vandrove@vc.cvut.cz
* Andreas Ehliar ehliar@lysator.liu.se (x2x)
* Marco Bizzarri m.bizzarri@icube.it (multiple X servers)
14.4 Standard Disclaimer
No liability for the contents of this document can be accepted. Usethe concepts, examples and other content at your own risk. As thisis a new edition of this document, there may be errors andinaccuracies that could be damaging to your system. Proceed withcaution, and although this is highly unlikely, I don't take anyresponsibility for that.
14.5 Copyright Information
This section of the document is copyrighted (c)1999 Frederick Niles and distributedunder the following terms:
* Linux HOWTO documents may be reproduced and distributed in whole orin part, in any medium physical or electronic, as long as thiscopyright notice is retained on all copies. Commercialredistribution is allowed and encouraged; however, the author wouldlike to be notified of any such distributions.
* All translations, derivative works, or aggregate worksincorporating any Linux HOWTO documents must be covered under thiscopyright notice. That is, you may not produce a derivative workfrom a HOWTO and impose additional restrictions on itsdistribution. Exceptions to these rules may be granted undercertain conditions; please contact the Linux HOWTO coordinator atthe address given below.
* If you have questions, please contact, the Linux HOWTO coordinator,at linux-howto@sunsite.unc.edu
14.6 What hardware is supported?
Most video cards assume they will be the only one in the system and arepermanently set with the addressing of the primary display adapter. Thereare a few exceptions.
* Matrox cards: This includes Matrox Millennium, Matrox Millennium II,Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, MatroxMystique G200, Matrox Millennium G200 and Matrox Marvel G200video cards
* MDA: This includes monochrome Hercules graphics adapter among others.This for text only second head support.
Note: it's only the second adapter that has to be one of the above.
14.7 Commercial support
This mini-HOWTO in primarily concerned with free software. However,there are commercial X servers with multi-head support. Theseinclude Metro Link's (www.metrolink.com) Metro-X and Xi Graphics'(www.xig.com) Accelerated-X.
14.8 Getting all the stuff.
You'll need the following patches and programs:
* "fbset" programtry:
http://www.cs.kuleuven.ac.be/~geert/bin/
(note: this program comes with RedHat 6.0)
* "fbaddon" Matrox dual head patches for Linux kerneltry:
ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/
* "con2fb" programtry:
ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/
* The X11 frame buffer server XF86_FBDev. This is a standardpart of XFree86 3.3.1.
14.9 Getting Started
The first thing you'll need to do is to patch a copy of the Linuxsource with the "fbaddon" patch. Then you need to configure thekernel and turn on frame buffer support. If you have Matrox cardsturn on Matrox unified accelerated driver support as well as theparticular type of card you have. Don't turn on VESA frame buffersupport. It can cause a conflict. Do turn on multi-head support(obviously). Build the kernel and reboot.
Now you need to install the "fbset" program and carefully read allthe documentation on how to adjust the settings. Using a"/etc/fb.modes" file is highly recommended once you've decided onyour settings. The fbset program includes a Perl script to convertyour XF86Config file to fb.modes settings. I've included myoctave/Borne shell script to convert your XF86Config file inAppendix A & B.
You need to get comfortable with using the frame buffer device onone monitor, understanding any issues that can arise from your setup that have nothing to do with multi-head support. This can savea lot of head scratching later.
I'm going to concentrate my explanation on getting X running on thesecond monitor as doing most other configurations will just be aobvious subset of the procedure.
Move a console over...
Compile the "con2fb" program. If you run it without any argumentsyou'll get the following usage message:
"usage: con2fb fbdev console".
Thus, an example command would be "con2fb /dev/fb1 /dev/tty6" tomove virtual console number six over to the second monitor. UseCtrl-Alt-F6 to move over to that console and see that it does indeedshow up on the second monitor.
Use "fb上一页 [1] [2] [3] [4] [5] [6] [7] 下一页 |
| 学院录入：4Lzx.com 责任编辑：4Lzx.com |
|
上一篇学院： FRramebuffer HOWTO英文(续)
下一篇学院： 在Linux下安装Oracle Database 9i |
| 【字体：小 大】【发表评论】【加入收藏】【告诉好友】【打印此文】【关闭窗口】 |
 网友评论：（评论内容只代表网友观点，与本站立场无关！） |
| |
|
 |
|
|
