diff --git a/src/add-ons/kernel/drivers/graphics/skeleton/README.html b/src/add-ons/kernel/drivers/graphics/skeleton/README.html
index aac05c18c0..a50f6d1a84 100644
--- a/src/add-ons/kernel/drivers/graphics/skeleton/README.html
+++ b/src/add-ons/kernel/drivers/graphics/skeleton/README.html
@@ -2,61 +2,36 @@
- Readme for (open)BeOS Unified Nvidia graphics driver
+ Readme for Haiku skeleton graphics driver
-Unified Nvidia graphics driver for (open)BeOS
+Haiku skeleton graphics driver
NOTE PLEASE:
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!
Supported cards (as far as is known):
- - TNT 1/2;
-
- TNT 2-M64;
-
- Vanta/Aladdin TNT2;
-
- GeForce 256;
-
- GeForce 2 MX/Ti/GTS/Go;
-
- GeForce 2 Integrated GPU (Nforce);
-
- GeForce 3 (Ti);
-
- GeForce 4 MX/Ti/Go;
-
- GeForce 4 Integrated GPU (Nforce 2);
-
- GeForce FX 5200/5600/5700/5800/5900/5950/Go;
-
- Quadro (2/4/FX/Go);
-
- Some GeForce PCIe cards.
+
- None.
Features:
- - Hardware cursor support (on both heads on dualhead cards);
-
- Full 2D acceleration;
-
- Full BWindowScreen support (used for hardware pageflipping, scrolling/panning and acceleration in applications/games);
-
- DPMS support for analog connected screens (on both heads on dualhead cards);
-
- B_YCbCr422 hardware overlay support on both TNT and GeForce series cards (overlay follows head in dualhead stretch/switch modes);
-
- Dualhead support on GeForce dualhead cards (use Mark Watson's 'Dualhead Setup' from BeBits for now);
-
- DVI and laptop panel (widescreen) support;
-
- Basic AGP mode support on AGP cards, using the new (seperate) (open)BeOS AGP busmanager;
-
- Coldstart support for analog connected screens on most cards except TNT1, GeForce 6600 and GeForce 6800.
+
- None.
Known limitations:
- - If the driver does not load make sure you enabled 'assign IRQ to VGA card' in your system BIOS;
-
- If the driver still 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). Make sure you mail me if you still have trouble but also if this version fixed that!
-
- If on a laptop the internal panel doesn't work when you connect an external monitor, make sure you set 'output device selection' to 'internal' (instead of 'auto') in the system BIOS if it has such an option. If you have this symptom on a normal card, or on a laptop without that BIOS option then you are probably out of luck for dualhead support.
+
- Everything you can think of.
Installation:
-If you encounter bugs, please checkout the driver's website to see if it's already on the todo list. You can also checkout the UPDATE 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 bugreport form on the site or send me an Email. Make sure you are as precise as possible because that will make things easier to trackdown and fix...
-
-
-OK, now that's all said let's get to it ;-)
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.
-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 disable user addons the system will load it's own drivers. If you don't do anything, the system will load the (open)BeOS Nvidia TNT/GeForce graphics driver.
+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 disable user addons the system will load it's own drivers. If you don't do anything, the system will load the Haiku skeleton graphics driver.
-Note: This might turn out to be handy if you run into trouble upon testing the driver, or if you are 'tweaking' the nv.settings file...
+Note: This might turn out to be handy if you run into trouble upon testing the driver, or if you are 'tweaking' the skel.settings file...
actual INSTALLATION:
@@ -72,41 +47,34 @@ Unzip the zip file that contains the driver to the root folder. Now reboot and y
Currently there's no uninstall script included. Just do it manually:
-Delete the nv.accelerant file in home/config/add-ons/accelerants/
-Delete the nv.driver file in home/config/add-ons/kernel/drivers/bin/
-Delete the nv.settings file in home/config/settings/kernel/drivers/
-Delete the nv.driver shortcut in home/config/add-ons/kernel/drivers/dev/graphics/ which pointed to the file nv.driver.
+Delete the skel.accelerant file in home/config/add-ons/accelerants/
+Delete the skel.driver file in home/config/add-ons/kernel/drivers/bin/
+Delete the skel.settings file in home/config/settings/kernel/drivers/
+Delete the skel.driver shortcut in home/config/add-ons/kernel/drivers/dev/graphics/ which pointed to the file skel.driver.
You have to reboot in order to apply the original configuration.
Settings:
-Please read this information carefully *before* installing and using the (open)BeOS Nvidia TNT/GeForce graphics driver. It might spare you some trouble afterwards..
-The driver uses a file named nv.settings to determine how to use your card. After installation this file will be located at home/config/settings/kernel/drivers/. 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.
+Please read this information carefully *before* installing and using the Haiku skeleton graphics driver. It might spare you some trouble afterwards..
+
The driver uses a file named skel.settings to determine how to use your card. After installation this file will be located at home/config/settings/kernel/drivers/. 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.
Note: The driver only reads this file during it's initialisation. This means that you have to reboot in order to let changes take effect.
-nv.settings driver configuration:
+skel.settings driver configuration:
- usebios:
The name of this item may be somewhat misleading, it might be changed in the future. It actually tells the driver if it should coldstart the card or not. The driver will rely on the VGA BIOS to have coldstarted the card before BeOS booted if you specify 'true'.
To make things look even more complex the driver might actually use the BIOS to determine your cards specifications on *both* possible settings.
- false:
- If you specify usebios false the driver will attempt to coldstart the card, which is the preferred way of doing it because of the better tuned setup if all is right. Unfortunately there's not enough info available to make this work reliably, so it's not used by default. This setting would enable you to use your nVidia card as a secondary card in your system. Be advised though that BeOS officially does not (yet) support multiple VGA cards, so you need special software in order to be able to actually use it (a video consumer node for instance).
+ If you specify usebios false the driver will attempt to coldstart the card, which is the preferred way of doing it because of the better tuned setup if all is right. Unfortunately there's not enough info available to make this work reliably, so it's not used by default. This setting would enable you to use your card as a secondary card in your system. Be advised though that BeOS officially does not (yet) support multiple VGA cards, so you need special software in order to be able to actually use it (a video consumer node for instance).
- true: (default setting)
- Specify usebios true unless you want to try to use a nVidia card as a secondary card in your system.
+ Specify usebios true unless you want to try to use a card as a secondary card in your system.
- Notes:
-
- - On driverversion 0.23 and before usebios had no effect at all. The cards were never coldstarted;
-
- Coldstarting should work on most cards except TNT1, GeForce 6600 and GeForce 6800;
-
- Coldstarting will not yet work with laptop- and DVI panels;
-
- Coldstarting should fix the 'bandwidth trouble' existing on some GeForce2 cards.
-
- memory: (disabled by default)
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!).
This option is disabled by default (preceded by a '#').
@@ -119,7 +87,7 @@ This option is disabled by default (preceded by a '#').
A software cursor 'flickers' a bit sometimes because it has to be redrawn constantly. So hardcursor true is the preferred setting. For DirectWindow windowed mode functionality you need to use this setting also (Chart demo app for instance).
logmask: (set to minimal by default)
-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 nv.accelerant.0.log in your ~ (home) 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 nv.accelerant.1.log, and it will also be in your home folder.
+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 skel.accelerant.0.log in your ~ (home) 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 skel.accelerant.1.log, and it will also be in your home folder.
Note:
- 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').
@@ -130,7 +98,7 @@ Dumprom is another 'tool' for bug-tracking purposes.
- false: (default setting)
Keep it set to dumprom false, unless you want the driver to dump the contents of your VGA BIOS ROM in a file.
- true:
- dumprom true lets the driver dump a copy of your VGA BIOS in a file called nv.rom in your ~ (home) folder.
+ dumprom true lets the driver dump a copy of your VGA BIOS in a file called skel.rom in your ~ (home) folder.
switchhead:
The driver always autodetects which output should be used as primary one, but you can let the driver 'invert' the outcome of that detection with this option (only for dualhead cards).
@@ -160,9 +128,9 @@ Keep this option set to force_pci false, unless the graphics ca
This option is only used if your card is running in AGP mode. It's a real tweak option. It's officially unsupported, and it's unknown if it can do harm to your card or system. It exists because using it can speedup unaccelerated graphics a lot. Think about video playback or playing quake2 in software rendering mode...
- false: (default setting)
-Keep this option set to unhide_fw false unless you are certain you want to try the 'unsupported' graphics speedup. NV15, NV18, NV28 and NV34 cards for example probably don't need it as they officially support the AGP FW (fastwrites) feature already. On cards supporting FW by default the unhide_fw option has no effect.
+Keep this option set to unhide_fw false unless you are certain you want to try the 'unsupported' graphics speedup. On cards supporting FW by default the unhide_fw option has no effect.
- true:
-If you have an older card that officially doesn't support the AGP FW feature, you could possibly get this feature anyway by setting unhide_fw true. For instance (some) NV11 cards work nicely with AGP FW enabled this way and unaccelerated graphics speedup considerably. Please make sure that at the first sign of trouble (system hanging, displaying artifacts, etc) you disable this feature here again, or you might risk destroying your card and/or AGP slot.
+If you have an older card that officially doesn't support the AGP FW feature, you could possibly get this feature anyway by setting unhide_fw true. Please make sure that at the first sign of trouble (system hanging, displaying artifacts, etc) you disable this feature here again, or you might risk destroying your card and/or AGP slot.
pgm_panel:
This option only has an effect if you have a laptop panel or DVI panel connected. It's existing because it's currently impossible to setup the driver in a way every single panel outthere is happy about it.
@@ -177,6 +145,6 @@ With the pgm_panel true setting, the driver will fix your panel
Rudolf Cornelissen.
-(Page last updated on November 1, 2004)
+(Page last updated on November 4, 2004)