From 898ec61104910812ae4b120240a49e019d399066 Mon Sep 17 00:00:00 2001 From: Rudolf Cornelissen Date: Tue, 29 Nov 2005 11:56:55 +0000 Subject: [PATCH] finalized docs for release. git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@15212 a95241bf-73f2-0310-859d-f6bbb57e9c96 --- .../drivers/graphics/matrox/README.html | 31 +++++++++++++------ .../drivers/graphics/matrox/UPDATE.html | 2 +- 2 files changed, 22 insertions(+), 11 deletions(-) diff --git a/src/add-ons/kernel/drivers/graphics/matrox/README.html b/src/add-ons/kernel/drivers/graphics/matrox/README.html index 3497231d33..13eddac5ed 100644 --- a/src/add-ons/kernel/drivers/graphics/matrox/README.html +++ b/src/add-ons/kernel/drivers/graphics/matrox/README.html @@ -39,25 +39,25 @@ You use this software at your own risk! Although I don't expect it to damage you
  • Full BWindowScreen support (used for hardware pageflipping, scrolling/panning and acceleration in applications/games);
  • Full card coldstart support (important if you use such a card as secondary videocard);
  • Sync_on_green support: G400, G450 and G550 apparantly miss the needed board wiring to actually support this fully though; -
  • DPMS support on both heads; +
  • DPMS support on all heads;
  • G200-G550:
  • G400-G550: + Note: You need Dualhead Setup 0.04 (BeBits) for use of Dualhead and/or TVout modes. current MGA driver limitations:

    @@ -74,6 +74,7 @@ BeOS first checks (during boot) if there are 'user-addons' that should be loaded
    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...
    Note: 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...
    +


    actual INSTALLATION, part 1:

    @@ -89,9 +90,12 @@ In order to do this, you need to delete two files (and reboot afterwards). Here'
  • In: home/config/add-ons/kernel/drivers/bin/
    delete: gx00.driver (You *should* find 'mga.driver' there if you already installed the openBeOS driver V0.13 alpha2 or up.) -
  • You can also delete the mgaGx00.log logfile which is generated by Mark's driver in your home 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 Haiku 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.) +
  • You can also delete the mgaGx00.log logfile which is generated by Mark's driver in your home folder. (The logfile called 'mga.(/dev/graphics name).0.log' the new driver generates is located there also. You may delete that if it gets too big: the Haiku driver simply creates a new one from scratch when needed. The same applies for a possibly existing 'mga.(/dev/graphics name).1.log' file, generated by clone accelerants.) If you install a new version of the Haiku MGA driver later on you won't encounter this manual thing again: it's a one-time thing only.
    +
    +Note: If you used the (non-released) 3D capable Matrox driver please remove it, as it may interfere with the Haiku driver. +


    actual INSTALLATION, part 2:
    @@ -149,7 +153,7 @@ This option is disabled by default (preceded by a '#').
  • 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 memory option to set the driver to the correct amount of RAM.
  • hardcursor:
    - The hardcursor capabilities of the MGA cards are limited to one head only. A hardcursor is nessesary though for DirectWindow windowed mode support. + The hardcursor capabilities of the MGA cards are limited to one head only (except for MMS cards). A hardcursor is nessesary though for DirectWindow windowed mode support. -
  • 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 mga.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 mga.accelerant.1.log, and it will also be in your home folder.
    +
  • logmask: (set to disabled 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 mga.(/dev/graphics name).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 mga.(/dev/graphics name).1.log, and it will also be in your home folder.
    Note:
  • greensync: (V0.14 and up)
    Greensync is used to enable an alternate monitor signal synchronisation setup used for some specific monitors outthere. @@ -187,6 +191,13 @@ Greensync is used to enable an alternate monitor signal synchronisation setup us +
  • primary: (set to disabled by default)
    +Primary lets you force a certain card to be used as primary card in your system if you have multiple graphics cards installed: so it will display your desktop. To enable this (hack) feature uncomment this item and fill in the exact name of the card that is to be primary (as exported by the kerneldriver in /dev/graphics/). If you are going to select a card other than the one displaying your system's POST messages at bootup, make sure you also keep the default 'usebios false' setting as otherwise the card(s) aren't coldstarted by the driver.
    +Note please: +
    Notes: @@ -196,6 +207,6 @@ Greensync is used to enable an alternate monitor signal synchronisation setup us

    Rudolf Cornelissen. -

    (Page last updated on November 24, 2005)

    +

    (Page last updated on November 29, 2005)

    diff --git a/src/add-ons/kernel/drivers/graphics/matrox/UPDATE.html b/src/add-ons/kernel/drivers/graphics/matrox/UPDATE.html index cdd449c5ef..5ab6edb43b 100644 --- a/src/add-ons/kernel/drivers/graphics/matrox/UPDATE.html +++ b/src/add-ons/kernel/drivers/graphics/matrox/UPDATE.html @@ -4,7 +4,7 @@

    Changes done for each driverversion:

    -

    head (SVN 0.26, Rudolf)

    +

    mga_driver 0.26 (Rudolf)