i2p/haiku-beta6
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

updated documentation

Browse Source 
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@5991 a95241bf-73f2-0310-859d-f6bbb57e9c96
This commit is contained in:
Rudolf Cornelissen
2004-01-08 16:41:12 +00:00
parent 0be4037053
commit 90879508d8
6 changed files with 268 additions and 184 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/add-ons/kernel/drivers/graphics/matrox/README.html
+84 -19
View File
@@ -2,24 +2,74 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="GENERATOR" content="The DarkSite">
<title>Readme for (open)BeOS MATROX MGA driver V0.14</title>
<title>Readme for (open)BeOS Unified Matrox graphics driver</title>
</head>
<body>
<h2 align="center">Matrox G100/G200/G400/G450/G550 driver for (open)BeOS</h2></align><br><br>
<h2>Installation:</h2>
This is the 0.14 release of the (open)BeOS Matrox display driver.<br>
<h2 align="center">Unified Matrox graphics driver for (open)BeOS</h2></align><br><br>
<hr>
<h3><strong>NOTE PLEASE:</strong><br>
You use this software at your own risk! Although I don't expect it to damage your PC, videocard or Monitor, I cannot guarantee this!</h3>
<hr>
<h2>Supported cards:</h2>
<ul>
<li>Millenium I (preliminary)
<li>Millenium II (preliminary)
<li>G100
<li>G200
<li>G400
<li>G450
<li>G550
</ul>
<br>
<hr>
<h2>Features:</h2>
<ul>
<li>Millenium I/II (preliminary):
<ul>
<li>Hardware cursor support;
<li>Full 2D acceleration;
<li>Full BWindowScreen support (used for hardware pageflipping, scrolling/panning and acceleration in applications/games);
<li>Sync_on_green support;
<li>DPMS support;
</ul>
<li>G100-G550:
<ul>
<li>Hardware cursor support on one head;
<li>Full 2D acceleration;
<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;
</ul>
<li>G200-G550:
<ul>
<li>B_YCbCr422 hardware overlay support on one head (including 'hardware zoom');
</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>
</ul>
<strong>current MGA driver limitations:</strong><br><br>
<ul>
<li>If the driver does not load make sure you enabled 'assign IRQ to VGA card' in your system BIOS;
<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>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.
</ul>
<br>
<hr>
<h2>Installation:</h2>
If you encounter bugs, please checkout the driver's <a href="http://web.inter.nl.net/users/be-hold/BeOS/MGAdriver/index.html">website</a> to see if it's already on the todo list. You can also checkout the <a href="UPDATE.html">UPDATE</a> file included with this driver to see if it should have been fixed. If you think it's prudent, or if you are unsure, then please fill out the <a href="http://web.inter.nl.net/users/be-hold/BeOS/MGAdriver/bugreport.html">bugreport</a> on the site or send me an <a href="mailto:[email protected]">Email</a>. Make sure you are as precise as possible because that will make things easier to trackdown and fix...<br>
<br>
<br>
OK, now that's all said let's get to it ;-)<br>
<br>
In contrary to what I have said before you don't need to de-install official Be drivers for this driver to work correctly. This driver will install in the user part of the BeOS, so not in the system part where the official drivers are.<br>
BeOS first checks (during boot) if there are 'user-addons' that should be loaded for a device. If not, it loads it's own drivers (if any). You can select which driver should be loaded by hitting the spacebar as soon as the BeOS 'icons' screen appears. If you select <strong>disable user addons</strong> the system will load it's own drivers. If you don't do anything, the system will load the (open)BeOS Matrox MGA driver.<br>
BeOS first checks (during boot) if there are 'user-addons' that should be loaded for a device. If not, it loads it's own drivers (if any). You can select which driver should be loaded by hitting the spacebar as soon as the BeOS 'icons' screen appears. If you select <strong>disable user addons</strong> the system will load it's own drivers. If you don't do anything, the system will load the (open)BeOS Matrox graphics driver.<br>
<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>
@@ -38,19 +88,34 @@ 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.log' the new driver generates is located there also. You may delete that if it gets too big: the (open)BeOS driver simply creates a new one from scratch when needed.)
<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 (open)BeOS 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.)
</ul>
If you install a new version of the (open)BeOS MGA driver later on you won't encounter this manual thing again: it's a one-time thing only. The install script Apsed wrote for the (open)BeOS MGA driver uninstalls the previous version automatically. It just does not check for the G400 driver Mark wrote...<br>
If you install a new version of the (open)BeOS MGA driver later on you won't encounter this manual thing again: it's a one-time thing only.<br>
<br>
<br>
<strong>actual INSTALLATION, part 2:</strong><br>
<br>
In a terminal switch to the 'openBeOS_Matrox_V0.14_src' or 'openBeOS_Matrox_V0.14_bin' folder (depending on downloaded version) and type:<br>
make install<br>
Doubleclick on the install.sh file and follow the instructions. You have to reboot in order to load the driver. Make sure you read the <strong>Settings</strong> information below before you do that...<br>
<br>
<br>
<strong>alternate INSTALLATION (part 2) method:</strong><br>
<br>
Unzip the zip file that contains the driver to the root folder. Now reboot and you should be using the new driver.<br>
<br>
<br>
<strong>DE-INSTALLATION:</strong><br>
<br>
Currently there's no uninstall script included. Just do it manually:<br>
<br>
Delete the <strong>mga.accelerant</strong> file in <strong>home/config/add-ons/accelerants/</strong><br>
Delete the <strong>mga.driver</strong> file in <strong>home/config/add-ons/kernel/drivers/bin/</strong><br>
Delete the <strong>mga.settings</strong> file in <strong>home/config/settings/kernel/drivers/</strong><br>
Delete the <strong>mga.driver shortcut</strong> in <strong>home/config/add-ons/kernel/drivers/dev/graphics/</strong> which pointed to the file <strong>mga.driver</strong>.<br>
<br>
You have to reboot in order to apply the original configuration.<br>
<br>
<br>
You have to reboot in order to load the driver. Make sure you read the <strong>Settings</strong> information below before you do that...<br>
<hr>
<br>
<a name="settings"></a><h2>Settings:</h2><br>
Please read this information carefully *before* installing and using the (open)BeOS Matrox MGA driver. It might spare you some trouble afterwards..<br>
<p>The driver uses a file named <strong>mga.settings</strong> to determine how to use your card. After installation this file will be located at <strong>home/config/settings/kernel/drivers/</strong>. How you should setup this file depends on what you want to do with the driver. While it has a 'failsave' default configuration, you might be able to do better than that... Anyway, read the nifty details below.<br>
@@ -83,12 +148,12 @@ 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.
The hardcursor capabilities of the MGA cards are limited to one head only. A hardcursor is nessesary though for DirectWindow windowed mode support.
<ul>
<li><strong>false:</strong> (default setting in V0.13 beta2 and later)<br>
<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.
<li><strong>true:</strong> (default setting in V0.13 beta1)<br>
A software cursor 'flickers' a bit sometimes because it has to be redrawn constantly. So for use in singlehead mode <strong>hardcursor true</strong> is the preferred setting.
<li><strong>true:</strong> (default setting in V0.13 beta1 and V0.15 and later)<br>
A software cursor 'flickers' a bit sometimes because it has to be redrawn constantly. So for use in singlehead mode <strong>hardcursor true</strong> is the preferred setting. For DirectWindow windowed mode functionality you need to use this setting also (Chart demo app for instance).
</ul>
<strong>Notes:</strong>
<ul>
@@ -96,7 +161,7 @@ This option is disabled by default (preceded by a '#').<br>
<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.log</strong> in hour <strong>~ (home)</strong> folder.<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>
<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').
@@ -125,12 +190,12 @@ Greensync is used to enable an alternate monitor signal synchronisation setup us
<br>
<strong>Notes:</strong>
<ul>
<li>If you want to use standard TVout or dualhead modes, you need <strong>dualheadSetup</strong>. You can download this <a href="http://www.bebits.com/app/1401" target="blank">application</a> from BeBits.
<li>If you want to use the VCD or DVD dualhead clone TVout modes on G450 or G550 with driver V0.14 and up, you can download a simple command-line tool called <strong>VideoScreen</strong> for now from the <a href="http://web.inter.nl.net/users/be-hold/BeOS/MGAdriver/tools.html#tools">tools</a> page on the (open)BeOS Matrox MGA driver site.
<li>If you want to use standard (Desktop) TVout or dualhead modes, you need <strong>dualheadSetup</strong>. You can download this <a href="http://www.bebits.com/app/1401" target="blank">application</a> from BeBits.
<li>If you want to use the VCD or DVD dualhead clone (Video) TVout modes on G400 with driver V0.15 and up, or on G450 or G550 with driver V0.14 and up, you can download a simple command-line tool called <strong>VideoScreen</strong> for now from the <a href="http://web.inter.nl.net/users/be-hold/BeOS/MGAdriver/tools.html#tools">tools</a> page on the (open)BeOS Matrox MGA driver site. For driver V0.15 and up you need the updated V6 version of this tool.
</ul>
<hr>
<br>
<a href="mailto:[email protected]">Rudolf Cornelissen.</a>
<p>(Page last updated on April 20, 2003)</p>
<p>(Page last updated on January 8, 2004)</p>
</body>
</html>
src/add-ons/kernel/drivers/graphics/matrox/UPDATE.html
+42
View File
@@ -4,6 +4,48 @@
</head>
<body>
<p><h2>Changes done for each driverversion:</h2></p>
<p><h1>head (0.16-1, Rudolf)</h1></p>
<ul>
<li><strong>General:</strong>
<ul>
<li>Expanded modelist to include suggested modes above 1600x1200 upto 2048x1536 resolution: Done by Andrew Bachmann;
<li>CRTC timing restriction checking updated: Modelists exported adhere to every cards max. CRTC capability now: the oldest cards support upto and including 1600x1200, while the newest cards support upto and including 2048x1536 resolution.
</ul>
</ul>
<p><h1>mga_driver 0.15 (Rudolf)</h1></p>
<ul>
<li><strong>G400/G400MAX:</strong>
<ul>
<li>Secondary head (maven) sync polarity programming fixed/implemented for monitor mode: this never worked correctly yet;
<li>Fixed TVout aspect ratio, size, position and distortions; also removed refreshrate dependancies. This means the PAL and NTSC Desktop modes 640x480, 800x600 and 1024x768 are fully OK now;
<li>Implemented the PAL and NTSC Video VCD and DVD TVout modes: being 640x480 and 720x480 for NTSC; 768x576 and 720x576 for PAL. Checkout the <a href="http://web.inter.nl.net/users/be-hold/BeOS/MGAdriver/tools.html#tools">tools</a> and <a href="http://web.inter.nl.net/users/be-hold/BeOS/MGAdriver/dvdvideo.html">VCD/DVD on TV</a> stuff;
<li>Checked out the overscanning rubbish visible on the top of the screen on the secondary head if spaces with virtual height are used. This cannot be fixed decently for monitor mode due to a MAVEN hardware design fault; fixed TVout modes via a vertical sync 'tweak' though. Also updated the workaround code for non-virtual and virtual-width-only modes to respect RAM size and non-accelerated modes;
<li>Updated ProposeMode RAM and virtual width requirement checks for dualhead modes.
</ul>
<li><strong>G450:</strong>
<ul>
<li>Updated ProposeMode RAM and virtual width requirement checks for dualhead modes;
<li>Added full DPMS support for secondary head;
<li>Disabled G400 MAVEN design fault workaround code as the new 'on die MAVEN' is OK.
</ul>
<li><strong>G550:</strong>
<ul>
<li>Updated ProposeMode RAM and virtual width requirement checks for dualhead modes;
<li>Added full DPMS support for secondary head;
<li>Disabled G400 MAVEN design fault workaround code as the new 'on die MAVEN' is OK.
</ul>
<li><strong>General:</strong>
<ul>
<li>Retrace sync fix: sync now actually happens during retrace;
<li>BWindowScreen R3-style function update for acceleration and page flipping/virtualscreens in apps ('Allegro' update): fixed cloning accelerants, fixed acceleration in clones;
<li>CRTC timing restriction checking updated;
<li>Kernel driver now signals abort on not being able to setup the INT routine instead of letting the machine freeze during accelerant initialisation;
<li>Primary head sync polarity programming fixed: this never worked correctly;
<li>Fixed/updated DPMS functionality on primary head as only part of it was working;
<li>DPMS compatibility update for use with sync_on_green: Secondary head DPMS remains operational; primary head will only blank the display while keeping it's sync in place;
<li>Modified the default settings file for use of the hardcursor ('hardcursor true'). It turns out BDirectWindow windowed mode needs this setting for it to be enabled ('Chart' demo app for instance). If you want a cursor on both heads using dualhead you need to change the settings file back to 'hardcursor false' yourself now.
</ul>
</ul>
<p><h1>mga_driver 0.14 (Rudolf)</h1></p>
<ul>
<li><strong>Millenium I:</strong>
src/add-ons/kernel/drivers/graphics/neomagic/README.html
+66 -43
View File
@@ -2,17 +2,54 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="GENERATOR" content="The DarkSite">
<title>Readme for (open)BeOS NeoMagic MagicGraph/MagicMedia graphics driver V0.05</title>
<title>Readme for (open)BeOS Unified NeoMagic MagicGraph/MagicMedia graphics driver</title>
</head>
<body>
<h2 align="center">NeoMagic MagicGraph/MagicMedia graphics driver for (open)BeOS</h2></align><br><br>
<h2>Installation:</h2>
This is the 0.05 release of the (open)BeOS NeoMagic display driver.<br>
<h2 align="center">Unified NeoMagic MagicGraph/MagicMedia graphics driver for (open)BeOS</h2></align><br><br>
<hr>
<h3><strong>NOTE PLEASE:</strong><br>
You use this software at your own risk! Although I don't expect it to damage your PC, videocard or Monitor, I cannot guarantee this!</h3>
<hr>
<br>
Note please:<br>
This driver is still alpha quality. 2D acceleration is still lacking, overlay does not work correctly yet on MagicMedia cards and there may be additional trouble. While you are encouraged to test and use the driver (if it works at all for you then it will probably be stable as well), don't delete the old one(s) just yet!<br>
<h2>Supported cards:</h2>
<ul>
<li>MagicGraph 128 (NM2070)
<li>MagicGraph 128V (NM2090)
<li>MagicGraph 128ZV (NM2093)
<li>MagicGraph 128ZV+ (NM2097)
<li>MagicGraph 128XD (NM2160)
<li>MagicMedia 256AV (NM2200)
<li>MagicMedia 256AV+ (NM2230)
<li>MagicMedia 256ZX (NM2360)
<li>MagicMedia 256XL+ (NM2380)
</ul>
<br>
<hr>
<h2>Features:</h2>
<ul>
<li>Hardware cursor support;
<li>Full BWindowScreen support (used for hardware pageflipping, scrolling/panning and acceleration in applications/games);
<li>B_YCbCr422 hardware overlay support (except on MagicGraph 128, so NM2070 cards).
</ul>
<strong>Known limitations:</strong>
<ul>
<li>If the driver does not load make sure you enabled 'assign IRQ to VGA card' in your system BIOS;
<li>NeoMagic cards do not support overlay downscaling. You won't be able to select for instance 50% scaled output, nor will you be able to resize the video output window below 100% by dragging.
<br>
(In Windows downscaling works: this is done by scaling down the overlay input bitmaps in the application software: so this is a 'trick' solution not done by the driver!)
<li>Stretching modes for the laptop display panel will not be setup. In stretched modes no hardcursor is supported, and overlay output requires tweaking to get going...
<li>Apparantly it's not possible to boot into modes with a resolution above 800x600 pixels on some cards. If you encounter this please report it, and only use high resolution modes on other workspaces for now.
<br>
A fix for this behaviour will be attempted in the future.
<li>The keyboard 'shortcut key' for changing output devices bypasses the videodriver and directly uses the cardBIOS. Sometimes using this key will have unwanted results. Please use with care! Or better yet: just preset the output device(s) you want in the system BIOS...
<br>
A fix for this behaviour will also be attempted in the future (sort of getting the driver and the BIOS in 'sync').
</ul>
<br>
<hr>
<h2>Installation:</h2>
If you encounter bugs, please checkout the driver's <a href="http://web.inter.nl.net/users/be-hold/BeOS/NMdriver/index.html">website</a> to see if it's already on the todo list. You can also checkout the <a href="UPDATE.html">UPDATE</a> file included with this driver to see if it should have been fixed. If you think it's prudent, or if you are unsure, then please fill out the <a href="http://web.inter.nl.net/users/be-hold/BeOS/NMdriver/bugreport.html">bugreport</a> on the site or send me an <a href="mailto:[email protected]">Email</a>. Make sure you are as precise as possible because that will make things easier to trackdown and fix...<br>
<br>
<br>
@@ -23,42 +60,27 @@ BeOS first checks (during boot) if there are 'user-addons' that should be loaded
<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 nm.settings file...<br>
<br><br>
<strong>actual INSTALLATION:</strong><br>
<br>
In a terminal switch to the 'openBeOS_Neomagic_V0.05_src' or 'openBeOS_Neomagic_V0.05_bin' folder (depending on downloaded version) and type:<br>
make install<br>
<br>
You have to reboot in order to load the driver. Make sure you read the <strong>Settings</strong> information below before you do that...
<br>
<br>
<br>
<strong>DE-INSTALLATION:</strong><br>
<br>
In a terminal switch to the 'openBeOS_Neomagic_V0.05_src' or 'openBeOS_Neomagic_V0.05_bin' folder (depending on downloaded version) and type:
<br>
make uninstall<br>
<br>
You have to reboot in order to apply the original configuration.<br>
<br>
<br>
<strong>alternate INSTALLATION method:</strong><br>
<br>
In order for the install to work as described above you need to have the developer tools installed. If you don't have that, you can still do a manual install by copying some files from the
<strong>obj/</strong> folder:<br>
<br>
Copy the <strong>nm.accelerant</strong> file to <strong>home/config/add-ons/accelerants/</strong><br>
Copy the <strong>nm.driver</strong> file to <strong>home/config/add-ons/kernel/drivers/bin/</strong><br>
Copy the <strong>nm.settings</strong> file to <strong>home/config/settings/kernel/drivers/</strong><br>
Create a <strong>shortcut</strong> in <strong>home/config/add-ons/kernel/drivers/dev/graphics/</strong> which points to the file
<strong>nm.driver</strong> you just installed.<br>
<br>
Now reboot and you should be using the new driver.<br>
<br>
<br>
<strong>alternate DE-INSTALLATION method:</strong><br>
<br>
Just delete the three files and the shortcut created as described in the <strong>alternate INSTALLATION method
</strong>. When you're done, reboot. The original configuration will now be in effect again.<br>
<strong>actual INSTALLATION:</strong><br>
<br>
Doubleclick on the install.sh file and follow the instructions. You have to reboot in order to load the driver. Make sure you read the <strong>Settings</strong> information below before you do that...<br>
<br>
<br>
<strong>alternate INSTALLATION method:</strong><br>
<br>
Unzip the zip file that contains the driver to the root folder. Now reboot and you should be using the new driver.<br>
<br>
<br>
<strong>DE-INSTALLATION:</strong><br>
<br>
Currently there's no uninstall script included. Just do it manually:<br>
<br>
Delete the <strong>nm.accelerant</strong> file in <strong>home/config/add-ons/accelerants/</strong><br>
Delete the <strong>nm.driver</strong> file in <strong>home/config/add-ons/kernel/drivers/bin/</strong><br>
Delete the <strong>nm.settings</strong> file in <strong>home/config/settings/kernel/drivers/</strong><br>
Delete the <strong>nm.driver shortcut</strong> in <strong>home/config/add-ons/kernel/drivers/dev/graphics/</strong> which pointed to the file <strong>nm.driver</strong>.<br>
<br>
You have to reboot in order to apply the original configuration.<br>
<br>
<br>
<hr>
<a name="settings"></a><h2>Settings:</h2><br>
@@ -75,14 +97,15 @@ Please read this information carefully *before* installing and using the (open)B
This option enables you to override the 'memory amount autodetection' of the driver. The driver does not need this because it's well known how much RAM every specific card contains, but you could limit the amount of RAM to a lower value than actually there to test with for instance overlay use in applications. So this option is probably only of interest to developers. Specify the RAM amount in Kb (use only 'whole' numbers!).<br>
This option is disabled by default (preceded by a '#').<br>
<li><strong>hardcursor:</strong><br>
A hardcursor is nessesary for DirectWindow windowed mode support.
<ul>
<li><strong>false:</strong><br>
If you have trouble with the hardcursor, select <strong>hardcursor false</strong>. Make sure you let me know about the hardcursor trouble also: this should not happen!
<li><strong>true:</strong> (default setting)<br>
A software cursor 'flickers' a bit sometimes because it has to be redrawn constantly. So <strong>hardcursor true</strong> is the preferred setting.
A software cursor 'flickers' a bit sometimes because it has to be redrawn constantly. So <strong>hardcursor true</strong> is the preferred setting. For DirectWindow windowed mode functionality you need to use this setting also (Chart demo app for instance).
</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>nm.accelerant.log</strong> in hour <strong>~ (home)</strong> folder.<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>nm.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>nm.accelerant.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').
@@ -100,6 +123,6 @@ Dumprom is another 'tool' for bug-tracking purposes.
<hr>
<br>
<a href="mailto:[email protected]">Rudolf Cornelissen.</a>
<p>(Page last updated on August 14, 2003)</p>
<p>(Page last updated on January 8, 2004)</p>
</body>
</html>
src/add-ons/kernel/drivers/graphics/neomagic/UPDATE.html
+9 -21
View File
@@ -4,6 +4,13 @@
</head>
<body>
<p><h2>Changes done for each driverversion:</h2></p>
<p><h1>head (0.06-1, Rudolf)</h1></p>
<ul>
<li>Updated modelist to include one more suggested mode for 800x600 resolution: Done by Andrew Bachmann;
<li>CRTC timing restriction checking updated: Modelists exported adhere to every cards max. CRTC capability now: the oldest cards support upto and including 1024x1000, while the newest cards support upto and including 1280x1024 resolution;
<li>Kernel driver now signals abort on not being able to setup the INT routine instead of letting the machine freeze during accelerant initialisation;
<li>BWindowScreen R3-style function update for acceleration (once setup) and page flipping/virtualscreens in apps ('Allegro' update): fixed cloning accelerants.
</ul>
<p><h1>nm_driver 0.05 (Rudolf)</h1></p>
<ul>
<li>Prevent system or video freeze on dragging files or so in tracker windows;
@@ -11,31 +18,11 @@
<li>Sync polarity setup now actually works (external monitor only mode);
<li>Power-up register unlocking narrowed down to overlay engine only. This should fix the screen rubbish trouble most users had with V0.04 which did not exist for them on V0.03.
</ul>
<strong>Known limitations:</strong>
<ul>
<li>NeoMagic cards do not support overlay downscaling. You won't be able to select for instance 50% scaled output, nor will you be able to resize the video output window below 100% by dragging.<br>
(In Windows downscaling works: this is done by scaling down the overlay input bitmaps in the application software: so this is a 'trick' solution not done by the driver!)
<li>Stretching modes for the laptop display panel will not be setup. In stretched modes no hardcursor is supported, and overlay output requires tweaking to get going...
<li>Apparantly it's not possible to boot into modes with a resolution above 800x600 pixels on some cards. If you encounter this please report it, and only use high resolution modes on other workspaces for now.<br>
A fix for this behaviour will be attempted in the future.
<li>The keyboard 'shortcut key' for changing output devices bypasses the videodriver and directly uses the cardBIOS. Sometimes using this key will have unwanted results. Please use with care! Or better yet: just preset the output device(s) you want in the system BIOS...<br>
A fix for this behaviour will also be attempted in the future (sort of getting the driver and the BIOS in 'sync').
</ul>
<p><h1>nm_driver 0.04 (Rudolf)</h1></p>
<ul>
<li>included hardware overlay for the B_YCbCr422 (FourCC: YUY2) colorspace;
<li>added CRTC registers unlock command on startup.
</ul>
<strong>Known limitations:</strong>
<ul>
<li>NeoMagic cards do not support overlay downscaling. You won't be able to select for instance 50% scaled output, nor will you be able to resize the video output window below 100% by dragging.<br>
(In Windows downscaling works: this is done by scaling down the overlay input bitmaps in the application software: so this is a 'trick' solution not done by the driver!)
<li>Stretching modes for the laptop display panel will not be setup. In stretched modes no hardcursor is supported, and overlay output requires tweaking to get going...
<li>Apparantly it's not possible to boot into modes with a resolution above 800x600 pixels on some cards. If you encounter this please report it, and only use high resolution modes on other workspaces for now.<br>
A fix for this behaviour will be attempted in the future.
<li>The keyboard 'shortcut key' for changing output devices bypasses the videodriver and directly uses the cardBIOS. Sometimes using this key will have unwanted results. Please use with care! Or better yet: just preset the output device(s) you want in the system BIOS...<br>
A fix for this behaviour will also be attempted in the future (sort of getting the driver and the BIOS in 'sync').
</ul>
<p><h1>nm_driver 0.03 (Rudolf)</h1></p>
<ul>
<li>virtual screens / BWindowScreen support including panning/scrolling;
@@ -52,7 +39,8 @@ A fix for this behaviour will also be attempted in the future (sort of getting t
<li>updates needed for LCD centering support;
<li>fix for trouble with booting into modes above 800x600 resolution on some cards (please report this behaviour!);
<li>shadowregister programming needed for 'full' KB switch BIOS support;
<li>2D acceleration.
<li>2D acceleration;
<li>MagicMedia series overlay update: still contains errors apparantly.
</ul>
</p>
</body>
src/add-ons/kernel/drivers/graphics/nvidia/README.html
+55 -29
View File
@@ -2,19 +2,54 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="GENERATOR" content="The DarkSite">
<title>Readme for (open)BeOS Nvidia TNT/GeForce driver V0.07</title>
<title>Readme for (open)BeOS Unified Nvidia graphics driver</title>
</head>
<body>
<h2 align="center">Nvidia TNT/GeForce graphics driver for (open)BeOS</h2></align><br><br>
<h2>Installation:</h2>
This is the 0.07 release of the (open)BeOS Nvidia TNT/GeForce display driver.<br>
<h2 align="center">Unified Nvidia graphics driver for (open)BeOS</h2></align><br><br>
<hr>
<h3><strong>NOTE PLEASE:</strong><br>
You use this software at your own risk! Although I don't expect it to damage your PC, videocard or Monitor, I cannot guarantee this!<br>
<br>
Especially owners of laptops are encouraged to be extra carefull with their internal panels. A refresh setting higher than 60Hz might destroy the panel!</h3>
<hr>
<h2>Supported cards (as far as is known):</h2>
<ul>
<li>TNT 1/2;
<li>TNT 2-M64;
<li>Vanta/Aladdin TNT2;
<li>GeForce 256;
<li>GeForce 2 MX/Ti/GTS/Go (Go only with external monitor);
<li>GeForce 2 Integrated GPU (Nforce) (setup RAM amount manually for now);
<li>GeForce 3 (Ti);
<li>GeForce 4 MX/Ti/Go (Go only with external monitor);
<li>GeForce 4 Integrated GPU (Nforce 2) (setup RAM amount manually for now);
<li>GeForce FX 5200/5600/5800/5900/Go (Go only with external monitor);
<li>Quadro (2/4/FX/Go) (Go only with external monitor).
</ul>
<br>
<hr>
<h2>Features:</h2>
<ul>
<li>Hardware cursor support;
<li>Full 2D acceleration;
<li>Full BWindowScreen support (used for hardware pageflipping, scrolling/panning and acceleration in applications/games);
<li>DPMS support;
<li>B_YCbCr422 hardware overlay support on all cards (so on both TNT and GeForce series).
</ul>
<strong>Known limitations:</strong>
<ul>
<li>If the driver does not load make sure you enabled 'assign IRQ to VGA card' in your system BIOS;
<li>If the driver seems to create 'random' trouble make sure you have a fully functional VGA BIOS, or system BIOS for embedded cards (check for updates on the manufacturor's site);
<li>256Mb RAM detection is still missing for cards that have that much of it: Please set the amount manually for now via the nv.settings file (driver defaults to 16Mb if you don't);
<li>Flatpanel protection for laptops is not yet in place: be carefull! External only output has been reported functional though.
<li>No DVI support: you have to use a standard VGA cable to connect external flatpanels;
<li>Embedded GeForce RAM detection is non-functional: please set amount manually for now via the nv.settings file (driver probably defaults to 1Mb if you don't). If you have overlay trouble, set a slightly smaller amount of RAM than you actually specified in the system BIOS (1Mb less or so);
<li>A few cards have hardcursor trouble. If you encounter this use the softcursor: select this via the nv.settings file;
<li>GeForce FX 5700 and FX 5950 are not yet supported (mail me if you own such a card!).
</ul>
<br>
<hr>
<h2>Installation:</h2>
If you encounter bugs, please checkout the driver's <a href="http://web.inter.nl.net/users/be-hold/BeOS/NVdriver/index.html">website</a> to see if it's already on the todo list. You can also checkout the <a href="UPDATE.html">UPDATE</a> file included with this driver to see if it should have been fixed. If you think it's prudent, or if you are unsure, then please fill out the <a href="http://web.inter.nl.net/users/be-hold/BeOS/NVdriver/bugreport.html">bugreport form</a> on the site or send me an <a href="mailto:[email protected]">Email</a>. Make sure you are as precise as possible because that will make things easier to trackdown and fix...<br>
<br>
<br>
@@ -27,35 +62,25 @@ BeOS first checks (during boot) if there are 'user-addons' that should be loaded
<br><br>
<strong>actual INSTALLATION:</strong><br>
<br>
In a terminal switch to the 'openBeOS_Nvidia_V0.07_src' folder and type:<br>
make install<br>
<br>
You have to reboot in order to load the driver. Make sure you read the <strong>Settings</strong> information below before you do that...<br>
<br>
<br>
<strong>DE-INSTALLATION:</strong><br>
<br>
In a terminal switch to the 'openBeOS_Nvidia_V0.07_src' folder and type:<br>
make uninstall<br>
<br>
You have to reboot in order to apply the original configuration.<br>
Doubleclick on the install.sh file and follow the instructions. You have to reboot in order to load the driver. Make sure you read the <strong>Settings</strong> information below before you do that...<br>
<br>
<br>
<strong>alternate INSTALLATION method:</strong><br>
<br>
In order for the install to work as described above you need to have the developer tools installed. If you don't have that, you can still do a manual install by copying some files from the <strong>obj/</strong> folder:<br>
<br>
Copy the <strong>nv.accelerant</strong> file to <strong>home/config/add-ons/accelerants/</strong><br>
Copy the <strong>nv.driver</strong> file to <strong>home/config/add-ons/kernel/drivers/bin/</strong><br>
Copy the <strong>nv.settings</strong> file to <strong>home/config/settings/kernel/drivers/</strong><br>
Create a <strong>shortcut</strong> in <strong>home/config/add-ons/kernel/drivers/dev/graphics/</strong> which points to the file <strong>nv.driver</strong> you just installed.<br>
<br>
Now reboot and you should be using the new driver.<br>
Unzip the zip file that contains the driver to the root folder. Now reboot and you should be using the new driver.<br>
<br>
<br>
<strong>alternate DE-INSTALLATION method:</strong><br>
<strong>DE-INSTALLATION:</strong><br>
<br>
Currently there's no uninstall script included. Just do it manually:<br>
<br>
Delete the <strong>nv.accelerant</strong> file in <strong>home/config/add-ons/accelerants/</strong><br>
Delete the <strong>nv.driver</strong> file in <strong>home/config/add-ons/kernel/drivers/bin/</strong><br>
Delete the <strong>nv.settings</strong> file in <strong>home/config/settings/kernel/drivers/</strong><br>
Delete the <strong>nv.driver shortcut</strong> in <strong>home/config/add-ons/kernel/drivers/dev/graphics/</strong> which pointed to the file <strong>nv.driver</strong>.<br>
<br>
You have to reboot in order to apply the original configuration.<br>
<br>
Just delete the three files and the shortcut created as described in the <strong>alternate INSTALLATION method</strong>. When you're done, reboot. The original configuration will now be in effect again.<br>
<br>
<hr>
<a name="settings"></a><h2>Settings:</h2><br>
@@ -72,14 +97,15 @@ Please read this information carefully *before* installing and using the (open)B
This option enables you to override the 'memory amount autodetection' of the driver. If autodetection is working incorrect, you can manually set the amount this way. You could also lower the amount of RAM to a lower value than actually there to test with for instance overlay use in applications. So this option is probably mostly of interest to developers. Specify the RAM amount in Mb (use only 'whole' numbers!).<br>
This option is disabled by default (preceded by a '#').<br>
<li><strong>hardcursor:</strong><br>
A hardcursor is nessesary for DirectWindow windowed mode support.
<ul>
<li><strong>false:</strong><br>
If you have trouble with the hardcursor, select <strong>hardcursor false</strong>. Make sure you let me know about the hardcursor trouble also: this should not happen!
<li><strong>true:</strong> (default setting)<br>
A software cursor 'flickers' a bit sometimes because it has to be redrawn constantly. So <strong>hardcursor true</strong> is the preferred setting.
A software cursor 'flickers' a bit sometimes because it has to be redrawn constantly. So <strong>hardcursor true</strong> is the preferred setting. For DirectWindow windowed mode functionality you need to use this setting also (Chart demo app for instance).
</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>nv.accelerant.log</strong> in hour <strong>~ (home)</strong> folder.<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>nv.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>nv.accelerant.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').
@@ -97,6 +123,6 @@ Dumprom is another 'tool' for bug-tracking purposes.
<hr>
<br>
<a href="mailto:[email protected]">Rudolf Cornelissen.</a>
<p>(Page last updated on October 28, 2003)</p>
<p>(Page last updated on January 8, 2004)</p>
</body>
</html>
src/add-ons/kernel/drivers/graphics/nvidia/UPDATE.html
+12 -72
View File
@@ -4,92 +4,43 @@
</head>
<body>
<p><h2>Changes done for each driverversion:</h2></p>
<p><h1>head (0.08-3, Rudolf)</h1></p>
<ul>
<li>Fixed GeForceFX 5600 monitor 'refresh out of range' / shutoff fault. nVidia changed the pixelPLL for the NV31 (fix is a hack for now due to missing specs);
<li>Fixed acceleration engine restrictions code to adhere to GeForceFX 5600 restrictions: those are still NV20 style for this card;
<li>Fixed overlay scaling restriction code to adhere to GeForceFX 5600 restrictions: engine is still the NV10/NV20 one, so it can downscale to 1/8 of the picture size;
<li>Kernel driver now signals abort on not being able to setup the INT routine instead of letting the machine freeze during accelerant initialisation;
<li>BWindowScreen R3-style function update for acceleration and page flipping/virtualscreens in apps ('Allegro' update): fixed cloning accelerants;
<li>Now only programming options head select register on dualhead cards. This fixes driver hanging on integrated GeForce2 cards (ID 0x01a0), and maybe also on some other cards;
<li>Expanded modelist to include suggested modes above 1600x1200 upto 2048x1536 resolution (if a card supports them): Done by Andrew Bachmann.
</ul>
<p><h1>nv_driver 0.07 (Rudolf)</h1></p>
<a name="features"></a><strong>Current Nvidia driver features:</strong><br><br>
<ul>
<li>Hardware cursor support;
<li>Full 2D acceleration;
<li>Full BWindowScreen support (used for hardware pageflipping and scrolling/panning);
<li>DPMS support;
<li>B_YCbCr422 hardware overlay support on all cards (so on both TNT and GeForce series).
</ul>
<strong>Supported cards (as far as is known):</strong>
<ul>
<li>TNT 1/2;
<li>TNT 2-M64;
<li>Vanta/Aladdin TNT2;
<li>GeForce 256;
<li>GeForce 2 MX/Ti/GTS/Go (Go only with external monitor);
<li>GeForce 2 Integrated GPU (Nforce) (setup RAM amount manually for now);
<li>GeForce 3 (Ti);
<li>GeForce 4 MX/Ti/Go (Go only with external monitor);
<li>GeForce 4 Integrated GPU (Nforce 2) (setup RAM amount manually for now);
<li>GeForce FX 5200/5800/5900/Go (5600 still has persistant trouble, Go only with external monitor);
<li>Quadro (2/4/FX/Go) (Go only with external monitor).
</ul>
<strong>Known limitations:</strong>
<ul>
<li>If the driver hangs your system on boot make sure you enabled 'assign IRQ to VGA card' in your system BIOS;
<li>If the driver seems to create 'random' trouble make sure you have a fully functional VGA BIOS, or system BIOS for embedded cards (check for updates on the manufacturor's site);
<li>256Mb RAM detection is still missing for cards that have that much of it: Please set the amount manually for now via the nv.settings file (driver defaults to 16Mb if you don't);
<li>Flatpanel protection for laptops is not yet in place: be carefull! External only output has been reported functional though.
<li>No DVI support: you have to use a standard VGA cable to connect external flatpanels;
<li>Embedded GeForce RAM detection is non-functional: please set amount manually for now via the nv.settings file (driver probably defaults to 1Mb if you don't). If you have overlay trouble, set a slightly smaller amount of RAM than you actually specified in the system BIOS (1Mb less or so);
<li>A few cards have hardcursor trouble. If you encounter this use the softcursor: select this via the nv.settings file;
<li>GeForce FX 5600 cards seem to have CRTC problems: the monitor shuts off and displays "refresh out of range";
<li>GeForce FX 5700 and FX 5950 are not yet supported (mail me if you own such a card!).
</ul>
<strong>Fixes for this version:</strong><br><br>
<ul>
<li>Added card recognition for some Nvidia GeForce4 Ti 4600 cards (ID 0x0252);
<li>GeForce overlay activation updated: hardware should respond to the first request instead of to the second ('stampTV' update);
<li>Included B_YCbCr422 hardware overlay for TNT 1/2 class cards (pre NV10 architecture).
</ul>
<hr>
<p><h1>nv_driver 0.06 (Rudolf)</h1></p>
<ul>
<li>Full 2D acceleration for TNT1 - GeForce FX cards;
<ul>
<li>Added full 2D acceleration for TNT1 - GeForce FX cards;
<li>Added card recognition for GeForce FX Go and some older laptop cards;
<li>Implemented retrace synchronisation (INT routine);
<li>Geforce overlay updated: turned off ints explicitly, corrected upscaling restriction to be 8x, small speed improvement;
<li>Vertical timing updated: missed a register on all GeForce cards, missed another register on older cards;
<li>Register unlocking updated: missed a register on all supported cards.
</ul>
<strong>Known limitations:</strong>
<ul>
<li>If the driver hangs your system on boot make sure you enabled 'assign IRQ to VGA card' in your system BIOS;
<li>256Mb RAM detection is still missing for cards that have that much of it;
<li>Flatpanel protection for laptops is not yet in place: be carefull! External only output has been reported functional though.
<li>no DVI support: you have to use a standard VGA cable to connect external flatpanels;
<li>Embedded GeForce RAM detection is non-functional: please set amount manually for now via the nv.settings file.
</ul>
<p><h1>nv_driver 0.05 (Rudolf)</h1></p>
<ul>
<li>Update on cursor move routine: pointer will nolonger accept illegal left-top positions. As a result it will nolonger vanish on some cards;
<li>Fixed hardware overlay on GeForce4 MX and Go series cards: disabled the embedded MPEG2 decoder engine which exist on these cards only;
<li>Fixed driver to adhere to the downscaling limitations of the new overlay engine existing in the GeForceFX series cards.
</ul>
<strong>Known limitations:</strong>
<ul>
<li>If the driver hangs your system on boot make sure you enabled 'assign IRQ to VGA card' in your system BIOS;
<li>256Mb RAM detection is still missing for cards that have that much of it;
<li>Flatpanel protection for laptops is not yet in place: be carefull! External only output has been reported functional though.
<li>no DVI support: you have to use a standard VGA cable to connect external flatpanels;
<li>Embedded GeForce RAM detection is non-functional: please set amount manually for now via the nv.settings file.
</ul>
<p><h1>nv_driver 0.04 (Rudolf)</h1></p>
<ul>
<li>New cursor_move sync_to_retrace for all supported cards: now all display distortions should be gone (GeForce4 for example);
<li>Added hardware overlay support for the entire GeForce series cards;
<li>Now powering up all card function blocks: dualhead cards should now switch to the connected head (by it's BIOS) instead of hanging the system on boot (tested on a dualhead GeForce4 with a DVI and a VGA connector).
</ul>
<strong>Known limitations:</strong>
<ul>
<li>256Mb RAM detection is still missing for cards that have that much of it;
<li>Flatpanel protection for laptops is not yet in place: be carefull! External only output has been reported functional though.
<li>no DVI support: you have to use a standard VGA cable to connect external flatpanels;
<li>Embedded GeForce RAM detection is non-functional: please set amount manually for now via the nv.settings file.
</ul>
<p><h1>nv_driver 0.03 (Rudolf)</h1></p>
<ul>
<li>Prevent system or video freeze on dragging files or so in tracker windows;
@@ -97,12 +48,6 @@
<li>Cursor bitmapadress setup modification for laptops: The cursor should be visible now also on 'Go' type of cards;
<li>BWindowScreen / Sync_to_retrace fix: prevent apps from crashing on endless waiting for retrace. Wait_for_retrace is temporary disabled now until it's actually implemented.
</ul>
<strong>Known limitations:</strong>
<ul>
<li>256Mb RAM detection is still missing for cards that have that much of it;
<li>Flatpanel protection for laptops is not yet in place: be carefull!
</ul>
With the 0.03 release most people should be able to use the driver for day to day use. My advice: use the lowest colordepth you can live with: this increases speed a lot! Meanwhile acceleration and overlay will hopefully be setup. Stay tuned! ;-)<br>
<p><h1>nv_driver 0.02 (Rudolf)</h1></p>
<ul>
<li>hardcursor support;
@@ -117,11 +62,6 @@ With the 0.03 release most people should be able to use the driver for day to da
<li>cardspecs are setup (faked PINS);
<li>several small fixes done to get the driver working correctly on all four of my cards: PCI TNT1, AGP TNT1, AGP TNT2 and AGP GeForce2MX400.
</ul>
<strong>Known limitations:</strong>
<ul>
<li>256Mb RAM detection is still missing for cards that have that much of it;
<li>Flatpanel protection for laptops is not yet in place: be carefull!
</ul>
<p><h1>Still todo:</h1></p>
<ul>
<li>Dualhead support on some GeForce series cards;