finalized docs for release.
git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@15212 a95241bf-73f2-0310-859d-f6bbb57e9c96
This commit is contained in:
Rudolf Cornelissen
parent
9528941458
commit
898ec61104
@ -39,25 +39,25 @@ You use this software at your own risk! Although I don't expect it to damage you
|
||||
<li>Full BWindowScreen support (used for hardware pageflipping, scrolling/panning and acceleration in applications/games);
|
||||
<li>Full card coldstart support (important if you use such a card as secondary videocard);
|
||||
<li>Sync_on_green support: G400, G450 and G550 apparantly miss the needed board wiring to actually support this fully though;
|
||||
<li>DPMS support on both heads;
|
||||
<li>DPMS support on all heads;
|
||||
</ul>
|
||||
<li>G200-G550:
|
||||
<ul>
|
||||
<li>B_YCbCr422 hardware overlay support on one head (including 'hardware zoom');
|
||||
<li>MMS (multiple heads using multiple GPUs) cards are supported on all heads (confirmed a G200MMS working OK), although you can't use the non-primary heads without a video consumer node or other special software;
|
||||
</ul>
|
||||
<li>G400-G550:
|
||||
<ul>
|
||||
<li>Dualhead functionality;<br>
|
||||
<strong>Note:</strong> You need <strong>Dualhead Setup</strong> for use of dualhead modes.
|
||||
<li>TVout support: Desktop modes: G400 only for now; Video modes: G400-G550.<br>
|
||||
<strong>Note:</strong> You need <strong>Dualhead Setup</strong> for use of Desktop TVout modes, and you need <strong>VideoScreen V6</strong> for use of Video TVout modes (for now).
|
||||
</ul>
|
||||
<strong>Note:</strong> You need <strong>Dualhead Setup 0.04</strong> (BeBits) for use of Dualhead and/or TVout modes.
|
||||
</ul>
|
||||
<strong>current MGA driver limitations:</strong><br><br>
|
||||
<ul>
|
||||
<li>If you want BScreen 'Sync_to_Retrace' capability make sure you enabled 'assign IRQ to VGA card' in your system BIOS (if available);
|
||||
<li>Expansion RAM modules are not supported as far as I know;
|
||||
<li>Special versions of G200 apparantly have colorpalette problems (Marvel, Matrox MMS cards like the HP VisualizeFX ). Use them in 32bit mode; overlay and hardware cursor should be OK.
|
||||
<li>Special versions of G200 apparantly have colorpalette problems (Marvel, some Matrox MMS cards like the HP VisualizeFX). Use them in 32bit mode; overlay and hardware cursor should be OK.
|
||||
<li>G400 cards have overscanning rubbish visible on the top of the screen if spaces with virtual height are used on the secondary head in monitor mode. This cannot be fixed decently, and is caused by a MAVEN hardware design fault;
|
||||
<li>DVI output is not yet supported.
|
||||
</ul>
|
||||
@ -74,6 +74,7 @@ BeOS first checks (during boot) if there are 'user-addons' that should be loaded
|
||||
<br>
|
||||
Since BeOS only supports all Matrox cards upto and including G400 you will end up in VGA grayscale videomode if you have a G450 or G550. Otherwise, you will have a normal colorfull Desktop. Only BeOS will be using it's own official drivers in this case...<br>
|
||||
<strong>Note:</strong> This might turn out to be handy if you run into trouble upon testing the driver, or if you are 'tweaking' the mga.settings file...<br>
|
||||
<br>
|
||||
<br><br>
|
||||
<strong>actual INSTALLATION, part 1:</strong><br>
|
||||
<br>
|
||||
@ -89,9 +90,12 @@ In order to do this, you need to delete two files (and reboot afterwards). Here'
|
||||
<li>In: <strong>home/config/add-ons/kernel/drivers/bin/</strong><br>
|
||||
delete: <strong>gx00.driver</strong>
|
||||
(You *should* find 'mga.driver' there if you already installed the openBeOS driver V0.13 alpha2 or up.)
|
||||
<li>You can also delete the <strong>mgaGx00.log</strong> logfile which is generated by Mark's driver in your <strong>home</strong> folder. (The logfile called 'mga.accelerant.0.log' the new driver generates is located there also. You may delete that if it gets too big: the Haiku driver simply creates a new one from scratch when needed. The same applies for a possibly existing 'mga.accelerant.1.log' file, generated by clone accelerants.)
|
||||
<li>You can also delete the <strong>mgaGx00.log</strong> logfile which is generated by Mark's driver in your <strong>home</strong> folder. (The logfile called 'mga.(/dev/graphics name).0.log' the new driver generates is located there also. You may delete that if it gets too big: the Haiku driver simply creates a new one from scratch when needed. The same applies for a possibly existing 'mga.(/dev/graphics name).1.log' file, generated by clone accelerants.)
|
||||
</ul>
|
||||
If you install a new version of the Haiku MGA driver later on you won't encounter this manual thing again: it's a one-time thing only.<br>
|
||||
<hr>
|
||||
<strong>Note: If you used the (non-released) 3D capable Matrox driver please remove it, as it may interfere with the Haiku driver.</strong>
|
||||
<hr>
|
||||
<br>
|
||||
<br>
|
||||
<strong>actual INSTALLATION, part 2:</strong><br>
|
||||
@ -149,7 +153,7 @@ This option is disabled by default (preceded by a '#').<br>
|
||||
<li>Memory detection does not work (yet) on Millenium I and II cards. Millenium I is preset to having 2Mb RAM, while Millenium II is preset to having 4Mb RAM. If you have more and want to use it, use the <strong>memory</strong> option to set the driver to the correct amount of RAM.
|
||||
</ul>
|
||||
<li><strong>hardcursor:</strong><br>
|
||||
The hardcursor capabilities of the MGA cards are limited to one head only. A hardcursor is nessesary though for DirectWindow windowed mode support.
|
||||
The hardcursor capabilities of the MGA cards are limited to one head only (except for MMS cards). A hardcursor is nessesary though for DirectWindow windowed mode support.
|
||||
<ul>
|
||||
<li><strong>false:</strong> (default setting in V0.13 beta2 and V0.14)<br>
|
||||
If you want to use dualhead and also want a visible cursor on both heads, select <strong>hardcursor false</strong>. This setting is used by default these days because it's a 'failsafe' setting that works independently of the selected videomode.
|
||||
@ -161,8 +165,8 @@ This option is disabled by default (preceded by a '#').<br>
|
||||
<li>Starting with V0.13beta1 the hardcursor also works on G100 cards.
|
||||
<li>Driverversion V0.14 also introduces Millenium I and II hardcursor support.
|
||||
</ul>
|
||||
<li><strong>logmask:</strong> (set to minimal by default)<br>
|
||||
The logmask option is very handy to track down trouble in the driver. You should only enable this if you are doing so, otherwise keep it turned off because it slows down your system. (All lines have a '#' preceding 'logmask' by default.) Logging creates a logfile called <strong>mga.accelerant.0.log</strong> in your <strong>~ (home)</strong> folder. A second logfile may get created depending on how the driver is used (on cloning; for BWindowScreen for example). The second file is called <strong>mga.accelerant.1.log</strong>, and it will also be in your home folder.<br>
|
||||
<li><strong>logmask:</strong> (set to disabled by default)<br>
|
||||
The logmask option is very handy to track down trouble in the driver. You should only enable this if you are doing so, otherwise keep it turned off because it slows down your system. (All lines have a '#' preceding 'logmask' by default.) Logging creates a logfile called <strong>mga.(/dev/graphics name).0.log</strong> in your <strong>~ (home)</strong> folder. A second logfile may get created depending on how the driver is used (on cloning; for BWindowScreen for example). The second file is called <strong>mga.(/dev/graphics name).1.log</strong>, and it will also be in your home folder.<br>
|
||||
<strong>Note:</strong>
|
||||
<ul>
|
||||
<li>You may only enable *one* logmask-line. The value you place after it (hexadecimal 32bit) determines what will be logged. The first 7 digits determine the part of the driver that will be logging, the last single digit determines the level of logging (like 'all messages', or only 'error messages').
|
||||
@ -173,7 +177,7 @@ Dumprom is another 'tool' for bug-tracking purposes.
|
||||
<li><strong>false:</strong> (default setting)<br>
|
||||
Keep it set to <strong>dumprom false</strong>, unless you want the driver to dump the contents of your VGA BIOS ROM in a file.
|
||||
<li><strong>true:</strong><br>
|
||||
<strong>dumprom true</strong> lets the driver dump a copy of your VGA BIOS in a file called <strong>mga.rom</strong> in your <strong>~ (home)</strong> folder.
|
||||
<strong>dumprom true</strong> lets the driver dump a copy of your VGA BIOS in a file called <strong>mga.(/dev/graphics name).rom</strong> in your <strong>~ (home)</strong> folder.
|
||||
</ul>
|
||||
<li><strong>greensync:</strong> (V0.14 and up)<br>
|
||||
Greensync is used to enable an alternate monitor signal synchronisation setup used for some specific monitors outthere.
|
||||
@ -187,6 +191,13 @@ Greensync is used to enable an alternate monitor signal synchronisation setup us
|
||||
<ul>
|
||||
<li>Enabling sync on green does two things. It enables output of composite sync on the Hsync line (while keeping Vsync only on the Vsync line), and it adds this composite sync to the green signal output to your monitor. While outputting composite sync works on all cards, adding this to the green signal output only works on older cards, upto and including G200.
|
||||
</ul>
|
||||
<li><strong>primary:</strong> (set to disabled by default)<br>
|
||||
Primary lets you force a certain card to be used as primary card in your system if you have multiple graphics cards installed: so it will display your desktop. To enable this (hack) feature uncomment this item and fill in the exact name of the card that is to be primary (as exported by the kerneldriver in /dev/graphics/). If you are going to select a card other than the one displaying your system's POST messages at bootup, make sure you also keep the default 'usebios false' setting as otherwise the card(s) aren't coldstarted by the driver.<br>
|
||||
<strong>Note please:</strong>
|
||||
<ul>
|
||||
<li>Coldstarting doesn't work on Millenium I and Millenium II cards yet;
|
||||
<li>Primary forces the primary card by preceding the exported name by a minus-sign (-) for the selected device. This ensures that this device will be listed at the top in the /dev/graphics/ folder, which is alphabetically ordered. Please make sure you enable the 'primary' feature on just one graphics driver, otherwise it's effect isn't 'guaranteed'.
|
||||
</ul>
|
||||
</ul>
|
||||
<br>
|
||||
<strong>Notes:</strong>
|
||||
@ -196,6 +207,6 @@ Greensync is used to enable an alternate monitor signal synchronisation setup us
|
||||
<hr>
|
||||
<br>
|
||||
<a href="mailto:info.be-hold@inter.nl.net">Rudolf Cornelissen.</a>
|
||||
<p>(Page last updated on November 24, 2005)</p>
|
||||
<p>(Page last updated on November 29, 2005)</p>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
@ -4,7 +4,7 @@
|
||||
</head>
|
||||
<body>
|
||||
<p><h2>Changes done for each driverversion:</h2></p>
|
||||
<p><h1>head (SVN 0.26, Rudolf)</h1></p>
|
||||
<p><h1>mga_driver 0.26 (Rudolf)</h1></p>
|
||||
<ul>
|
||||
<li><strong>G200-G550:</strong>
|
||||
<ul>
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user