diff --git a/src/add-ons/kernel/drivers/graphics/via/README.html b/src/add-ons/kernel/drivers/graphics/via/README.html index a50f6d1a84..08d14b6afa 100644 --- a/src/add-ons/kernel/drivers/graphics/via/README.html +++ b/src/add-ons/kernel/drivers/graphics/via/README.html @@ -2,36 +2,43 @@ - Readme for Haiku skeleton graphics driver + Readme for Haiku VIA unichrome (pro) graphics driver -

Haiku skeleton graphics driver



+

Haiku VIA unichrome (pro) 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):

+

Supported chipsets (as far as is known):


Features:

Known limitations:

Installation:


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 Haiku skeleton 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 VIA unichrome (pro) 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 skel.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 via.settings file...


actual INSTALLATION:

@@ -47,24 +54,24 @@ 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 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.
+Delete the via.accelerant file in home/config/add-ons/accelerants/
+Delete the via.driver file in home/config/add-ons/kernel/drivers/bin/
+Delete the via.settings file in home/config/settings/kernel/drivers/
+Delete the via.driver shortcut in home/config/add-ons/kernel/drivers/dev/graphics/ which pointed to the file via.driver.

You have to reboot in order to apply the original configuration.


Settings:


-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.
+Please read this information carefully *before* installing and using the Haiku VIA unichrome (pro) graphics driver. It might spare you some trouble afterwards..
+

The driver uses a file named via.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.



-skel.settings driver configuration:
+via.settings driver configuration:

  • 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 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.
    +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 via.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 via.accelerant.1.log, and it will also be in your home folder.
    Note:
  • 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). @@ -145,6 +152,6 @@ With the pgm_panel true setting, the driver will fix your panel

    Rudolf Cornelissen. -

    (Page last updated on November 4, 2004)

    +

    (Page last updated on July 17, 2005)

    diff --git a/src/add-ons/kernel/drivers/graphics/via/UPDATE.html b/src/add-ons/kernel/drivers/graphics/via/UPDATE.html index bece1416c8..1a79fe79e9 100644 --- a/src/add-ons/kernel/drivers/graphics/via/UPDATE.html +++ b/src/add-ons/kernel/drivers/graphics/via/UPDATE.html @@ -4,99 +4,24 @@

    Changes done for each driverversion:

    -

    skel_driver 0.00, (Rudolf)

    +

    via_driver (SVN 0.03, Rudolf)

    Still todo:


    -Welcome at the Haiku-OS skeleton graphicsdriver.
    -
    -It contains a lot of non-working programming, almost all of which sits in the 'engine' folder of the accelerant. The main task to make this a working driver for any card outthere, is rewriting the engine. The code there is kept in place because in fact most of the time you only have to replace the actual card-register programming. And it's always handy to have an example of previous working code at hand when you do that: at least, that's my experience.
    -
    -Using this driver as a starting point for development
    -
    -You have to add your cardID and vendorID to both the kerneldriver (driver.c) and the accelerant (general.c). On top of that, you need to make the kerneldriver framebuffer mapping work. Probably the only thing you need to know is the correct area in which the buffer sits: probably the largest one available.
    -
    -Once you have this done in the driver, you should setup a VESA file for the resolution and depth you are going to work in (you will be developing the driver while you already work with it). Use the lowest resolution you can live with, and choose 8-bit colordepth.
    -Now bootup the system in vesa mode or failsafe video mode (Startup option). Select the vesa mode you will be using explicitly for all workspaces in the Screen preferences app.
    -
    -OK, you should be set now. Install the new driver and reboot... You should have a normal Vesa like screen, only you'll find you have the kerneldriver loaded, the accelerant is running, and you can set modes via the Screen prefs panel: although it will only mess-up your screen. (Luckily the app falls-back to the old mode if you don't confirm the new mode ;-).
    -
    -If your CPU supports MTRR, the kerneldriver will have activated that, and if your card is AGP and you have the busmanager installed, the accelerant will have activated that. This means you should already have optimum speed for framebuffer access: working with BeOS should be smoother already than it was before when you where using real Vesa mode (and nothing else).
    -
    -
    -
    -OK, your first task is get to the point I am describing above. Once you have that going, it's time to really start development. Personally, I have a certain list I always run-down. My advice would be to follow it more or less, as the order of doing things has a certain logic to it, making the steps as testable as can be using this development method.
    -
    - -
    -Todo: complete list..

    Rudolf Cornelissen. -

    (Page last updated on November 8, 2004)

    +

    (Page last updated on July 17, 2005)