Re: [Dri-devel] Sorta OT: Congrats on DRI success Block Diagram Feature Checklists (Doc) proposals.
[EMAIL PROTECTED] wrote: Firstly a block diagram showing how the the various aspects of 3D on Linux fit together. ie how DRI, XFree86 4.1, the window manager, Linux Kernal, OpenGL, the actual drivers for various graphics chipsets etc fits together. This I feel would make it easier to see the big picture of 3D accelleration on Linux, making it easier for people to see where things are going wrong. There are two block diagrams available: 1) A high level, simplified diagram available at http://www.precisioninsight.com/dr/topper.jpg 2) A low level, detailed diagram available in low resolution at http://www.precisioninsight.com/dr/mini_poster.jpg and high resolution at http://www.precisioninsight.com/dr/poster.jpg Secondly a Feature Checklist page for each graphics chipset / graphics card (where apropriate) showing the HW features of each card and whether or not they are implemnted in DRI / driver or the status of said function. Good suggsestion. Two items to consider here: 1) Work with Frank Worsely regarding the content of the DRI site. He has been doing an excellent job in this area. 2) The biggest challenge for getting information for some of the drivers is identifying an owner. The 3Dfx driver for example, has a few developers submitting patches here and there; but hasn't changed much in over a year. There are other drivers in similar shape. Regards, Jens -- /\ Jens Owen/ \/\ _ [EMAIL PROTECTED] /\ \ \ Steamboat Springs, Colorado ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] DRI CVS mesa-4-0-branch doesn't compile
Have anyone got any luck compiling DRI CVS mesa-4-0-branch ? It compiles fine (it looks so), but during link step complains - -lXext not found ... -- Zilvinas Valinskas ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] DRI CVS mesa-4-0-branch doesn't compile
On Sat, Dec 08, 2001 at 06:19:05PM -0500, Zilvinas Valinskas wrote: Have anyone got any luck compiling DRI CVS mesa-4-0-branch ? It compiles fine (it looks so), but during link step complains - -lXext not found ... Hmm, I hate to reply myself but this is strange - if I change xc/conf/cf/host.def like this #define ProjectRoot /opt/X11R6-DRI the make World fails but if I leave ProjectRoot commented as it is ... compiles just fine ... that's very weird. :) -- Zilvinas Valinskas ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel -- Zilvinas Valinskas ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] DRI CVS mesa-4-0-branch doesn't compile
You need to compile DRI mesa-4-0-branch alongside mesa_4_0_branch from Mesa3d. You'll also need to specify your current X libs. Add this to your host.def: #define LdPreLib -L$(BUILDLIBDIR) -L$(USRLIBDIR) -L/usr/X11R6/lib/ --- Dan Chen [EMAIL PROTECTED] GPG key: www.cs.unc.edu/~chenda/pubkey.gpg.asc On Sat, 8 Dec 2001, Zilvinas Valinskas wrote: Have anyone got any luck compiling DRI CVS mesa-4-0-branch ? It compiles fine (it looks so), but during link step complains - -lXext not found ... ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] DRI CVS mesa-4-0-branch doesn't compile
On Sun, 2001-12-09 at 02:28, Zilvinas Valinskas wrote: On Sat, Dec 08, 2001 at 08:06:18PM -0500, Daniel T. Chen wrote: You need to compile DRI mesa-4-0-branch alongside mesa_4_0_branch from What do you mean along side ? Get the Mesa 4.0 (mesa_4_0_branch from mesa3d.sf.net ?) and modify host.def with #define MesaSrcDir $MESA_SRC/Mesa4.0 ??? That used to be necessary until very recently, but now Mesa 4.0.1 has been imported into the mesa-4-0-branch, so it can be built like the trunk. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] dri trouble
Hi ppl! I have come to the conclusion that there is a bug somewhere (TM). Using XF86 cvs from about 4 days ago, gatos cvs from the same time. Following happens with the r128.o I get in either xf86 cvs or dri cvs: - ten kernel: [drm:r128_cce_indirect] *ERROR* process 2635 using buffer owned by 0 - (X logs don't show anything) This is IMHO the reason why when using dri: - there are minor display distortions (parts of screen remain black, basically the kde splash screen is completely fscked, but it sorts out later). - when I do a chvt 1;chvt 7, X starts eating all the CPU time and 2d accelerated functions seize working (mouse can be moved but kde panel doesn't pop up). killall X doesn't work, killall -9 X does. When this bug feels like it should become especially mean to me, this killall -9 X causes a complete machine lockup. This also happens immediately after a fresh bootup when I haven't done anything yet. Volodya: whether km is loaded doesn't matter. These problems disappear when I comment dri in XF86Config. Card: ATI AIW 128 16M AGP (non-pro). Kernel 2.4.14. RH 7.1 with current patches. Hints (besides not using dri)? I finally want to get better uptimes than 3 days. Bye, Peter Surda (Shurdeek) [EMAIL PROTECTED], ICQ 10236103, +436505122023 -- The best things in life are free, but the expensive ones are still worth a look. msg02104/pgp0.pgp Description: PGP signature
[Dri-devel] Re: [Xpert]dri trouble
On Sun, 2001-12-09 at 03:49, Peter Surda wrote: - there are minor display distortions (parts of screen remain black, basically the kde splash screen is completely fscked, but it sorts out later). Does the R128BlockHandler() function of the driver you're using contain a FLUSH_RING(); ? - when I do a chvt 1;chvt 7, X starts eating all the CPU time and 2d accelerated functions seize working (mouse can be moved but kde panel doesn't pop up). killall X doesn't work, killall -9 X does. When this bug feels like it should become especially mean to me, this killall -9 X causes a complete machine lockup. In R128EnterVT(), try moving the R128ModeInit() and R128EngineInit() calls before the code guarded by #ifdef XF86DRI. Those are fixes I made in DRI CVS some time ago, but at least the first one is in XFree86 CVS now. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
