Re: [Dri-devel] bug in DRI with G400?
On Thursday 20 December 2001 15:01 pm, Gavriels State wrote: > The horizontal rotor appears correctly on our NVidia and Rage128 > test machines. > > The only known problem that we have on NVidia GL is a failure to > draw the lightmap used for the rocket exhaust and the explosion of the > other helicopter. > > On the Rage128 with DRI, there are several lighting bugs in the Adventure > demo, and some severe problems with Shiny's Sacrifice. Interestingly, > the Xi GL exhibits some of the same problems... Shall I contribute my G400 for tests? or is there a way to make a screenshot to show the problem? :) -- Hetz Ben Hamo [EMAIL PROTECTED] ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] bug in DRI with G400?
Hi Guys, I don't know if this mailing lists fits the problem - but here goes... My machine: Pentium 4 1.5GB and Matrox G400. The problem appears both in Matrox drivers and in the standard XFree 4.1.0 RPMs from Redhat 7.2. I installed WineX and tried 3DMark 2000 with it - and it runs pretty good (60% the speed of native windows - which I consider for a first version of WineX pretty good).. However - there is one problem: On the first series of tests there is a demo of helicopter shooting another helicopter - and the horizonal rotor is not shown while the vertical rotor shows ok. I checked the same 3DMark with original windows and the problem doesn't appear... DRI problem or WineX problem? (I'm cc'ing this email to WineX developers as well) Thanks, -- Hetz Ben Hamo ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] ATI driver for Fire 8700/8800
I probably didn't explain myself well, The FireGL card is basically the same as the 7500/7800 with some modification to enable it to perform much faster then the 7500/7800. So basically the FireGL driver can be with some very minor modifications work with the 7500/7800 based cards. Currently (and people - please correct me if I'm wrong) the Linux drivers through DRI are not even close in performance compared to ATI's drivers in Windows 2k/XP/9X - and as a potential customer - I do expect a company like ATI to provide me with the fastest drivers to really use my card. If I recall correctly, ATI didn't re-hire PI/VA to write the Linux drivers for the 7500/7800 cards and ATI said before that they are written in-house.. So Alex, since I assume you work at ATI (at least according to your email address) - could you ask for the official stance of the drivers regarding the 7500/7800? status about them? I hardly belive that telling people about those drivers will violate any NDA. Thanks, -- Hetz Ben Hamo [EMAIL PROTECTED] ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] ATI driver for Fire 8700/8800
On Wednesday 21 November 2001 17:49 pm, you wrote: > Hey, did these ATI FireGL products already hit the stores now? > AFAIK they have not. > > As Linus always told: Things will come when they are done. > Unlike Linus, the driver wont be open source, simply because > of the high amount of trade secrets contained within. But > on the other side you will get premium support on this code. > And you will get a bunch of grafics industry important features > that you wont see in that concentrated form at much other drivers. Yeah, but would ATI release drivers for the 7500/7800/8500 or only to the 8500 series? Any time frame? I'm going to order a machine soon (dual AMD) and I'm interested buying the Radeon 8500DV and so far not a single word from ATI regarding wether the card will be fully supported under Linux (and I mean video in/out [V4L compatibility is very important], DVD playback (including Xv support), TV tuner etc.. - will of this will be supported with the upcoming driver? NVidia for example have a nice trick - 95% of their drivers code is the same on Linux and on Windows, with only some modifications like kernel modules for Linux and agpgard - will ATI do the same? -- Hetz Ben Hamo [EMAIL PROTECTED] ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Matrox G450 (PCI) and DRI
Matrox just released a set of new drivers for both XFree 4.0.x and 4.1.0 with the ability to use hardware 3D acceleration on the 2nd screen, among other things.. www.matrox.com -- Hetz Ben Hamo [EMAIL PROTECTED] On Wednesday 31 October 2001 13:17 pm, Michael Greger wrote: > Hi, > > Has anybody experience with a MGA G450 (PCI) and direct rendering? > > In my system starting an OGL application, e.g. "atlantis" causes a system > crash. > > I use the X4.1.0 driver with kernel 2.4.13 module (mga.o). > Also tested the driver 1.4.3 from the Matrox web page. > glxinfo shows this > > OpenGL renderer string: Mesa DRI G400 20010321 AGP 1x (?) > ... > direct rendering: yes > > lsmod shows: > > mga usage:1 > agpgart usage: 3 > > > Is there a special client (_dri-)driver available for the G450 PCI? > What does AGP 1x mean on a PCI board? > > Thank you and best regards, > Michael > > > > Michael Greger > Waldpromenade 70 > 82131 Gauting > eMail: [EMAIL PROTECTED] > > > _ > Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp > > > ___ > Dri-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/dri-devel ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Matrox G550 support?
Hi All, Since I'm not under any NDA and I've started to see some info about this card, then I thought to ask this: Matrox are planning to release Matrox G550 card until the end of this month. The card, from a technical point of view will be a continuation of Matrox G450 - it will have some T&L support (only 1 feature of the T&L actually), 128-bit DDR support etc... (you can read about it at: http://www.tech-report.com/onearticle.x/2329) Now, since this card will be out until the end of this month, and XFree 4.1 will be also coming out around this time frame, then I wonder if there is a plan to support it at least in terms of 2D. Daryll? Also, I would like to ask - since Matrox hired a guy who would take care of the Linux issue - will VA Linux develop the DRI and other parts of this card? or this time Matrox will do it directly? (please tell me that VA guys will do, cause the VA guys have much more experience with X drivers). Any time schedule? Thanks, Hetz ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Re: kmix & SB Live
Grrr oops, wrong email address :) Hetz On Tuesday 24 April 2001 13:35, Mike A. Harris wrote: > On Tue, 24 Apr 2001, Hetz Ben Hamo wrote: > >Date: Tue, 24 Apr 2001 15:23:18 + > > From: Hetz Ben Hamo <[EMAIL PROTECTED]> > > >To: [EMAIL PROTECTED] > >Content-Type: text/plain; > > charset="iso-8859-1" ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] kmix & SB Live
Hi, I seem to have a small problem with kmix.. I patched my SB Live driver to have bass/treble support in the driver, and kmix show it, and I can set it - but it seems it doesn't save those values, which means: if I exit from X and restart KDE, then those values are going back to the default.. Any suggestions? Hetz ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Re: Inline assembly question
URL?? The "rawhide" dir has disappeared from redhat's FTP sites Hetz On Sunday 01 April 2001 00:05, Mike A. Harris wrote: > On Sat, 31 Mar 2001, Greg Hughes wrote: > >Inline assembly experts, > > > >I've been palying with RedHat 7.1 Beta. This ships with gcc 2.96.77, > >which is much better than the 2.96 bundled with RedHat 7.0. This > >compiler can build the xc tree from the trunk, but it chokes trying to > >build the mesa-3-5-branch. It doesn't like the COPY_DWORDS macro in the > >r128, radeon, and i810 directories. > > > > > >#define COPY_DWORDS( j, vb, vertsize, v ) \ > > __asm__ __volatile__( "rep ; movsl" \ > > > > : "=%c" (j), "=D" (vb) \ > > : "0" (vertsize), \ > > > > "D" ((long)vb), \ > > "S" ((long)v)\ > > > > : "esi" ) > > > >The error is: > > > > Can't find a register in class `SIREG' while reloading `asm'. > > > >My question: Is this a compiler defect, or is the compiler just being > >more strict? > > gcc-2.96-80.src.rpm is our latest. I dunno if it changes > anything or not. I'm inquiring about this internally and if i > find out anything I'll post it here. ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Inline assembly question
Try upgrading to GCC 2.96-79 - I think it's fixed there.. Hetz On Saturday 31 March 2001 23:27, Greg Hughes wrote: > Inline assembly experts, > > I've been palying with RedHat 7.1 Beta. This ships with gcc 2.96.77, > which is much better than the 2.96 bundled with RedHat 7.0. This > compiler can build the xc tree from the trunk, but it chokes trying to > build the mesa-3-5-branch. It doesn't like the COPY_DWORDS macro in the > r128, radeon, and i810 directories. > > > #define COPY_DWORDS( j, vb, vertsize, v ) \ >__asm__ __volatile__( "rep ; movsl" \ > > : "=%c" (j), "=D" (vb) \ > : "0" (vertsize), \ > >"D" ((long)vb), \ >"S" ((long)v)\ > > : "esi" ) > > The error is: > > Can't find a register in class `SIREG' while reloading `asm'. > > My question: Is this a compiler defect, or is the compiler just being > more strict? > > Thanks, > > Greg Hughes[EMAIL PROTECTED] > > > ___ > Dri-devel mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/dri-devel ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
