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

DPMS update completed

Browse Source 
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@7756 a95241bf-73f2-0310-859d-f6bbb57e9c96
This commit is contained in:
Rudolf Cornelissen 2004-06-06 10:29:42 +00:00
parent 3794f85ae6
commit e85b66ba46
2 changed files with 20 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
src/add-ons/kernel/drivers/graphics/neomagic/README.html
View File

@ -12,7 +12,7 @@ You use this software at your own risk! Although I don't expect it to damage you
<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>
This driver is still alpha quality. 2D acceleration is still lacking for some cards, 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)
@ -31,26 +31,26 @@ This driver is still alpha quality. 2D acceleration is still lacking, overlay do
<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>
<li>B_YCbCr422 hardware overlay support (except on MagicGraph 128, so NM2070 cards);
<li>DPMS support for both panels and external displays;
<li>Full 2D acceleration for NM2070, NM2097 and NM2160 (current CVS version and up).
</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.
<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>
<li>Stretching modes for the laptop display panel will not be setup because in stretched modes no hardcursor is supported, and overlay output requires tweaking to get going;
<li>If your laptop doesn't work with the driver (distorted/black screen), make sure you disabled LCD stretching/zooming or whatever it's called in the system BIOS;
<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 higher resolution modes on other workspaces for now.
<li>The keyboard 'shortcut key' for changing output devices bypasses the graphics driver and directly uses the cardBIOS. Sometimes using this key will have undesired results. Please use with care! Or better yet: just preset the output device(s) you want in the system BIOS (if possible). If you are going to use that shortcut key anyway: then make sure you switch workspaces between spaces with different settings after using it, so the driver updates the card programming again (so it gets in sync with the card again);
<li>Overlay is not yet working correctly on NM2200 and later cards: if you have such a card and want to help by testing stuff, let me know!
<li>On NM2070 panel centering only works vertically: horizontal centering-related info is missing.
</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:rag.cornelissen@inter.nl.net">Email</a>. Make sure you are as precise as possible because that will make things easier to trackdown and fix...<br>
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: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>
@ -122,7 +122,7 @@ Dumprom is another 'tool' for bug-tracking purposes.
<hr>
<br>
<a href="mailto:rag.cornelissen@inter.nl.net">Rudolf Cornelissen.</a>
<p>(Page last updated on January 8, 2004)</p>
<a href="mailto:info.be-hold@inter.nl.net">Rudolf Cornelissen.</a>
<p>(Page last updated on June 6, 2004)</p>
</body>
</html>

8
src/add-ons/kernel/drivers/graphics/neomagic/UPDATE.html
View File

@ -4,7 +4,7 @@
</head>
<body>
<p><h2>Changes done for each driverversion:</h2></p>
<p><h1>head (0.06-15, Rudolf)</h1></p>
<p><h1>head (0.06-16, 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;
@ -22,7 +22,8 @@
<li>Added fixed sync polarity programming if flatpanel in use: needed to make sure centering actually works;
<li>Disabling centering if external only monitor mode is active: fixes some trouble on NM2070 and maybe others;
<li>Added panel modeline programming for NM2070 cards: fixes hardcursor trouble on panel;
<li>Added pixelprecise panning for virtualscreens in all modes.
<li>Added pixelprecise panning for virtualscreens in all modes;
<li>Added full DPMS support.
</ul>
Note:<br>
Acceleration engine benchmarked and tested for errors with BeRoMeter V1.2.6.
@ -52,9 +53,8 @@ Acceleration engine benchmarked and tested for errors with BeRoMeter V1.2.6.
<p><h1>Still todo:</h1></p>
<ul>
<li>fix for trouble with booting into modes above 800x600 resolution on some cards (please report this behaviour!);
<li>BIOSmode register programming needed for 'full' KB switch BIOS support(?);
<li>2D acceleration (in progress);
<li>MagicMedia series overlay update: still contains errors apparantly.
<li>MagicMedia series overlay update: still contains errors.
</ul>
</p>
</body>