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

updated docs (working cards, DMA mode info).

Browse Source 
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@11365 a95241bf-73f2-0310-859d-f6bbb57e9c96
This commit is contained in:
Rudolf Cornelissen 2005-02-13 17:54:11 +00:00
parent 658ffe9fcf
commit de0194f56b
2 changed files with 17 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
src/add-ons/kernel/drivers/graphics/nvidia/README.html
View File

@ -21,9 +21,10 @@ You use this software at your own risk! Although I don't expect it to damage you
<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.
<li>GeForce (4 MX) PCX 4300;
<li>GeForce FX/PCX 5200/5300/5600/5700/5750/5800/5900/5950/Go;
<li>GeForce FX/PCX 6200/6600/6800/Go;
<li>Quadro (2/4/FX/PCX/Go).
</ul>
<br>
<hr>
@ -33,11 +34,11 @@ You use this software at your own risk! Although I don't expect it to damage you
<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>B_YCbCr422 hardware overlay support on both TNT and GeForce series cards, except for GeForce 6200 and 6600 (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.
<li>Coldstart support for analog connected screens on most cards except TNT1, GeForce 6200, 6600 and 6800.
</ul>
<strong>Known limitations:</strong>
<ul>
@ -156,6 +157,14 @@ Keep this option set to <strong>force_pci false</strong>, unless the graphics ca
<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>dma_acc:</strong><br>
You can select one of two methods for (2D) acceleration here: PIO mode and DMA mode. DMA mode works 2-3 times as fast as PIO mode on modern CPU's (beyond 2Ghz or so), and should still match the PIO mode speed on slower CPU's (below 500Mhz).
<ul>
<li><strong>false:</strong><br>
If the default setting does not work as expected, you can try falling back to PIO mode acceleration. Note however that PIO mode is currently not working on NV40 and higher GPU's (GeForce 6200, 6600 and 6800 like types). Also, chances are that this method of acceleration will be removed in future driverversions (so be sure to let me know if you are having trouble with DMA mode!).
<li><strong>true:</strong> (default setting)<br>
<strong>dma_acc true</strong> enables DMA cmd fetching by the GPU for (2D) acceleration instead of using the old PIO method (which directly programs acceleration commands inside the GPU). The DMA method works (much) faster than PIO mode depending on system CPU speed. Also the DMA method is the only method that works on NV40 and higher GPU's (GeForce 6200, 6600 and 6800 like types) currently.
</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>
@ -177,6 +186,6 @@ With the <strong>pgm_panel true</strong> setting, the driver will fix your panel
<hr>
<br>
<a href="mailto:info.be-hold@inter.nl.net">Rudolf Cornelissen.</a>
<p>(Page last updated on November 1, 2004)</p>
<p>(Page last updated on February 13, 2005)</p>
</body>
</html>

4
src/add-ons/kernel/drivers/graphics/nvidia/UPDATE.html
View File

@ -6,11 +6,11 @@
<p><h2>Changes done for each driverversion:</h2></p>
<p><h1>head (cvs 0.36, Rudolf)</h1></p>
<ul>
<li>Execution of acceleration commands is re-setup. Now it should be possible to use more engine commands than there are FIFO channels for them, by doing on-the-fly reconfiguring. This should be especially usefull when 3D acceleration is going to be setup later on;
<li>Execution of acceleration commands (PIO mode) is re-setup. Now it should be possible to use more engine commands than there are FIFO channels for them, by doing on-the-fly reconfiguring. This should be especially usefull when 3D acceleration is going to be setup later on;
<li>Added recognition for 20 new cards: Some (new) GeForce 6200, 6600 and 6800 types are now recognized;
<li>Modified cursor to be hardware synchronized to the screen's vertical retrace. This fixes the high CPU load on moving the mouse especially while being on the bottom of the screen (all GeForce series cards);
<li>Added new acceleration method using DMA command fetching. You can now choose beween (the old) PIO mode and (the new) DMA mode acceleration via a new switch in nv.settings (DMA mode is default). DMA acceleration is say 2-3 times as fast as PIO mode acceleration on systems with relative fast CPU's (above 2Ghz or so). On relative slow CPU's (500Mhz or lower) there is no speedgain left and both methods match about up.<br>
Note that on NV40 and higher only DMA mode acceleration currently works ('fix' in progress).
<strong>Note please:</strong> On NV40 and higher only DMA mode acceleration currently works.
</ul>
<p><h1>nv_driver 0.30, (Rudolf)</h1></p>
<ul>