Aren
/
haiku
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

initial import of skeleton graphics kerneldriver (not yet working/stripped) 

git-svn-id: file:///srv/svn/repos/haiku/trunk/current@9784 a95241bf-73f2-0310-859d-f6bbb57e9c96
This commit is contained in:
Rudolf Cornelissen 2004-11-04 12:37:27 +00:00
parent 6835336864
commit 08a017dc15
5 changed files with 1595 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

29
src/add-ons/kernel/drivers/graphics/skeleton/Jamfile Normal file
View File

@ -0,0 +1,29 @@
SubDir OBOS_TOP src add-ons kernel drivers graphics skeleton ;
UsePrivateHeaders graphics ;
UsePrivateHeaders [ FDirName graphics skeleton ] ;
R5KernelAddon skel.driver : kernel drivers bin :
driver.c
;
Package haiku-skeleton-cvs :
README.html UPDATE.html ;
Package openbeos-skeleton-cvs :
skel.driver :
boot home config add-ons kernel drivers bin ;
Package haiku-skeleton-cvs :
<kernel!drivers!dev!graphics>skel.driver :
boot home config add-ons kernel drivers dev graphics ;
Package haiku-skeleton-cvs :
skel.settings :
boot home config settings kernel drivers ;
# Link to kernel/drivers/dev/graphics
{
local dir = [ FDirName $(OBOS_ADDON_DIR) kernel drivers dev graphics ] ;
local instDriver = <kernel!drivers!dev!graphics>skel.driver ;
MakeLocate $(instDriver) : $(dir) ;
RelSymLink $(instDriver) : skel.driver ;
}

182
src/add-ons/kernel/drivers/graphics/skeleton/README.html Normal file
View File

@ -0,0 +1,182 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="GENERATOR" content="The DarkSite">
<title>Readme for (open)BeOS Unified Nvidia graphics driver</title>
</head>
<body>
<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!</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;
<li>GeForce 2 Integrated GPU (Nforce);
<li>GeForce 3 (Ti);
<li>GeForce 4 MX/Ti/Go;
<li>GeForce 4 Integrated GPU (Nforce 2);
<li>GeForce FX 5200/5600/5700/5800/5900/5950/Go;
<li>Quadro (2/4/FX/Go);
<li>Some GeForce PCIe cards.
</ul>
<br>
<hr>
<h2>Features:</h2>
<ul>
<li>Hardware cursor support (on both heads on dualhead cards);
<li>Full 2D acceleration;
<li>Full BWindowScreen support (used for hardware pageflipping, scrolling/panning and acceleration in applications/games);
<li>DPMS support for analog connected screens (on both heads on dualhead cards);
<li>B_YCbCr422 hardware overlay support on both TNT and GeForce series cards (overlay follows head in dualhead stretch/switch modes);
<li>Dualhead support on GeForce dualhead cards (use Mark Watson's 'Dualhead Setup' from BeBits for now);
<li>DVI and laptop panel (widescreen) support;
<li>Basic AGP mode support on AGP cards, using the new (seperate) (open)BeOS AGP busmanager;
<li>Coldstart support for analog connected screens on most cards except TNT1, GeForce 6600 and GeForce 6800.
</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 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!
<li>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.
</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:info.be-hold@inter.nl.net">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 Nvidia TNT/GeForce graphics driver.<br>
<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 nv.settings file...<br>
<br><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>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>
<br>
<hr>
<a name="settings"></a><h2>Settings:</h2><br>
Please read this information carefully *before* installing and using the (open)BeOS Nvidia TNT/GeForce graphics driver. It might spare you some trouble afterwards..<br>
<p>The driver uses a file named <strong>nv.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>
<br>
<strong>Note:</strong> The driver only reads this file during it's initialisation. This means that you have to reboot in order to let changes take effect.<br>
<br>
<br>
<br>
<strong>nv.settings driver configuration:</strong><br>
<ul>
<li><strong>usebios:</strong><br>
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'.<br>
To make things look even more complex the driver might actually use the BIOS to determine your cards specifications on *both* possible settings.
<ul>
<li><strong>false:</strong><br>
If you specify <strong>usebios false</strong> 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).
<li><strong>true:</strong> (default setting)<br>
Specify <strong>usebios true</strong> unless you want to try to use a nVidia card as a secondary card in your system.
</ul>
<strong>Notes:</strong>
<ul>
<li>On driverversion 0.23 and before usebios had no effect at all. The cards were never coldstarted;
<li>Coldstarting should work on most cards except TNT1, GeForce 6600 and GeForce 6800;
<li>Coldstarting will not yet work with laptop- and DVI panels;
<li>Coldstarting should fix the 'bandwidth trouble' existing on some GeForce2 cards.
</ul>
<li><strong>memory:</strong> (disabled by default)<br>
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 (on one or both of the heads), 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. 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.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').
</ul>
<li><strong>dumprom:</strong><br>
Dumprom is another 'tool' for bug-tracking purposes.
<ul>
<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>nv.rom</strong> in your <strong>~ (home)</strong> folder.
</ul>
<li><strong>switchhead:</strong><br>
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).
<ul>
<li><strong>false:</strong> (default setting)<br>
Keep it set to <strong>switchhead false</strong>, unless you feel you want the card's other output to be used as primary one. Note that if a single connected screen is found, that screen will be the driver's primary output with this setting.
<li><strong>true:</strong><br>
<strong>switchhead true</strong> lets the driver 'invert' the output assignments for all modes. Use only when you have two screens connected, otherwise the one connected screen will remain black as the other (not connected) output is being used.<br>
</ul>
<strong>Note:</strong>
<ul>
<li>If the driver determines it cannot use a digital panel <strong>despite</strong> it being physically connected and powered on, using the switchhead option will not fix this. This is no fault in your card or the panel, but happens only because the driver relies on certain functions inside your cards BIOS to behave in a certain way.
</ul>
<li><strong>force_pci:</strong><br>
On AGP cards you can block the use of AGP mode transfers.
<ul>
<li><strong>false:</strong> (default setting)<br>
Keep this option set to <strong>force_pci false</strong>, unless the graphics card or motherboard has trouble using AGP.
<li><strong>true:</strong><br>
<strong>force_pci true</strong> prevents the graphicsdriver from activating AGP mode, so it will be using PCI mode like it has always been in the past. The downside of this is that this comes at a performance penalty if your motherboard supports the AGP 'fastwrite' (FW) option, which won't be utilized with this setting.
</ul>
<strong>Note:</strong>
<ul>
<li>If you have trouble using AGP mode, you should prefer tweaking the AGP busmanager settings file as it might well enable you to use a 'lesser' AGP mode instead of falling back to PCI mode alltogether.
</ul>
<li><strong>unhide_fw:</strong><br>
This option is only used if your card is running in AGP mode. It's a real <strong>tweak</strong> option. It's officially unsupported, and it's unknown if it can do harm to your card or system. It exists because using it <strong>can</strong> speedup unaccelerated graphics <strong>a lot</strong>. Think about video playback or playing quake2 in software rendering mode...
<ul>
<li><strong>false:</strong> (default setting)<br>
Keep this option set to <strong>unhide_fw false</strong> 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.
<li><strong>true:</strong><br>
If you have an older card that officially doesn't support the AGP FW feature, you could possibly get this feature anyway by setting <strong>unhide_fw true</strong>. For instance (some) NV11 cards work nicely with AGP FW enabled this way and unaccelerated graphics speedup considerably. Please <strong>make sure</strong> that at the first sign of trouble (system hanging, displaying artifacts, etc) you disable this feature here again, or you might risk <strong>destroying</strong> your card and/or AGP slot.
</ul>
<li><strong>pgm_panel:</strong><br>
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.
<ul>
<li><strong>false:</strong><br>
If you select <strong>pgm_panel false</strong> the driver will not program the panel's pixelclock (refreshrate). Instead it relies on your cardBIOS to have done that correctly. While this is probably the case, it might introduce some displaying errors every now and then.
<li><strong>true:</strong> (default setting)<br>
With the <strong>pgm_panel true</strong> setting, the driver will fix your panel's refreshrate to 60Hz. While this should be working on all panels outthere, some panels are particular picky about refreshrates below 60.0Hz (they shut off), and some other panels are particular picky about refreshrates above 60.0Hz (they shut off). While the driver requests the hardware to set 60.0Hz, this isn't exactly possible, so the actual setting is <strong>bound</strong> to be a tiny bit below or above 60.0Hz.
</ul>
</ul>
<hr>
<br>
<a href="mailto:info.be-hold@inter.nl.net">Rudolf Cornelissen.</a>
<p>(Page last updated on November 1, 2004)</p>
</body>
</html>

156
src/add-ons/kernel/drivers/graphics/skeleton/UPDATE.html Normal file
View File

@ -0,0 +1,156 @@
<html>
<head>
<title>Changes</title>
</head>
<body>
<p><h2>Changes done for each driverversion:</h2></p>
<p><h1>nv_driver 0.30, (Rudolf)</h1></p>
<ul>
<li>Overlay fix for GeForce2 and GeForce4 MX Integrated GPU boards: updated RAM amount detection. The last 64Kb RAM is used for the card's BIOS or something so it's not available to the graphicsdriver;
<li>Enabled coldstart switch setting (called 'usebios' in nv.settings) in drivercode. Changed the default setting to keep the driver working in the same way it did before;
<li>Added recognition for 25 new cards including the first PCI-express (PCX) cards: FX/PCX 6800, FX 6600, PCX 5300/5750/5900, PCX Quadro. New 'old style' cards: Quadro FX 700, Quadro FX 1000 Go, FX 5100 and FX 5700 Go. While FX6800 still seems to be non-functional, a Quadro4 280 NVS PCIe (GeForce PCX 5300 PCIe) has been confirmed working OK already;
<li>Card coldstarts should now be operational (if enabled in nv.settings) on most cards, except TNT1, GeForce 6600 and GeForce 6800. Tested successfully on TNT2/TNT2-M64 (NV05), GeForce2 MX400 (NV11), GeForce4 MX440 (NV18), GeForce4 Ti4200 (NV28) and GeForce FX5200 (NV34). Note however that laptop panels and DVI panels will not work via coldstarting yet!
<li>The 'bandwidth trouble' existing on older cards, especially on some GeForce2 types, should be fixed now if you enable card coldstarting for these cards. Note that this problem existed because of a fault in these card's BIOSes (they missed some specific register programming). Confirmed a NV15 working OK now.
</ul>
<p><h1>nv_driver 0.22, (Rudolf)</h1></p>
<ul>
<li>Added AGP mode capability on AGP cards along with the option to block it in nv.settings. No GART and AGP aperture support; but if your card and system AGP host bridge support the 'fastwrite' (FW) feature, you'll notice a nice speedup of unaccelerated graphics.
<ul>
<li>Tested Quake 2 in software rendering mode over here using timedemo1 with demo1.dm2: framerates jumped up to 140% of the 'original' in AGP2.0 4X mode!
<li>Also tested video playback using bitmap output mode: CPU load drops considerably depending on desktop colordepth and size of the video output window.<br>
<li>2D acceleration will not speedup because it's working 'local', so within the graphics cards engine and it's RAM only.
</ul>
<strong>Note please:</strong><br>
<ul>
<li>You need the new (seperate) (open)BeOS AGP busmanager module that has been setup for this feature, without it you will remain using PCI mode as usual.
<li>If you have trouble with AGP, you have the option to shut it off by setting 'force_pci true' in nv.settings. You are adviced however to tweak the AGP busmanager settings file instead, as this might enable you to keep using AGP mode, be it in a slower setting.
</ul>
<li>Updated CRTC modeline tuning for panels: this should fix the 'right-shifted' picture on some panels in their native modes;
<li>Fixed BIOS ROM dump (to file) option;
<li>Fixed GET_TIMING_CONSTRAINTS and GET_ACCELERANT_DEVICE_INFO accelerant hooks to return valid data; updated modeline checking and modification code (used by ProposeDisplayMode) to adhere to one more timing constraint
<li>Lowered fixed refreshrate setting for panels to be 60Hz now: it turns out panels exist that are picky 'on the high side' as well;
<li>Added option in nv.settings to block refreshrate programming if a flatpanel is active: this should enable support on picky panels;
<li>Added option in nv.settings to 'unhide' fastwrite support in AGP cards. Some older cards support FW even though normally they don't show it so it won't get activated (confirmed GeForce2 MX400, NV11).<br>
<strong>NOTE please:</strong><br>
This is a tweak that you <strong>can</strong> enable, but you do so at your own risk (of course)!
<li>Fixed RAM amount detection for GeForce2 and GeForce4 MX Integrated GPU boards.
</ul>
<p><h1>nv_driver 0.10, (Rudolf)</h1></p>
<ul>
<li>Implemented laptop internal flatpanel presence and native resolution detection;
<li>Implemented external DVI flatpanel(s) presence and native resolution detection;
<li>Added flatpanel(s) refreshrate protection: it(they) is(are) always kept at 62Hz refresh (60Hz shuts off some panels);
<li>Added flatpanel specific CRTC modeline and DFP modeline tuning: DVI connected panels work now on both heads (if applicable);
<li>Added aspect correction programming for flatpanels: corrects if mode aspect differs too much from panel aspect;
<li>Fixed acceleration engine management regarding sync_to_token: no more updating glitches should occur now;
<li>Added recognition for GeForce4 MX 4000, GeForceFX 5700LE and GeForceFX 5700VE cards; also modified a few others to be more correct;
<li>Implemented virtualized CRTC1/DAC1 and CRTC2/DAC2 access: when one flatpanel is found on a card that panel is always primary output now;
<li>Dualhead switch mode is operational with flatpanels now (via the virtualized setup);
<li>The user has the option to select the primary output via nv.settings now (via the new 'switchhead' option);
<li>Modified analog type monitor detection to work the same as for digital panels (detect on bootup only);
<li>Added dualhead switch mode for NV11 (works via virtualized head access implemented now);
<li>Modified dualhead switch mode for all other cards to work via the virtualized head access also;
<li>Modified overlay to work correctly with the virtualized setup;
<li>Added output-devices/heads matrix setup: the driver now selects the right head for primary output and dualhead should work for all cards with all monitor-types now (if connected before boot);
<li>Updated head selection code for register programming: NV11 needs a special treatment (again); NV11 dualhead modes are finally OK now, including switch mode;
<li>Updated secondary head specs: they are improved for nview cards (like GeForce4 and FX) in comparison to twinview cards (like GeForce2);
<li>Added move_overlay() so overlay (finally) works correctly in virtualscreens;
<li>You can now select upto one more 4:3 aspect, and 6 new 16:10 aspect modes by just selecting them from the Screenprefs app, <strong>except</strong> if you use the native R5 one. Use Dualhead setup instead (for example):
<ul>
<li>Added standard (4:3 aspect) mode 1400x1050 for panels and analog monitors to the modelist exported by the driver;
<li>Added widescreen (16:10 aspect) modes 800x500, 1024x640, 1280x800, 1440x900, 1680x1050 and 1920x1200 for panel(s) to the modelist exported by the driver if only widescreen panel(s) is (are) connected (so also no analog monitors may be connected!);
<li>Added blocking of modes above panel (with lowest) native resotution: this includes blocking of all widescreen modes if a non-widescreen (analog) screen is detected.
</ul>
<li>Cursor update for dualhead cards: when the 'softcursor' is used, the hardcursors are <strong>both</strong> actually turned off now.
</ul>
<br>
<strong>NOTE:</strong><br>
The features below are shutdown because they are possibly dangerous without feedback: No documentation on this exists, so this was setup by me tested on my cards only. Feedback (<strong>logfiles!</strong>) you might send to me might help me gain more info about <strong>IF</strong> we can use (or need) this, and <strong>IF</strong> it's OK to use it for a later driver release.
<ul>
<li>Added flatpanel LVDS and TMDS transmitters powerup if a panel is detected (not finished: needs more feedback);
<li>Added flatpanel DPMS support for both heads via powerup/powerdown of LVDS and TMDS transmitters (not finished: needs more feedback).
</ul>
<p><h1>nv_driver 0.09, (Rudolf)</h1></p>
<ul>
<li>Fixed NV11 trouble with repeating screen(s) on the right side of the monitor;
<li>Updated CRTC memory granularity code to work-around a hardware bug in older cards;
<li>Fixed fuzzy modes / no picture on GeForceFX 5700 cards: PLL discriminator restrictions updated.
</ul>
<p><h1>nv_driver 0.08, (Rudolf)</h1></p>
<ul>
<li>Fixed GeForceFX 5600 and FX 5700 monitor 'refresh out of range' / shutoff fault. nVidia changed the pixelPLL for the NV31 and NV36;
<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;
<li>Added card recognition for GeForceFX 5700, FX 5950 and some other (older) cards;
<li>Added 256Mb RAM detection;
<li>Improved startup code: this should (could) fix random trouble on some cards like for instance hardcursor trouble on especially laptops;
<li>Added dualhead support (use Mark Watson's 'Dualhead Setup' from BeBits for now);
<li>Updated mode granularity and max virtual size checking/limiting;
<li>Added dualhead support for 8- and 15bit colordepths;
<li>Fixed move_display distortions in virtualscreens especially visible in 8-bit colordepth (for both heads);
<li>Added 'overlay follows head' for dualhead stretch and switch modes: if more than half the overlay output window is on a screen, that screen gets the overlay output;
<li>Added dualhead switch mode (except for NV11 cards as they do not have output connector switching capability);
<li>Added monitor presence detection for both monitor output connectors on dualhead cards (analog type signals only);
<li>Added 'output follows monitor' for all modes: it does not matter on which connector you connect your monitor, the output will go there after setting a mode; like the card's BIOS does (except for NV11 cards as they do not have output connector switching capability).
</ul>
<p><h1>nv_driver 0.07 (Rudolf)</h1></p>
<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>
<p><h1>nv_driver 0.06 (Rudolf)</h1></p>
<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>
<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>
<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>
<p><h1>nv_driver 0.03 (Rudolf)</h1></p>
<ul>
<li>Prevent system or video freeze on dragging files or so in tracker windows;
<li>Pre NV10 cursor sync_to_retrace: no more distortions in cursor bitmaps on moving it;
<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>
<p><h1>nv_driver 0.02 (Rudolf)</h1></p>
<ul>
<li>hardcursor support;
<li>virtual screens / BWindowScreen support including panning/scrolling;
<li>colorspace selection;
<li>colorpalette setup;
<li>refreshrate selection;
<li>85 cards of 4 brands are detected now: These are all TNT1 - GeForce FX5900 Ultra cards as far as I know. Hopefully all those cards will actually work OK with the driver;
<li>DPMS support;
<li>resolution selection (CRTC setup);
<li>switch to 'enhanced mode' included: VESA is gone now!
<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>
<p><h1>Still todo:</h1></p>
<ul>
<li>TVout support;
<li>Improve/extend various stuff when/if possible.
</ul>
</p>
</body>
</html>

1171
src/add-ons/kernel/drivers/graphics/skeleton/driver.c Normal file
View File

File diff suppressed because it is too large Load Diff

57
src/add-ons/kernel/drivers/graphics/skeleton/skel.settings Normal file
View File

@ -0,0 +1,57 @@
# Settings file for the nv driver and accelerant
#
# This file should be moved to the directory
# ~/config/settings/kernel/drivers/
#
# nv.driver parameters
# accelerant "nv.accelerant"
# nv.accelerant parameters
usebios true # if true rely on bios to coldstart the card
#memory 2 # in MB, override builtin memory size detection
hardcursor true # if true use on-chip cursor capabilities
#logmask 0x00000000 # nothing logged, is default
#logmask 0x08000604 # log overlay use in full
#logmask 0xffffffff # log everything
dumprom false # dump bios rom in ~/nv.rom
switchhead false # switch head assignment (dualhead cards only)
force_pci false # block AGP mode use if true (AGP cards only)
# WARNING: tweak alert! modify stuff below on your own risk...
unhide_fw false # if true 'unhide' cards AGP fastwrite support on cards that hide it
pgm_panel true # if false don't program DVI and laptop panel pixelclocks (refreshrates)
#--------- that's all.
#logmask setup info:
#log level select:
#logmask 0x0000000x # lowest digit: bitmask to select logging level.
#log modules select:
#logmask 0xxxxxxxx0 # highest 7 digits: bitmask to select individual modules to log.
#log modules:
#logmask 0x00000100 # engine: agp
#logmask 0x00000200 # engine: bes
#logmask 0x00000400 # overlay
#logmask 0x00000800 # engine: support
#logmask 0x00001000 # engine: dac2
#logmask 0x00002000 # engine: info
#logmask 0x00004000 # engine: i2c
#logmask 0x00008000 # engine: general
#logmask 0x00010000 # engine: dac1
#logmask 0x00020000 # engine: crtc2
#logmask 0x00040000 # engine: crtc1
#logmask 0x00080000 # engine: acc
#logmask 0x00100000 # engine: brooktree tv
#logmask 0x00200000 # set displaymode
#logmask 0x00400000 # propose displaymode
#logmask 0x00800000 # init accelerant
#logmask 0x01000000 # get timing constraints
#logmask 0x02000000 # get mode info
#logmask 0x04000000 # get device info
#logmask 0x08000000 # get accelerant hook
#logmask 0x10000000 # engine management
#logmask 0x20000000 # cursor
#logmask 0x40000000 # acceleration