From: <jrf...@us...> - 2003-12-06 12:02:17
|
#!/bin/sh set -e GROUP=/home/groups/d/dr/dri BACKUP=$GROUP/backups/wiki SUBJECT='Wiki Update' FROM=jrf...@us... TO=dri...@li... DATE=`date +%Y%m%d` tar -cjf $BACKUP/dri_wiki-$DATE.tar.bz2 \ -C $GROUP \ --exclude wiki/cache \ --exclude 'wiki/*.log' \ --exclude 'wiki/tags' \ cgi-bin/moin_config.py \ wiki CURRENT=$BACKUP/dri_wiki-current.tar.bz2 if [ -e $CURRENT ] then TMPDIR=`mktemp -d /tmp/wiki.XXXXXX` tar -xjf $CURRENT -C $TMPDIR wiki/text DIFF=$BACKUP/dri_wiki-$DATE.diff if ! diff -urN $TMPDIR/wiki/text $GROUP/wiki/text > $DIFF then ( echo "From: $FROM" echo "To: $TO" echo "Subject: $SUBJECT" echo "Content-Type: text/plain; charset=iso-8859-1" echo "Content-Transfer-Encoding: quoted-printable" echo "" cat $0 ) | /usr/sbin/sendmail -f "$FROM" $TO $FROM fi rm -rf $TMPDIR fi ln -sf dri_wiki-$DATE.tar.bz2 $CURRENT |
From: <jrf...@us...> - 2003-12-06 12:21:47
|
diff -urN /tmp/wiki.GjyAGq/wiki/text/NeverWinterNights /home/groups/d/dr/dri/wiki/text/NeverWinterNights --- /tmp/wiki.GjyAGq/wiki/text/NeverWinterNights 2003-10-01 11:05:00.000000000 -0700 +++ /home/groups/d/dr/dri/wiki/text/NeverWinterNights 2003-12-05 07:07:38.000000000 -0800 @@ -38,5 +38,19 @@ -- RolandScheidegger on dri-users. + +== Bad lightening == +(maybe this is not the correct place for such a hint, but as there already was a NeverWinterNights section...) + +'''Problem:''' + +Some part of the scene is not lightened correctly (it is flickering). + +'''Solution:''' + +Seems that this is a problem with TCL. +Just set R200_NO_TCL=1 then it should work fine (but with no TCL of course) (this disables TCL for the game, it has nothing to do with the drivers) + +See this [http://pgshopping.com/mdkxp/en/artcls/nwnfaq.php#path NeverWinter Nights for linux FAQ] ---- CategoryTroubleshooting diff -urN /tmp/wiki.GjyAGq/wiki/text/S3Savage /home/groups/d/dr/dri/wiki/text/S3Savage --- /tmp/wiki.GjyAGq/wiki/text/S3Savage 2003-09-23 10:25:27.000000000 -0700 +++ /home/groups/d/dr/dri/wiki/text/S3Savage 2003-12-05 12:49:02.000000000 -0800 @@ -19,6 +19,8 @@ ''savage_dri.c'' is still needing several functions. i've been basically copy & pasting from the other drivers (especially Radeon, which is one of the most recent) to fill in the void. +FelixKuehling has started porting the S3/VIA driver to Mesa 5.x. His work is available on the savage-2_0_0 branch in cvs. It is not yet working for 4.3 and above. + ==== How can I help? ==== Making the DDX DRI-aware doesn't require a very deep knowledge is a matter of diff -urN /tmp/wiki.GjyAGq/wiki/text/Trident /home/groups/d/dr/dri/wiki/text/Trident --- /tmp/wiki.GjyAGq/wiki/text/Trident 2003-11-09 14:32:57.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/Trident 2003-12-05 12:34:59.000000000 -0800 @@ -8,13 +8,12 @@ == Specifications == -ToDo +Complete specs (2D, 3D, Overlay and MC/IDCT, capture, and dualhead) for the Trident CyberBLADE i1 (VIA Apollo PLE133 Chipset VT8601A North Bridge) http://www.viavpsd.com/product/Download.jsp?motherboardId=21 == Resources == Trident Microsystems, Inc: Videographics: http://www.tridentmicro.com/videographics/index.asp -Trident CyberBLADE i1 (VIA Apollo PLE133 Chipset VT8601A North Bridge) http://www.viavpsd.com/product/Download.jsp?motherboardId=21 ---- CategoryHardwareVendor |
From: <jrf...@us...> - 2003-12-09 12:02:12
|
diff -urN /tmp/wiki.OC0j49/wiki/text/NeverWinterNights /home/groups/d/dr/dri/wiki/text/NeverWinterNights --- /tmp/wiki.OC0j49/wiki/text/NeverWinterNights 2003-12-05 07:07:38.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/NeverWinterNights 2003-12-08 07:49:01.000000000 -0800 @@ -49,7 +49,7 @@ '''Solution:''' Seems that this is a problem with TCL. -Just set R200_NO_TCL=1 then it should work fine (but with no TCL of course) (this disables TCL for the game, it has nothing to do with the drivers) +Just set R200_NO_TCL=1 (or use the ConfigurationOptions to disable TCL in newer version) then it should work fine (but with no TCL of course) See this [http://pgshopping.com/mdkxp/en/artcls/nwnfaq.php#path NeverWinter Nights for linux FAQ] ---- |
From: <jrf...@us...> - 2003-12-11 12:02:18
|
diff -urN /tmp/wiki.Cok2qS/wiki/text/LocalSpellingWords /home/groups/d/dr/dri/wiki/text/LocalSpellingWords --- /tmp/wiki.Cok2qS/wiki/text/LocalSpellingWords 2003-09-22 07:10:25.000000000 -0700 +++ /home/groups/d/dr/dri/wiki/text/LocalSpellingWords 2003-12-11 02:56:28.000000000 -0800 @@ -85,3 +85,5 @@ At Client In Lcore Lib Open Plans The Xserver access apply are at be build call client commands different don for fork given have in is it linked list locking low making manner mesa must name normal of on only order part priority protocol protocols renders safe software spawn that the this time to unable use version way working writing Accesses always and as can directly hardware internal maybe or others parts rendering share side similar something target three used with + +Free86 |
From: <jrf...@us...> - 2003-12-14 12:02:23
|
diff -urN /tmp/wiki.Fz9dtJ/wiki/text/BugZilla /home/groups/d/dr/dri/wiki/text/BugZilla --- /tmp/wiki.Fz9dtJ/wiki/text/BugZilla 1969-12-31 16:00:00.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/BugZilla 2003-12-13 10:51:08.000000000 -0800 @@ -0,0 +1,5 @@ +BugZilla is a commonly used bug report management system. + +Bugs entered at http://bugs.xfree86.org will typically be forwarded to the dri-devel mailing list (see MailingLists) if they are related to 3D specific questions of the XFree86 system. + +There is further the BugZilla database at http://sourceforge.net/tracker/index.php, but even if this database is existing, it is already somewhat out of duty for some time. diff -urN /tmp/wiki.Fz9dtJ/wiki/text/Development /home/groups/d/dr/dri/wiki/text/Development --- /tmp/wiki.Fz9dtJ/wiki/text/Development 2003-10-13 14:39:06.000000000 -0700 +++ /home/groups/d/dr/dri/wiki/text/Development 2003-12-13 10:52:04.000000000 -0800 @@ -11,6 +11,7 @@ Community information: * MailingLists + * BugZilla [http://bugs.xfree86.org Bugzilla Bug Reporting System at XFree86.org] * IRCMeetings * CurrentDevelopers @@ -23,5 +24,6 @@ Special topics: * [http://xfree86.linuxwiki.org/XFree86_205_2e0 Plans For XFree86 5.0] + * [http://www.xfree86.org/releaseplans.html Status of current XFree86 release] * DriWithoutX: DRI without an X server diff -urN /tmp/wiki.Fz9dtJ/wiki/text/MailingLists /home/groups/d/dr/dri/wiki/text/MailingLists --- /tmp/wiki.Fz9dtJ/wiki/text/MailingLists 2003-11-26 21:06:22.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/MailingLists 2003-12-13 10:44:04.000000000 -0800 @@ -1,6 +1,6 @@ == Mailing Lists == -If you need more help getting DRI to work on your Linux system then your best bet is to check out the DRI mailing lists: +If you need more help getting DRI to work on your Linux system then your best bet is to check out the DRI mailing lists or BugZilla: [[BR]] [[BR]] diff -urN /tmp/wiki.Fz9dtJ/wiki/text/SiS6326 /home/groups/d/dr/dri/wiki/text/SiS6326 --- /tmp/wiki.Fz9dtJ/wiki/text/SiS6326 2003-11-19 16:33:52.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/SiS6326 2003-12-13 09:09:06.000000000 -0800 @@ -6,7 +6,11 @@ A driver for the SiS 6326 series is currently in development by EricAnholt. Notable differences from the SiS300 series are that these cards have a single texture unit and a 16-bit Z buffer. A UtahGLX driver for these cards is available. == Specifications == -No documentation is publicly available for this series of card. + SiS530 datasheet (using for SiS53fb driver) + * [http://softpixel.com/~cwright/papers/tech/0530DS10.PDF] + + 6326 SiS datasheet (chipset) exe (self extracting) + * [http://softpixel.com/~cwright/papers/tech/6326ds10.exe] == Resources == * [http://www.sis.com/ SiS homepage] diff -urN /tmp/wiki.Fz9dtJ/wiki/text/TestingAndDebugging /home/groups/d/dr/dri/wiki/text/TestingAndDebugging --- /tmp/wiki.Fz9dtJ/wiki/text/TestingAndDebugging 2003-11-19 07:23:37.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/TestingAndDebugging 2003-12-13 06:30:57.000000000 -0800 @@ -73,7 +73,7 @@ == How should I report bugs? == -Please submit bugs to the [mailto:dri...@li... dri-devel mailing list]. +Please submit bugs to the [mailto:dri...@li... dri-devel mailing list]. Please subscribe to that list first, details can be found at MailingLists. It's best if you can create a small example that shows what you think is the problem. |
From: <jrf...@us...> - 2003-12-24 12:02:27
|
diff -urN /tmp/wiki.0vbqaI/wiki/text/No2048Limit /home/groups/d/dr/dri/wiki/text/No2048Limit --- /tmp/wiki.0vbqaI/wiki/text/No2048Limit 2003-11-26 21:45:00.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/No2048Limit 2003-12-23 09:50:08.000000000 -0800 @@ -1,6 +1,6 @@ == No2048Limit == -Device option in MergedFB patches as of 10/24/2003 which allows you to bypass the builtin DRI screen limit of 2048x2048 pixels. +Device option in DRI CVS as of 10/24/2003 which allows you to bypass the builtin DRI screen limit of 2048x2048 pixels. A more in-depth discussion of this can be found here: |
From: <jrf...@us...> - 2003-12-31 12:02:20
|
diff -urN /tmp/wiki.K7yQHX/wiki/text/AlanCox /home/groups/d/dr/dri/wiki/text/AlanCox --- /tmp/wiki.K7yQHX/wiki/text/AlanCox 2003-11-07 02:47:56.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/AlanCox 2003-12-30 17:58:24.000000000 -0800 @@ -1,15 +1,10 @@ == Your Name == - Email:: ... + Email:: alan at redhat dot com - Homepage:: ... - - Interests:: - * ... - * ... + Homepage:: .http://www.linux.org.uk/diary ---- CategoryHomepage -<big> '''Been default for a while''' diff -urN /tmp/wiki.K7yQHX/wiki/text/NoAccel /home/groups/d/dr/dri/wiki/text/NoAccel --- /tmp/wiki.K7yQHX/wiki/text/NoAccel 1969-12-31 16:00:00.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/NoAccel 2003-12-30 18:10:46.000000000 -0800 @@ -0,0 +1,9 @@ +== NoAccel == + +An option understood by most video drivers to disable 2D acceleration. Normally used for debugging or in problem situations. Enabled by +specifying Option "NoAccel" in the Driver section of the configuration file. + +=== Resources === + +---- +CategoryGlossary diff -urN /tmp/wiki.K7yQHX/wiki/text/VIACLE266 /home/groups/d/dr/dri/wiki/text/VIACLE266 --- /tmp/wiki.K7yQHX/wiki/text/VIACLE266 2003-10-01 11:39:39.000000000 -0700 +++ /home/groups/d/dr/dri/wiki/text/VIACLE266 2003-12-30 18:09:15.000000000 -0800 @@ -2,33 +2,38 @@ == Status == -VIA has released a DRI driver for XFree86 4.2.0 (Mesa 3.4). AlanCox has been porting it to Mesa 3.5+: +The current pending submit 2D driver and the cleaned up kernel module now work with both the 4.2 DRI from VIA and indeed +all the components are interchangable which helps debugging. - I promised folks I'd get around to putting up the XFree 4.3.0 port of - the DRI stuff (or what works so far). Don't get too excited as it works - if - - 1. 2D accel is off, - - 2. The 3D window is on the top - - 3. It feels like it - - 4. You run glxgears and not much else. - - The tar ball of the via gl directory can be found at. - http://www.linux.org.uk/~alan/via-gl.tar.gz and is hopefully useful for - building a proper via branch in CVS. +Latest status: 31/12/03 - -- AlanCox + * Fixed all the problems with gcc 3.2 and optimisation that works (volatile is your friend) + + * Got the fallbacks working without segfaults + + * Still requires the window is top and that it runs "NoAccel" + + * Textures don't always get loaded, although render setup seems ok (if I hand poke in some data bits they get rendered) + + * Tuxracer sort of mostly appears but is using far too many fallbacks and has a brown colour + * Sproingies shows the fallbacks especially have some depth buffer problems, hopefully we can kill them off anyway -The current CLE266 code is available in CVS on the cle266-0-0-1 branch. + * Glxgears... works! + + * Some hangs with AGP modules loaded, fine without (driver supports pure PCI mode too) + + -- AlanCox + +The older CLE266 code is available in CVS on the cle266-0-0-1 branch. (new stuff needs submitting) == Specifications == Not available. +The basics can be deduced from the driver _lite source from VIA. Its a fairly generic "queue up the vertices and fire" type chipset and +the most noticable thing about it appears to be the lack of hardware clipping. When its not doing fallbacks performance seems comparable to the onboard intel stuff but its not radeon grade. + == Resources == * [http://www.via.com.tw/en/apollo/chipsetindex.jsp Product homepage] |
From: <jrf...@us...> - 2004-01-02 12:02:18
|
diff -urN /tmp/wiki.w9UMwo/wiki/text/CvsBranches /home/groups/d/dr/dri/wiki/text/CvsBranches --- /tmp/wiki.w9UMwo/wiki/text/CvsBranches 2003-11-08 12:34:14.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/CvsBranches 2004-01-01 16:07:49.000000000 -0800 @@ -20,7 +20,7 @@ cle266-0-0-1-branch:: This is the branch for integration of the VIA CLE266 driver. - i865-agp-0-0-1-branch:: This is the branch for i865 driver development. + i865-agp-0-1-branch:: This is the branch for i865 driver development. == Old Branches == |
From: <jrf...@us...> - 2004-01-03 12:02:17
|
diff -urN /tmp/wiki.mIIOMe/wiki/text/Documentation /home/groups/d/dr/dri/wiki/text/Documentation --- /tmp/wiki.mIIOMe/wiki/text/Documentation 2003-12-16 04:04:06.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/Documentation 2004-01-02 19:25:42.000000000 -0800 @@ -1,89 +1,91 @@ +] = Documentation = - + == End-User Documentation == - + * [http://dri.sourceforge.net/doc/DRIbeginner.html DRI Beginner's Guide] - + A short, step-by-step guide on how to setup the DRI. Read this guide to get started, then refer to the user guide for more information. - + * [http://dri.sourceforge.net/doc/DRIuserguide.html DRI User Guide] - + This guide explains how to use the DRI and troubleshoot common problems. Please read this document before reporting problems on the DRI mailing lists. There is also a [http://www.meding.net/DRIuserguide-de.htm user guide in german] . - + * [http://dri.sourceforge.net/doc/DRIcompile.html DRI Compilation Guide] - + This guide explains how to download, compile and install the XFree86 X server with DRI 3D acceleration. Also available in [http://www.meding.net/DRIcompile-de.htm german] . - + * DriTroubleshooting - + This page covers the most common issues with configuring the DRI for Linux and FreeBSD. - + * ConfigurationInfrastructure - + This page describes the configuration file format and contains links to a configuration GUI. - + * [http://gatos.sf.net/dri-debug.php DRI Debugging Guide] - + This guide explains how to debug a DRI installation that is not working. Thanks to Vladimir Dergachev and the LiViD folks for putting it together. - + * [http://dri.sourceforge.net/doc/GlideVoodoo5.txt Compiling Glide3 for the Voodoo 5] - + Instructions for compiling Glide3 for the Voodoo5 for DRI. - + * [http://dri.sourceforge.net/doc/building.html Building the DRI] - + Instructions for building the DRI on your own machine. - + == General Developer Documentation == - + * [http://dri.sourceforge.net/doc/DRIintro.html Introduction to the Direct Rendering Infrastructure] - + This document was written for a tutorial session at LinuxWorld 2000 (San Jose) and explains the DRI at a high level. - + * Development - + This page collects various information related to development of the DRI. - + * CvsBranches - + This page lists the active branches of DRI CVS. - + * CvsPolicy - + This document explains the rules for DRI development and how CVS branches are to be used. - + * [http://dri.sourceforge.net/doc/vendor_relationships_paper.html Managing Graphics Hardware Vendor Relationships in the Linux Developer Community] - + A paper presented at the Linux World Conference and Expo in San Jose, CA on March 4, 1999. This paper offers guidelines to anyone who is responsible for establishing or maintaining business relationships. Although the paper is written to describe a specific type of business relationship, it can be applicable to many similar situations. - + == High-Level Design Documents and Diagrams == - + * [http://dri.sourceforge.net/doc/dri_data_flow.html Data Flow Diagram - with explanation] - + * [http://dri.sourceforge.net/doc/dri_control_flow.html Control Flow Diagram - with explanation] - + * [http://dri.sourceforge.net/doc/images/data_flow.jpg Data Flow Diagram] - + * [http://dri.sourceforge.net/doc/images/control_flow.jpg Control Flow Diagram] - + * [http://dri.sourceforge.net/doc/images/control_flow_poster.jpg Control Flow Diagram (Poster Size)] - + * [http://dri.sourceforge.net/doc/design_high_level.html A Multipipe Direct Rendering Architecture for 3D, High-Level Design Document] - + == Low-Level Design Documents == - + * [http://dri.sourceforge.net/doc/design_low_level.html Direct Rendering Infrastructure, Low Level Design Document] - + * [http://dri.sourceforge.net/doc/drm_low_level.html The Direct Rendering Manager, Kernel Support for the Direct Rendering Infrastructure] - + * [http://dri.sourceforge.net/doc/hardware_locking_low_level.html Hardware Locking for the Direct Rendering Infrastructure] - + * [http://dri.sourceforge.net/doc/security_low_level.html A Security Analysis of the Direct Rendering Infrastructure] - + * [http://dri.sourceforge.net/doc/dri_extensions_low_level.txt DRI Extensions for supporting the Direct Rendering Protocol Specification] - + == Other Documents == - + * [http://homepage.hispeed.ch/rscheidegger/atilinux/ati_linux_comp.html Radeon 9000 driver comparison - from R.Scheidegger] - + * [http://www.tomshardware.com Tom's Hardware - drives stories about any grafics acellerator any now and then, including the Linux OS.] +] diff -urN /tmp/wiki.mIIOMe/wiki/text/Download /home/groups/d/dr/dri/wiki/text/Download --- /tmp/wiki.mIIOMe/wiki/text/Download 2003-11-03 04:43:06.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/Download 2004-01-02 19:58:12.000000000 -0800 @@ -1,32 +1,33 @@ '''Contents''' [[TableOfContents]] - + = Source = - + == CVS == - + [[Include(CvsRepository)]] - + == CVSup == - + [[Include(CVSup)]] - + == Kernel Modules == - + You can download the Linux kernel modules for XFree86 4.2.x at [http://www.xfree86.org/~alanh]. - + Kernel modules for subsequent versions of XFree86 can be found in the XFree86 source tree in the directory `xc/programs/Xserver/hw/xfree86/os-support/linux/drm` - + = Binaries = - + == Snapshots == - + Nightly snapshots of the DRI drivers are available from [http://dri.sourceforge.net/snapshots/] - + == Debian packages == - + See http://dri.sourceforge.net/snapshots/README.Debian - -Notice that if you install dri deb's and use synaptics driver you may want to symlink synaptics_drv.o from /usr/!X11R6/lib/modules/input/ to /usr/!X11R6/lib/modules-dri-trunk/drivers/ or it won't be found from X. + +Notice that if you install dri deb's and use synaptics driver you may want to symlink synaptics_drv.o from /usr/!X11R6/lib/modules/input/ to /usr/!X11R6/lib/modules-dri-trunk/drivers/ or it won't be found from X. +X. diff -urN /tmp/wiki.mIIOMe/wiki/text/DriTroubleshooting /home/groups/d/dr/dri/wiki/text/DriTroubleshooting --- /tmp/wiki.mIIOMe/wiki/text/DriTroubleshooting 2003-11-21 15:01:09.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/DriTroubleshooting 2004-01-02 16:19:49.000000000 -0800 @@ -145,6 +145,10 @@ If you are using a radeon and it complains about the module versions and maybe fails on an assertion, you need to update your DRM as in the instructions above. -If you've made it this far, glxinfo should be printing {{{direct rendering: Yes}}} and direct rendering for native GL programs should be working. Make sure that you are running at reasonable settings for your card, and maybe adjust your expectations of speed. +If you've made it this far, glxinfo should be printing {{{direct rendering: Yes}}} and direct rendering for native GL programs should be working. Make sure that you are running at reasonable settings for your card, and maybe adjust your expectations of +speed. + + +If you are experiencing trouble using GL with any program, maybe setting more [http://dri.sourceforge.net/doc/dri_driver_features.phtml environment variables] may help you. FreeBSD: Linux compatibility has its own set of issues. To debug linux DRI compatibility (i.e. quake3/UT), use {{{/compat/linux/usr/X11R6/bin/glxinfo}}} with {{{LIBGL_DEBUG=verbose}}} set. You should be using -current as of April 25, 2003 or -stable as of May 2nd, 2003. Your linux_dri version should exactly match the X you have installed. If not you'll probably get segfaults. If your XFree86 segfaults, make sure you don't have the linux_glx port installed. If you get coredumps on your system with SSE support (Pentium 3 and up, Athlon XP and up), you may need to set the environment variable MESA_FORCE_SSE to 1 due to what appears to be a bug with our linux compat's signal handling. diff -urN /tmp/wiki.mIIOMe/wiki/text/chipset /home/groups/d/dr/dri/wiki/text/chipset --- /tmp/wiki.mIIOMe/wiki/text/chipset 2003-09-22 07:10:25.000000000 -0700 +++ /home/groups/d/dr/dri/wiki/text/chipset 2004-01-02 19:27:41.000000000 -0800 @@ -1,5 +1,5 @@ == Chipset == - + High density electronic circuits are often called 'chips' or 'microchips' because they're laid out on a small square of silicon or another thin, flat substrate. That's what's embedded inside the plastic/ceramic squares inside @@ -14,6 +14,6 @@ the chipset people will be asking about (such as '440BX' or 'VIA MVP3'.) These days, the 'chipset' may well be integrated into a single package, but the historical usage persists. - + ---- CategoryGlossary |
From: <jrf...@us...> - 2004-01-04 12:02:17
|
diff -urN /tmp/wiki.It191H/wiki/text/ConfigurationForDevelopers /home/groups/d/dr/dri/wiki/text/ConfigurationForDevelopers --- /tmp/wiki.It191H/wiki/text/ConfigurationForDevelopers 1969-12-31 16:00:00.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/ConfigurationForDevelopers 2004-01-03 07:17:35.000000000 -0800 @@ -0,0 +1,48 @@ += How to make a driver configurable = + +ToDo + += How to add a new configuration option = + +Steps: + + 1. Define the new option + 2. Add the new option to common/xmlpool.h (optional) + 3. Add the new option to __driConfigOptions + 4. Query the option in a convenient place + +== 1. Define the new option == + +Configuration options are described to the driver and external configuration tools in XML. A set of macros in src/mesa/drivers/dri/common/xmlpool.h helps building such descriptions. + +An option description always starts with {{{DRI_CONF_OPT_BEGIN}}} or {{{DRI_CONF_OPT_BEGIN_V}}} depending on whether you intend to limit the valid range of option values. These macros have 3 or 4 parameters respecitively: ''name'', ''type'', ''default value'' and optionally ''valid range''. + +An option description ends with {{{DRI_CONF_OPT_END}}}. Inbetween you can place verbal descriptions of your options in any number of languages. In the simplest case a description looks like this: {{{DRI_CONF_DESC(lang,"text")}}}. + +'''Note:''' Descriptions must be UTF-8 encoded. + +If you are describing enum type options then you start a description with {{{DRI_CONF_DESC_BEGIN(lang,"text")}}} and end it with {{{DRI_CONF_DESC_END}}}. Inbetween you can place descriptions of different values of the enum option like {{{DRI_CONF_ENUM(value,"text")}}}. + +For enum options it is recommended that you also define macros to give option values symbolic names to be used in the driver. + +== 2. Add the new option to common/xmlpool.h (optional) == + +It is recommended that new options that are likely to be used by more than one driver are added to the common pool of configuration options in src/mesa/drivers/dri/common/xmlpool.h. This makes maintainance easier and increases the chances of the option description being translated to more languages. + +You add an option by defining a macro that expands to the entire option description as outlined in the previous section. You may choose to make the default value a parameter of this macro so that the driver can choose an apropriate default value. For some options it may also make sense to make the valid range of values a parameter. + +== 3. Add the new option to __driConfigOptions == + +In order to inform the driver and external configuration tools about the new option it has to be added to the XML document that advertises the driver's configuration options. It is stored in the global variable {{{__driConfigOptions}}} which is usually found in ''driver''_screen.c or ''driver''_xmesa.c. + +If you added the option to the common pool of options then you just use the macro defined there. Otherwise you fill in the entire option description here. Related options are grouped in sections in {{{__driConfigOptions}}}. Either choose an apropriate section or add a new one if the new options doesn't fit in an existing one. + +== 4. Query the option in a convenient place == + +Now you can query the option value. This must happen after {{{driParseOptionInfo}}} and {{{driParseConfigFiles}}} have been called. This means that you can't query an option before context creation. There are three functions {{{driQueryOption[bif]}}} for querying options for boolean, integer and floating point options respectively. Enum options are queried like integer options. + +The query functions take two arguments, a ''pointer to the option cache'' in the driver's context record and the ''name'' of the option to be queried as a string. If you need the option value very frequently then it is best to query the option once during context creation and store its value in the driver's context record. + +If you try to query an option that is not available or has a different type then an assertion fails. Therefore common code that is linked to different drivers should check if an option is really available first. This is done with driCheckOption. It takes three arguments, a ''pointer to the option cache'', the ''option name'' and the ''type''. It returns a boolean indicating if an option with matching name and type is available. + +-- FelixKuehling diff -urN /tmp/wiki.It191H/wiki/text/ConfigurationInfrastructure /home/groups/d/dr/dri/wiki/text/ConfigurationInfrastructure --- /tmp/wiki.It191H/wiki/text/ConfigurationInfrastructure 2003-11-12 02:46:11.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/ConfigurationInfrastructure 2004-01-03 06:57:51.000000000 -0800 @@ -4,7 +4,7 @@ Since 9th October 2003 the new configuration infrastructure is part of the main trunk of the DRI CVS repository. It introduces a consistent mechanism for configuring all DRI drivers using a XML-based configuration file. Further it provides an interface for configuration GUIs to find out about the ConfigurationOptions of installed drivers. Option descriptions are available in multiple languages, german and english so far. The first GUI configuration tool that uses the new infrastructure is DriConf. -DriConf is by far the easiest and most user-friendly way to edit the configuration. On the page ConfigurationOptions you find more detailed descriptions of common configuration options. If you prefer to edit the configuration file with a text editor then read on. For those interested in the technical details there is a [http://dri.freedesktop.org/~fxkuehl/driconf/dri_config_design_rev4.html design document]. +DriConf is by far the easiest and most user-friendly way to edit the configuration. On the page ConfigurationOptions you find more detailed descriptions of common configuration options. If you prefer to edit the configuration file with a text editor then read on. ConfigurationForDevelopers describes how to make drivers configurable and how to add new options to drivers. For those interested in the technical details there is a [http://dri.freedesktop.org/~fxkuehl/driconf/dri_config_design_rev4.html design document]. == System wide and per-user configuration files == |
From: <jrf...@us...> - 2004-01-05 12:02:14
|
diff -urN /tmp/wiki.7Yihie/wiki/text/ConfigurationForDevelopers /home/groups/d/dr/dri/wiki/text/ConfigurationForDevelopers --- /tmp/wiki.7Yihie/wiki/text/ConfigurationForDevelopers 2004-01-03 07:17:35.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/ConfigurationForDevelopers 2004-01-04 09:18:11.000000000 -0800 @@ -37,6 +37,8 @@ If you added the option to the common pool of options then you just use the macro defined there. Otherwise you fill in the entire option description here. Related options are grouped in sections in {{{__driConfigOptions}}}. Either choose an apropriate section or add a new one if the new options doesn't fit in an existing one. +Finally, don't forget to increment the value of {{{__driNConfigOptions}}} after adding a new option. If you do, the driver will output an error message that reminds you. + == 4. Query the option in a convenient place == Now you can query the option value. This must happen after {{{driParseOptionInfo}}} and {{{driParseConfigFiles}}} have been called. This means that you can't query an option before context creation. There are three functions {{{driQueryOption[bif]}}} for querying options for boolean, integer and floating point options respectively. Enum options are queried like integer options. diff -urN /tmp/wiki.7Yihie/wiki/text/Development /home/groups/d/dr/dri/wiki/text/Development --- /tmp/wiki.7Yihie/wiki/text/Development 2003-12-13 10:52:04.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/Development 2004-01-04 14:12:03.000000000 -0800 @@ -14,6 +14,7 @@ * BugZilla [http://bugs.xfree86.org Bugzilla Bug Reporting System at XFree86.org] * IRCMeetings * CurrentDevelopers + * [http://sourceforge.net/projects/dri/ DRI Project Homepage at Sourceforge] Policy issues: * BinaryCompatability: binary compatability policy diff -urN /tmp/wiki.7Yihie/wiki/text/DriConf /home/groups/d/dr/dri/wiki/text/DriConf --- /tmp/wiki.7Yihie/wiki/text/DriConf 2003-11-15 01:32:14.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/DriConf 2004-01-04 19:11:46.000000000 -0800 @@ -46,18 +46,22 @@ http://dri.freedesktop.org/~fxkuehl/driconf/driconf.png -''Version 0.2.0 (gtk-2)'' +''Version 0.2.1 (gtk-2)'' == Download == - * [http://dri.freedesktop.org/~fxkuehl/driconf/driconf-0.1.1.tar.gz driconf-0.1.1.tar.gz] (gtk-1.2) - * [http://dri.freedesktop.org/~fxkuehl/driconf/driconf-0.2.1.tar.gz driconf-0.2.1.tar.gz] (gtk-2) + * [http://dri.freedesktop.org/~fxkuehl/driconf/driconf-0.1.2.tar.gz driconf-0.1.2.tar.gz] (gtk-1.2) + * [http://dri.freedesktop.org/~fxkuehl/driconf/driconf-0.2.2.tar.gz driconf-0.2.2.tar.gz] (gtk-2) * [http://dri.freedesktop.org/~fxkuehl/driconf Older releases] == History == === Gtk-2 Versions === +==== driconf-0.2.2: Mon Jan 5 03:51:35 CET 2004 ==== + + * Fixed a problem with floating point options that specify a list of valid values, like the new def_max_anisotropy. + ==== driconf-0.2.1: Sat Nov 15 10:04:37 CET 2003 ==== * Select the first writable application configuration on startup with the nice side effect that the window doesn't grow later. @@ -74,6 +78,10 @@ === Gtk-1.2 Versions === +==== driconf-0.1.2: Mon Jan 5 03:56:51 CET 2004 ==== + + * Fixed a problem with floating point options that specify a list of valid values, like the new def_max_anisotropy. + ==== driconf-0.1.1: Sat Nov 15 10:08:13 CET 2003 ==== * Select the first writable application configuration on startup with the nice side effect that the window doesn't grow later. diff -urN /tmp/wiki.7Yihie/wiki/text/SiS6326 /home/groups/d/dr/dri/wiki/text/SiS6326 --- /tmp/wiki.7Yihie/wiki/text/SiS6326 2003-12-13 09:09:06.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/SiS6326 2004-01-04 10:06:00.000000000 -0800 @@ -3,7 +3,12 @@ * SiS 530 == Status == -A driver for the SiS 6326 series is currently in development by EricAnholt. Notable differences from the SiS300 series are that these cards have a single texture unit and a 16-bit Z buffer. A UtahGLX driver for these cards is available. +A driver for the SiS 6326 series is currently in development by EricAnholt. +AlanCox has ported it to run with XFree 4.3.0 and the sis-4.4.0 DRI module. +Basic 3D stuff works with the depth buffer disabled. + +Notable differences from the SiS300 series are that these cards have a single texture unit and a 16-bit Z buffer. +A UtahGLX driver for these cards is available. == Specifications == SiS530 datasheet (using for SiS53fb driver) @@ -15,6 +20,7 @@ == Resources == * [http://www.sis.com/ SiS homepage] * [http://www.winischhofer.net/linuxsisvga.shtml Thomas Winischhofer's SiS graphics chipsets and Linux/XFree86 page] + * [http://www.linux.org.uk/~alan/sis6326.tar.gz Current code drop from Alan Cox] ---- CategoryHardwareChipset diff -urN /tmp/wiki.7Yihie/wiki/text/SiliconMotion /home/groups/d/dr/dri/wiki/text/SiliconMotion --- /tmp/wiki.7Yihie/wiki/text/SiliconMotion 1969-12-31 16:00:00.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/SiliconMotion 2004-01-04 06:53:35.000000000 -0800 @@ -0,0 +1,16 @@ += Silicon Motion, Inc. = + +'''Chipsets''' +[[PageList(^SiliconMotion.+)]] + +== Status == + +todo + +== Resources == + + * [http://www.siliconmotion.com/en/ Silicon Motion, Inc. homepage] + * [http://www.paceblade.com/ Paceblade: builds devices with these chipsets and has a Linux support site] + +---- +CategoryHardwareVendor diff -urN /tmp/wiki.7Yihie/wiki/text/SiliconMotionSM722 /home/groups/d/dr/dri/wiki/text/SiliconMotionSM722 --- /tmp/wiki.7Yihie/wiki/text/SiliconMotionSM722 1969-12-31 16:00:00.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/SiliconMotionSM722 2004-01-04 06:56:13.000000000 -0800 @@ -0,0 +1,27 @@ += SiliconMotion SM722 = +sometimes named SMI722 or LYNX3DM + +Overview from their website: +{{{ + + 128-Bit 2D/3D Graphics Engine + + High Integration with up to 8MB of Internal Memory + + Hardware Accelerated MPEG2/DVD Playback + + Industrial Temperature Available (-40° to +85°) + + Long Term Supply Assurance +}}} + +== Status == + +todo + +== Specifications == + +Complete register level spec.: +[http://www.siliconmotion.com/databooks/SM722_Rev08.pdf] + +== Resources == + +[http://www.siliconmotion.com/en/sm722.htm] + +---- +CategoryHardwareChipset, CategoryHelpWanted diff -urN /tmp/wiki.7Yihie/wiki/text/SiliconMotionSM731 /home/groups/d/dr/dri/wiki/text/SiliconMotionSM731 --- /tmp/wiki.7Yihie/wiki/text/SiliconMotionSM731 1969-12-31 16:00:00.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/SiliconMotionSM731 2004-01-04 06:54:57.000000000 -0800 @@ -0,0 +1,26 @@ += SiliconMotion SM731 = +sometimes named SMI731 or COUGAR3DR + +Overview from their website: +{{{ + + Ultra low-power 3D/2D display controller + + DualMon technology for expanded view on secondary monitor + + QuickRotate feature for instantaneous rotationHardware supported rotation for 90, 180 and 270 + + TabView(TM) for extended desktop view on secondary monitor for docked TabletPC + + Enhanced ReduceOn(TM) power management +}}} +== Status == + +todo + +== Specifications == + +Complete register level spec.: +[http://www.siliconmotion.com/databooks/SM731_Rev_1.5.pdf] + +== Resources == + +[http://www.siliconmotion.com/en/sm731.htm] + +---- +CategoryHardwareChipset, CategoryHelpWanted diff -urN /tmp/wiki.7Yihie/wiki/text/VIACLE266 /home/groups/d/dr/dri/wiki/text/VIACLE266 --- /tmp/wiki.7Yihie/wiki/text/VIACLE266 2003-12-30 18:09:15.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/VIACLE266 2004-01-04 10:12:31.000000000 -0800 @@ -5,23 +5,19 @@ The current pending submit 2D driver and the cleaned up kernel module now work with both the 4.2 DRI from VIA and indeed all the components are interchangable which helps debugging. -Latest status: 31/12/03 +Latest status: 2004-01-02 - * Fixed all the problems with gcc 3.2 and optimisation that works (volatile is your friend) + * 3D now works with 2D accelleration enabled - * Got the fallbacks working without segfaults + * Chromium BSU now runs entirely - * Still requires the window is top and that it runs "NoAccel" + * Window overlapping now works - * Textures don't always get loaded, although render setup seems ok (if I hand poke in some data bits they get rendered) + * Tuxracer works except that the initial screen has a pale brown not a pale blue background - * Tuxracer sort of mostly appears but is using far too many fallbacks and has a brown colour + * Most screensavers run - morph3d and pipes crash - * Sproingies shows the fallbacks especially have some depth buffer problems, hopefully we can kill them off anyway - - * Glxgears... works! - - * Some hangs with AGP modules loaded, fine without (driver supports pure PCI mode too) + * Several screensavers (but not tuxracer) don't render polygons that are clipped -- AlanCox @@ -38,6 +34,7 @@ * [http://www.via.com.tw/en/apollo/chipsetindex.jsp Product homepage] * [http://www.viaarena.com/?PageID=325 Vendor drivers] + * [http://www.linux.org.uk/~alan/via-dri-20040102.tar.gz] ---- CategoryHardwareChipset, CategoryHelpWanted |
From: <jrf...@us...> - 2004-01-06 12:02:19
|
diff -urN /tmp/wiki.Y73BwU/wiki/text/Matrox /home/groups/d/dr/dri/wiki/text/Matrox --- /tmp/wiki.Y73BwU/wiki/text/Matrox 2003-10-01 14:03:56.000000000 -0700 +++ /home/groups/d/dr/dri/wiki/text/Matrox 2004-01-05 15:15:28.000000000 -0800 @@ -24,6 +24,8 @@ == Specifications == +Databooks for the G200 and G400 used to be available through Matrox' developer program, however the program seems to no longer exist. + == Resources == diff -urN /tmp/wiki.Y73BwU/wiki/text/S3Savage /home/groups/d/dr/dri/wiki/text/S3Savage --- /tmp/wiki.Y73BwU/wiki/text/S3Savage 2003-12-05 12:49:02.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/S3Savage 2004-01-05 16:32:17.000000000 -0800 @@ -7,27 +7,18 @@ S3/VIA released the source code to their savage DRI driver for xfree86 4.2.0. It is based on mesa 3.x, and as such needs to be ported to mesa 4.x for 4.3.0 or 5.x for CVS. There is some work going on to port the driver to the new -mesa. The code from S3/VIA is in the savage-1_0_0 branch in DRI CVS. For -information on compiling the source for 4.2.0, see +mesa. For information on compiling the source for 4.2.0, see [http://moh.oxiq.org/acer_aspire1300/index.php?p=xf86 this page]. This driver -seems to only be for prosavage and twister cores. The UtahGLX project has +seems to only be for prosavage and twister (savage4) cores. The UtahGLX project has support for savage 3D/MX/IX for XFree86 3.3.x and 4.x. ==== What's the status of the Savage driver? ==== -At this point work is still being done to make the 2D driver DRI aware. See the [http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/dri/xc/xc/programs/Xserver/hw/xfree86/drivers/savage/?only_with_tag=savage-0-0-1-branch Savage DDX driver on CVS] and the preliminary [http://dri.sourceforge.net/doc/howto/ddx.html DDX chapter of the DRI Driver HOWTO]. - -''savage_dri.c'' is still needing several functions. i've been basically copy & pasting from the other drivers (especially Radeon, which is one of the most recent) to fill in the void. - -FelixKuehling has started porting the S3/VIA driver to Mesa 5.x. His work is available on the savage-2_0_0 branch in cvs. It is not yet working for 4.3 and above. +FelixKuehling has started porting the S3/VIA driver to Mesa 5.x. His work is available on the savage-2-0-0 branch in cvs. The code on the branch now works for most savage4-based chips. There seems to be a problem with 2D accel and 3D on some savage4 chips, some modes don't work correctly, and the driver locks up on VT switches. Work will also begin for supporting the older savage chips (3D/MX/IX/etc.). ==== How can I help? ==== -Making the DDX DRI-aware doesn't require a very deep knowledge is a matter of -mostly copy & pasting from other drivers. Bootstrapping a DRM kernel module is -also easy - see for example the 3dfx one. Both these things could be done by a -newbie, allowing the developers to concentrate on the more demanding Mesa -driver. +There are some problems with VT switches and certain display modes that need investigating. XvMC support also needs some work as it doesn't seem to work at the moment. ---- CategoryHardwareChipset, CategoryHelpWanted |
From: <jrf...@us...> - 2004-01-07 12:02:21
|
diff -urN /tmp/wiki.VwoAJF/wiki/text/ATIRadeon /home/groups/d/dr/dri/wiki/text/ATIRadeon --- /tmp/wiki.VwoAJF/wiki/text/ATIRadeon 2003-11-14 07:42:14.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/ATIRadeon 2004-01-06 04:59:42.000000000 -0800 @@ -77,7 +77,7 @@ The difference between the Rv250 and the Rv280 is that the R9200 has AGP 8x while the Rv250 has AGP 4x. -The 9200SE is a toned down version of the 9200 and has half the memory bandwidth (64 bit verses 128 bit) +The 9200SE is a toned down version of the 9200 and has half the memory bandwidth (64 bit versus 128 bit) and lower clock speed (200 MHz versus 250 MHz). One problem with the 9200SE is that some older XFree86 servers will not @@ -154,6 +154,7 @@ Legend: + * SE = Stripped down version of the chip which has half the memory bandwidth (64 bit versus 128 bit). * VE = Value Edition * LE = Light Edition * SDR = Single Data Rate (RAM) |
From: <jrf...@us...> - 2004-01-08 12:02:18
|
diff -urN /tmp/wiki.y2rWfG/wiki/text/ATIRadeon /home/groups/d/dr/dri/wiki/text/ATIRadeon --- /tmp/wiki.y2rWfG/wiki/text/ATIRadeon 2004-01-06 04:59:42.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/ATIRadeon 2004-01-07 06:37:05.000000000 -0800 @@ -126,7 +126,7 @@ ===== Radeon IGP ===== -The Radeon IGP chipsets to not have discrete video ram. They share system ram much like the Intel i8xx chips, and VIA/S3 ProSavage/Twister chips. There is support for 2D acceleration for the IGP chipsets in CVS. 3D support is available as a [http://bugs.xfree86.org/show_bug.cgi?id=314 patch], but has not yet been integrated into CVS. +The Radeon IGP chipsets to not have discrete video ram. They share system ram much like the Intel i8xx chips, and VIA/S3 ProSavage/Twister chips. There is support for 2D acceleration for the IGP chipsets in CVS. 3D support is available as a [http://bugs.xfree86.org/show_bug.cgi?id=314 patch]. This patch was recently integrated into CVS. ===== All Radeons ===== diff -urN /tmp/wiki.y2rWfG/wiki/text/VIACLE266 /home/groups/d/dr/dri/wiki/text/VIACLE266 --- /tmp/wiki.y2rWfG/wiki/text/VIACLE266 2004-01-04 10:12:31.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/VIACLE266 2004-01-07 07:18:35.000000000 -0800 @@ -35,6 +35,7 @@ * [http://www.via.com.tw/en/apollo/chipsetindex.jsp Product homepage] * [http://www.viaarena.com/?PageID=325 Vendor drivers] * [http://www.linux.org.uk/~alan/via-dri-20040102.tar.gz] + * Patch to make Alan's via-dri compile with XFree86 4.4 CVS (NOTE: It compiles, but doesn't work yet - it's only a start, help welcome!) [http://www.arklinux.org/~bero/via-dri-20040102-XF44.patch] ---- CategoryHardwareChipset, CategoryHelpWanted |
From: <jrf...@us...> - 2004-01-10 12:02:16
|
diff -urN /tmp/wiki.6ikxZ0/wiki/text/AlexDeucher /home/groups/d/dr/dri/wiki/text/AlexDeucher --- /tmp/wiki.6ikxZ0/wiki/text/AlexDeucher 2003-11-24 07:55:40.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/AlexDeucher 2004-01-09 10:04:58.000000000 -0800 @@ -8,7 +8,9 @@ [http://bugs.xfree86.org/show_bug.cgi?id=96 Radeon Power Manangement Support] -[http://www.botchco.com/alex/radeon/Xv Radeon Overlay Projects] +[http://www.botchco.com/alex/radeon/Xv Radeon Overlay (Xv) Projects] + +[http://www.botchco.com/alex/savage/ S3 Savage DRI support] ---- CategoryHomepage diff -urN /tmp/wiki.6ikxZ0/wiki/text/Download /home/groups/d/dr/dri/wiki/text/Download --- /tmp/wiki.6ikxZ0/wiki/text/Download 2004-01-02 19:58:12.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/Download 2004-01-09 18:56:24.000000000 -0800 @@ -30,4 +30,22 @@ See http://dri.sourceforge.net/snapshots/README.Debian Notice that if you install dri deb's and use synaptics driver you may want to symlink synaptics_drv.o from /usr/!X11R6/lib/modules/input/ to /usr/!X11R6/lib/modules-dri-trunk/drivers/ or it won't be found from X. -X. + +=== Debian XFree packages === + +Latest Xfree 4.3 builds can be downloaded, If you are with unstable, with this line in /etc/apt/sources.list (on 10 Jan 2004): + +deb ftp://<your debian mirror>/debian experimental main non-free contrib + +And: + +1) Modify (or create) /etc/apt/preferences this way: + +Package: * +Pin: release a=experimental,s=x11 +Pin-Priority: 995 + +2) Manually selecting (may be a tedious work) with : + +$ apt-get install xserver-xfree86/experimental + diff -urN /tmp/wiki.6ikxZ0/wiki/text/FrontPage /home/groups/d/dr/dri/wiki/text/FrontPage --- /tmp/wiki.6ikxZ0/wiki/text/FrontPage 2003-12-24 16:43:00.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/FrontPage 2004-01-08 09:01:24.000000000 -0800 @@ -20,7 +20,7 @@ * Download * Development * Contributing - * Links + * Links :) == Miscellaneous == diff -urN /tmp/wiki.6ikxZ0/wiki/text/Links /home/groups/d/dr/dri/wiki/text/Links --- /tmp/wiki.6ikxZ0/wiki/text/Links 2003-09-23 10:25:27.000000000 -0700 +++ /home/groups/d/dr/dri/wiki/text/Links 2004-01-09 10:00:05.000000000 -0800 @@ -26,7 +26,7 @@ [http://www.3dfx.com 3DFX] Out of business, but provided Open Source DRI Drivers -[http://www.3dlabs.com 3D Labs] Open Source DRI Drivers +[http://www.3dlabs.com 3D Labs] Open Source (DRI) and proprietary Drivers [http://www.ati.com ATI] Open Source (DRI) and proprietary Drivers diff -urN /tmp/wiki.6ikxZ0/wiki/text/VIACLE266 /home/groups/d/dr/dri/wiki/text/VIACLE266 --- /tmp/wiki.6ikxZ0/wiki/text/VIACLE266 2004-01-07 07:18:35.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/VIACLE266 2004-01-08 07:31:42.000000000 -0800 @@ -35,7 +35,7 @@ * [http://www.via.com.tw/en/apollo/chipsetindex.jsp Product homepage] * [http://www.viaarena.com/?PageID=325 Vendor drivers] * [http://www.linux.org.uk/~alan/via-dri-20040102.tar.gz] - * Patch to make Alan's via-dri compile with XFree86 4.4 CVS (NOTE: It compiles, but doesn't work yet - it's only a start, help welcome!) [http://www.arklinux.org/~bero/via-dri-20040102-XF44.patch] + * Patch to make Alan's via-dri compile and work with XFree86 4.4 CVS: (Note: there are still some rendering bugs and FALLBACK 7 errors, but it works) [http://www.arklinux.org/~bero/via-dri-20040102-XF44.patch] ---- CategoryHardwareChipset, CategoryHelpWanted |
From: <jrf...@us...> - 2004-01-11 12:02:18
|
diff -urN /tmp/wiki.X9dIp9/wiki/text/3dfx /home/groups/d/dr/dri/wiki/text/3dfx --- /tmp/wiki.X9dIp9/wiki/text/3dfx 2003-10-09 22:15:56.000000000 -0700 +++ /home/groups/d/dr/dri/wiki/text/3dfx 2004-01-10 17:21:20.000000000 -0800 @@ -12,6 +12,10 @@ * 3dfx Voodoo Banshee * Velocity 100/200 +Unsupported Cards (2D only in XFree86) + * 3dfx Voodoo2 + * 3dfx Voodoo1 + Important notes: * 3dfx is now defunct. * hardware acceleration is only supported at 16bpp on the Voodoo 3 and the Banshee. @@ -19,6 +23,7 @@ * The driver lacks a current maintainer. * SLI is currently not supported. We are looking for volunteers to complete the SLI work. Note that this is quite difficult to complete. * AGP support in your kernel does not matter to the 3dfx driver, as it doesn't use AGP on Linux/BSD. + * Voodoo1/Voodoo2 use Glide2 and very different interfaces to later cards. While it is not impossible to write DRI modules for Voodoo1/2 the hardware is not designed for windowed 3D == Specifications == diff -urN /tmp/wiki.X9dIp9/wiki/text/Documentation /home/groups/d/dr/dri/wiki/text/Documentation --- /tmp/wiki.X9dIp9/wiki/text/Documentation 2004-01-02 19:25:42.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/Documentation 2004-01-10 18:12:22.000000000 -0800 @@ -87,5 +87,3 @@ * [http://homepage.hispeed.ch/rscheidegger/atilinux/ati_linux_comp.html Radeon 9000 driver comparison - from R.Scheidegger] - * [http://www.tomshardware.com Tom's Hardware - drives stories about any grafics acellerator any now and then, including the Linux OS.] -] diff -urN /tmp/wiki.X9dIp9/wiki/text/SiS6326 /home/groups/d/dr/dri/wiki/text/SiS6326 --- /tmp/wiki.X9dIp9/wiki/text/SiS6326 2004-01-04 10:06:00.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/SiS6326 2004-01-10 17:09:35.000000000 -0800 @@ -5,7 +5,7 @@ == Status == A driver for the SiS 6326 series is currently in development by EricAnholt. AlanCox has ported it to run with XFree 4.3.0 and the sis-4.4.0 DRI module. -Basic 3D stuff works with the depth buffer disabled. +Basic 3D stuff works with some depth and triangle setu p problems, also no textures yet Notable differences from the SiS300 series are that these cards have a single texture unit and a 16-bit Z buffer. A UtahGLX driver for these cards is available. diff -urN /tmp/wiki.X9dIp9/wiki/text/VIACLE266 /home/groups/d/dr/dri/wiki/text/VIACLE266 --- /tmp/wiki.X9dIp9/wiki/text/VIACLE266 2004-01-08 07:31:42.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/VIACLE266 2004-01-10 18:06:16.000000000 -0800 @@ -7,21 +7,19 @@ Latest status: 2004-01-02 - * 3D now works with 2D accelleration enabled - - * Chromium BSU now runs entirely + * 3D now works with 2D acceleration enabled * Window overlapping now works * Tuxracer works except that the initial screen has a pale brown not a pale blue background - * Most screensavers run - morph3d and pipes crash + * Screensavers run - * Several screensavers (but not tuxracer) don't render polygons that are clipped + * Clipping is fixed -- AlanCox -The older CLE266 code is available in CVS on the cle266-0-0-1 branch. (new stuff needs submitting) +The older CLE266 code is available in CVS on the cle266-0-0-1 branch. (new stuff needs submitting but can be found at http://people.redhat.com/alan) == Specifications == @@ -34,8 +32,8 @@ * [http://www.via.com.tw/en/apollo/chipsetindex.jsp Product homepage] * [http://www.viaarena.com/?PageID=325 Vendor drivers] - * [http://www.linux.org.uk/~alan/via-dri-20040102.tar.gz] - * Patch to make Alan's via-dri compile and work with XFree86 4.4 CVS: (Note: there are still some rendering bugs and FALLBACK 7 errors, but it works) [http://www.arklinux.org/~bero/via-dri-20040102-XF44.patch] + * [http://people.redhat.com/alan Alan's Patches] + * Patch to make an older version of Alan's via-dri compile and work with XFree86 4.4 CVS/old Mesa: (Note: there are still some rendering bugs and FALLBACK 7 errors, but it works) [http://www.arklinux.org/~bero/via-dri-20040102-XF44.patch] ---- CategoryHardwareChipset, CategoryHelpWanted diff -urN /tmp/wiki.X9dIp9/wiki/text/nVidia /home/groups/d/dr/dri/wiki/text/nVidia --- /tmp/wiki.X9dIp9/wiki/text/nVidia 2003-09-23 10:25:27.000000000 -0700 +++ /home/groups/d/dr/dri/wiki/text/nVidia 2004-01-10 17:18:15.000000000 -0800 @@ -6,7 +6,8 @@ == Specifications == -Hardware specs are not available to the DRI developers. +Hardware specs are not available to the DRI developers. Some reverse engineering has been done and can be found at RivaTV +[http://rivatv.sourceforge.net/stuff/riva128.txt Riva128] == nVidia nForce AGPGART driver == @@ -14,7 +15,7 @@ == Resources == -UtahGLX has support for nVidia Riva / TNT / GeForce for XFree86 3.3 and 4.0. +UtahGLX also has basic support for nVidia Riva / TNT / GeForce for XFree86 3.3 and 4.0. ---- CategoryHardwareVendor |
From: <jrf...@us...> - 2004-01-12 12:02:18
|
diff -urN /tmp/wiki.qSGP8Y/wiki/text/Documentation /home/groups/d/dr/dri/wiki/text/Documentation --- /tmp/wiki.qSGP8Y/wiki/text/Documentation 2004-01-10 18:12:22.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/Documentation 2004-01-11 06:46:51.000000000 -0800 @@ -1,4 +1,3 @@ -] = Documentation = == End-User Documentation == diff -urN /tmp/wiki.qSGP8Y/wiki/text/SiS6326 /home/groups/d/dr/dri/wiki/text/SiS6326 --- /tmp/wiki.qSGP8Y/wiki/text/SiS6326 2004-01-10 17:09:35.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/SiS6326 2004-01-11 10:13:50.000000000 -0800 @@ -5,7 +5,7 @@ == Status == A driver for the SiS 6326 series is currently in development by EricAnholt. AlanCox has ported it to run with XFree 4.3.0 and the sis-4.4.0 DRI module. -Basic 3D stuff works with some depth and triangle setu p problems, also no textures yet +Basic 3D stuff works with some depth and triangle setup problems, also no textures yet. Notable differences from the SiS300 series are that these cards have a single texture unit and a 16-bit Z buffer. A UtahGLX driver for these cards is available. |
From: <jrf...@us...> - 2004-01-13 12:02:21
|
diff -urN /tmp/wiki.7X0Txe/wiki/text/FelixKuehling /home/groups/d/dr/dri/wiki/text/FelixKuehling --- /tmp/wiki.7X0Txe/wiki/text/FelixKuehling 2003-09-26 01:41:13.000000000 -0700 +++ /home/groups/d/dr/dri/wiki/text/FelixKuehling 2004-01-12 14:37:11.000000000 -0800 @@ -9,7 +9,7 @@ Interests:: * ConfigurationInfrastructure * ATIRadeon - * Savage4 + * S3Savage ---- CategoryHomepage |
From: <jrf...@us...> - 2004-01-14 12:02:21
|
diff -urN /tmp/wiki.0yHFuf/wiki/text/Documentation /home/groups/d/dr/dri/wiki/text/Documentation --- /tmp/wiki.0yHFuf/wiki/text/Documentation 2004-01-11 06:46:51.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/Documentation 2004-01-13 19:45:28.000000000 -0800 @@ -21,6 +21,10 @@ * ConfigurationInfrastructure This page describes the configuration file format and contains links to a configuration GUI. + + * DriverFiles + + This page describes the files that make up the 2D and 3D drivers and DRM for each driver. * [http://gatos.sf.net/dri-debug.php DRI Debugging Guide] diff -urN /tmp/wiki.0yHFuf/wiki/text/Download /home/groups/d/dr/dri/wiki/text/Download --- /tmp/wiki.0yHFuf/wiki/text/Download 2004-01-09 18:56:24.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/Download 2004-01-13 16:01:22.000000000 -0800 @@ -42,7 +42,9 @@ 1) Modify (or create) /etc/apt/preferences this way: Package: * + Pin: release a=experimental,s=x11 + Pin-Priority: 995 2) Manually selecting (may be a tedious work) with : diff -urN /tmp/wiki.0yHFuf/wiki/text/DriverFiles /home/groups/d/dr/dri/wiki/text/DriverFiles --- /tmp/wiki.0yHFuf/wiki/text/DriverFiles 1969-12-31 16:00:00.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/DriverFiles 2004-01-13 20:10:24.000000000 -0800 @@ -0,0 +1,65 @@ +== Driver Files == +This page is dedicated to describing what functions live where and how all the actual files fit together for the 2D driver, the 3D driver, and the DRM. There is some variation between different drivers, but for the most part there is pattern of driver structure. + + +=== 2D Driver === +The 2D driver source is found here: +xc/programs/Xserver/hw/xfree86/drivers + +*_driver.c - This is the guts of the 2D driver. It usually contains the mandatory functions (PreInit() ScreenInit(), VT switching, etc. - see the XFree86 [http://www.xfree86.org/current/DESIGN.html DESIGN] document for more info on required functions) and the mode setting/switching code. + +*_regs.h - Contains the register defines and macros. + +*.h or *_driver.h - usually contains the driver specific info struct and other structs needed by the driver. May also comtain some macro defines and function definitions shared by the various files in the driver. + +*_video.c or *xv.c - Contains the code to set up and use the video overlay (Xv). + +*_hwmc.c - Contains the code to set up and use the iDCT or motion compensation features with the video overlay (XvMC). + +*_accel.c - Contains the 2D acceleration code. + +*_shadow.c - Contains functions to support the shadow framebuffer if the driver supports it. + +*_i2c.c - Contains driver specific code for accessing the i2c bus on the card/chip. It's usually used for DDC2. + +*_dga.c - Contains code to support DGA, an old feature that lets apps write driectly to the framebuffer. It's rarely used nowadays. + +*_cursor.c - Contains code to enable the hardware cursor. + +*_dri.c - Contains server side code to set up the DRI. + +*_sarea.h - Contains defines needed for the SAREA (shared memory area). + + +=== 3D driver === +The 3D driver source is found here: +xc/lib/GL/mesa/src/drv/ + +*_3d_reg.h or *_reg.h - 3D register and macro defines. + +*_tex.[ch] - Contains texture code. + +*_xmesa.c or *_screen.[ch] and *_context.[ch] - These deal with screen and context management. The xmesa name is historical. There used to be a number of callbacks whose names started with XMesa. They were called directly by Mesa. The interface has changed in Mesa 4.0. Now there is an API record that specifies these driver entry points. In some drivers (radeon, r200, r128) these functions are in *_screen.[ch] and *_context.[ch]. + +*_span.[ch] - Access to spans of the frame buffer, used for software rasterization fallbacks. + +*_tris.[ch] - It draws all primitives using some templates in mesa/tnl_dd. All primitives are mapped to the ones supported directly by the hardware. At the highest level whole Mesa vertex buffers are rendered. + +It is not the most efficient way of rendering because all strips and fans are decomposed into individual triangles. So lots of duplicate +vertices are emitted to the hardware. At some point we may implement our own render stage that takes advantages of hardware strips and fans. r128 and mga used to have *_fastpath.[ch] files in Mesa 3 that did just that. So did the savage driver. These were not ported to Mesa 4 in any of these drivers. Maybe it's not such a big performance win in practice. + +*_state.[ch] - manage the 3D state in hardware. + +*_dd.[ch] - Some selection of device driver functions. I don't know why they are collected in this file. Maybe a historical leftover. The radeon drivers don't have it anymore. It's pretty short in other drivers. + +*_ioctl.[ch] - ioctls for use with the DRM. + +*_vb.[ch] - Vertex setup. Determines which components are needed for the current state and generates appropriate hardware vertices from Mesa vertices. For the D3D-like vertex formats there are templates in mesa/tnl_dd. + + +=== DRM === +The linux DRM source is found here: +xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel + +ToDo + diff -urN /tmp/wiki.0yHFuf/wiki/text/S3Savage /home/groups/d/dr/dri/wiki/text/S3Savage --- /tmp/wiki.0yHFuf/wiki/text/S3Savage 2004-01-05 16:32:17.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/S3Savage 2004-01-13 10:18:16.000000000 -0800 @@ -14,11 +14,11 @@ ==== What's the status of the Savage driver? ==== -FelixKuehling has started porting the S3/VIA driver to Mesa 5.x. His work is available on the savage-2-0-0 branch in cvs. The code on the branch now works for most savage4-based chips. There seems to be a problem with 2D accel and 3D on some savage4 chips, some modes don't work correctly, and the driver locks up on VT switches. Work will also begin for supporting the older savage chips (3D/MX/IX/etc.). +FelixKuehling has started porting the S3/VIA driver to Mesa 5.x. AlexDeucher is working on the 2D driver. Their work is available on the savage-2-0-0 branch in cvs. The code on the branch now works for most savage4-based (savage4/prosavage/twister) chips. Work is also beginning for supporting the older savage chips (3D/MX/IX/etc.). ==== How can I help? ==== -There are some problems with VT switches and certain display modes that need investigating. XvMC support also needs some work as it doesn't seem to work at the moment. +There are some problems with VT switches and certain display modes that need investigating. XvMC support also needs some work as it doesn't seem to work at the moment and textures still show some corruption. ---- CategoryHardwareChipset, CategoryHelpWanted diff -urN /tmp/wiki.0yHFuf/wiki/text/VIACLE266 /home/groups/d/dr/dri/wiki/text/VIACLE266 --- /tmp/wiki.0yHFuf/wiki/text/VIACLE266 2004-01-10 18:06:16.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/VIACLE266 2004-01-13 14:00:50.000000000 -0800 @@ -33,7 +33,7 @@ * [http://www.via.com.tw/en/apollo/chipsetindex.jsp Product homepage] * [http://www.viaarena.com/?PageID=325 Vendor drivers] * [http://people.redhat.com/alan Alan's Patches] - * Patch to make an older version of Alan's via-dri compile and work with XFree86 4.4 CVS/old Mesa: (Note: there are still some rendering bugs and FALLBACK 7 errors, but it works) [http://www.arklinux.org/~bero/via-dri-20040102-XF44.patch] + * Patch to make Alan's via-dri compile and work with XFree86 4.4 CVS/old Mesa: (Note: there are still some rendering bugs and FALLBACK 7 errors, but it works) [http://www.arklinux.org/~bero/via-dri-20040102-XF44.patch] ---- CategoryHardwareChipset, CategoryHelpWanted |
From: <jrf...@us...> - 2004-01-15 12:02:14
|
diff -urN /tmp/wiki.D3sMDV/wiki/text/DriTroubleshooting /home/groups/d/dr/dri/wiki/text/DriTroubleshooting --- /tmp/wiki.D3sMDV/wiki/text/DriTroubleshooting 2004-01-02 16:19:49.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/DriTroubleshooting 2004-01-14 06:53:39.000000000 -0800 @@ -152,3 +152,5 @@ If you are experiencing trouble using GL with any program, maybe setting more [http://dri.sourceforge.net/doc/dri_driver_features.phtml environment variables] may help you. FreeBSD: Linux compatibility has its own set of issues. To debug linux DRI compatibility (i.e. quake3/UT), use {{{/compat/linux/usr/X11R6/bin/glxinfo}}} with {{{LIBGL_DEBUG=verbose}}} set. You should be using -current as of April 25, 2003 or -stable as of May 2nd, 2003. Your linux_dri version should exactly match the X you have installed. If not you'll probably get segfaults. If your XFree86 segfaults, make sure you don't have the linux_glx port installed. If you get coredumps on your system with SSE support (Pentium 3 and up, Athlon XP and up), you may need to set the environment variable MESA_FORCE_SSE to 1 due to what appears to be a bug with our linux compat's signal handling. + +On Mandrake 9.2 : big troubles I will try to recover. |
From: <jrf...@us...> - 2004-01-16 12:02:18
|
diff -urN /tmp/wiki.X6qyzm/wiki/text/SiliconMotionSM722 /home/groups/d/dr/dri/wiki/text/SiliconMotionSM722 --- /tmp/wiki.X6qyzm/wiki/text/SiliconMotionSM722 2004-01-04 06:56:13.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/SiliconMotionSM722 2004-01-15 08:35:54.000000000 -0800 @@ -12,7 +12,7 @@ == Status == -todo +ToDo == Specifications == diff -urN /tmp/wiki.X6qyzm/wiki/text/SiliconMotionSM731 /home/groups/d/dr/dri/wiki/text/SiliconMotionSM731 --- /tmp/wiki.X6qyzm/wiki/text/SiliconMotionSM731 2004-01-04 06:54:57.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/SiliconMotionSM731 2004-01-15 08:35:19.000000000 -0800 @@ -11,7 +11,7 @@ }}} == Status == -todo +ToDo == Specifications == |
From: <jrf...@us...> - 2004-01-17 12:02:21
|
diff -urN /tmp/wiki.vfVIpp/wiki/text/S3Savage /home/groups/d/dr/dri/wiki/text/S3Savage --- /tmp/wiki.vfVIpp/wiki/text/S3Savage 2004-01-13 10:18:16.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/S3Savage 2004-01-16 12:31:45.000000000 -0800 @@ -20,5 +20,7 @@ There are some problems with VT switches and certain display modes that need investigating. XvMC support also needs some work as it doesn't seem to work at the moment and textures still show some corruption. +Adding extenstions: Once we get the 3D driver cleaned up there are some extensions that could be added. At a quick glance, based on the 3D registers it looks like MESA_ycbcr_texture could be supported, probably others as well. + ---- CategoryHardwareChipset, CategoryHelpWanted |
From: <jrf...@us...> - 2004-01-20 12:02:21
|
diff -urN /tmp/wiki.uZlbA4/wiki/text/AlexDeucher /home/groups/d/dr/dri/wiki/text/AlexDeucher --- /tmp/wiki.uZlbA4/wiki/text/AlexDeucher 2004-01-09 10:04:58.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/AlexDeucher 2004-01-19 06:13:34.000000000 -0800 @@ -2,7 +2,7 @@ Email: agd5f at yahoo dot com -Developer and maintainer of MergedFB support for radeon hardware and general XFree86 enthusiast. +Developer and maintainer of MergedFB support for ATIRadeon hardware and general XFree86 enthusiast. [http://bugs.xfree86.org/show_bug.cgi?id=276 Radeon MergedFB info] @@ -10,7 +10,7 @@ [http://www.botchco.com/alex/radeon/Xv Radeon Overlay (Xv) Projects] -[http://www.botchco.com/alex/savage/ S3 Savage DRI support] +S3Savage DRI support ---- CategoryHomepage |
From: <jrf...@us...> - 2004-01-22 12:02:17
|
diff -urN /tmp/wiki.rDOOMz/wiki/text/Download /home/groups/d/dr/dri/wiki/text/Download --- /tmp/wiki.rDOOMz/wiki/text/Download 2004-01-13 16:01:22.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/Download 2004-01-21 13:57:02.000000000 -0800 @@ -1,7 +1,7 @@ '''Contents''' [[TableOfContents]] -= Source = +=== Source === == CVS == @@ -15,7 +15,7 @@ You can download the Linux kernel modules for XFree86 4.2.x at [http://www.xfree86.org/~alanh]. -Kernel modules for subsequent versions of XFree86 can be found in the XFree86 +Linux Kernel modules for subsequent versions of XFree86 can be found in the XFree86 source tree in the directory `xc/programs/Xserver/hw/xfree86/os-support/linux/drm` |
From: <jrf...@us...> - 2004-01-26 12:02:19
|
diff -urN /tmp/wiki.qeS1ff/wiki/text/LocalSpellingWords /home/groups/d/dr/dri/wiki/text/LocalSpellingWords --- /tmp/wiki.qeS1ff/wiki/text/LocalSpellingWords 2003-12-11 02:56:28.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/LocalSpellingWords 2004-01-25 12:49:06.000000000 -0800 @@ -87,3 +87,9 @@ Accesses always and as can directly hardware internal maybe or others parts rendering share side similar something target three used with Free86 + +Rage cards driver drivers graphics support supported + +Rage cards drivers + +Inc Technologies ati |