Re: [Dri-devel] Athlon/Kt133/Radeon QD system locking with > 1GB ram

2002-01-23 Thread Steve Bergman
On Wed, 2002-01-23 at 13:56, Brian Paul wrote: > > FYI, the new issue if Linux Journal (february, page 78) has a technical > support question regarding stability of a Soyo K7V Dragon/1.4GHz Athlon > system. The system runs fine with 1GB of ram but is flaky with 1.5GB > > The responses to this

[Dri-devel] S3 Savage IX/MX DRI support

2002-01-23 Thread Eugene Brevdo
Hi all, I guess this type of e-mail comes up every once in a while, but I see that the Utah-GLX project made a bit of headway with their support for the S3 Savage chip (a very popular chip with laptop manufacturers). However, I haven't seen too much on the Utah-GLX scene lately, and it would be n

Subject: Re: [Dri-devel] Athlon/Kt133/Radeon QD system locking with> 1GB ram

2002-01-23 Thread Steve Bergman
On Wed, 2002-01-23 at 13:56, Brian Paul wrote: > Is your system stable with 1.5GB of RAM when X is not running? > Or, when X is running, but the DRI is disabled? Yes. I have now tested 2D X for about an hour now with the dri and glx modules *NOT* loaded at all. It seems quite stable running a

[Dri-devel] Re: S3 Savage IX/MX DRI support

2002-01-23 Thread Mattias Jansson
On Wed, 2002-01-23 at 22:37, Eugene Brevdo wrote: > Hi all, > I guess this type of e-mail comes up every once in a while, but I see > that the Utah-GLX project made a bit of headway with their support for > the S3 Savage chip (a very popular chip with laptop manufacturers). > However, I haven't s

Re: [Dri-devel] ideal primitive rates?

2002-01-23 Thread Keith Whitwell
Karl Czajkowski wrote: > > We have one particularly brute-force application that draws large > batches of points (millions per frame) with low alpha value using an > acculative blend mode and no z-buffer. I am curious what kind of > performance is expected through the DRI in the long run. > > U

[Dri-devel] SOME ITEMS THAT YOU MAY BE INTERESTED IN OR BE ABLE TO ADVISE ME ON

2002-01-23 Thread kriss rolo
These are the items that iam interested in selling.. Could you help me with some details on the goods, history, origin etc. are these worth anything and if so who would i contact with regards to selling them? and the best way to sell them ie auction etc APOLOGISE IF YOU HAVE ALREADY RECEIVED THIS

Re: [Dri-devel] [PATCH] ioremap_nocache() support in DRM

2002-01-23 Thread Paul Mundt
On Wed, Jan 23, 2002 at 05:54:17PM +, Keith Whitwell wrote: > > At the moment, DRM provides a wrapper for ioremap() but does not do so for > > ioremap_nocache().. this is unfortunate, as a good number of framebuffer > > drivers (probably X drivers as well) don't always want to remap in cached

[Dri-devel] Question about MGA driver texturing patch

2002-01-23 Thread Lawrence Gold
Hi, Back in June 2001, Karl Lessard posted the following patch to the mailing list: http://www.geocrawler.com/lists/3/SourceForge/680/0/5955984/ Are there any plans to incorporate this? I perused the latest CVS sources and wasn't able to find this in there. Thanks! ___

[Dri-devel] Shared texture object problem

2002-01-23 Thread Lynn Quam
I have an OpenGL (Mesa) application that works fine except when I attempt to render the same texture objects in more than one window (GLX windows) at the same time, in which case the textures are incorrect and I get the following error message: Couldn't alloc placeholder sz 4 ofs 18

[Dri-devel] Was: Re: Athlon/Linux bug found --- Solution is under way!

2002-01-23 Thread Dieter Nützel
Words from AMD came. It has something to-do with "potential cache coherency interaction between Athlon speculative writes and the GART". Both Nvidia GART and kernel GART are concerned. Patches are under development if I understand it right. http://marc.theaimsgroup.com/?l=linux-kernel&m=1011811

Re: [Dri-devel] Shared texture object problem

2002-01-23 Thread Keith Whitwell
Lynn Quam wrote: > > I have an OpenGL (Mesa) application that works fine except when I attempt to render > the same texture objects in more than one window (GLX windows) at the same time, in >which > case the textures are incorrect and I get the following error message: > >Couldn't alloc pl

[Dri-devel] i think i have a functioning FreeBSD SiS 630e/300 agp device. howdo i test it?

2002-01-23 Thread John Utz
hi; i have reason to suspect that i have successfully hooked up agp in my FreeBSD kernel. Why? because agp0 is now attached to a pci id that matches the one that http://www.yourvote.com/pci/vendors.txt asserts is the agp port on the SiS630 agp0@pci1:0:0: class=0x03 card=0x80351043 chip=0

Re: [Dri-devel] Question about MGA driver texturing patch

2002-01-23 Thread Keith Whitwell
Lawrence Gold wrote: > > Hi, > > Back in June 2001, Karl Lessard posted the following patch to the mailing > list: > > http://www.geocrawler.com/lists/3/SourceForge/680/0/5955984/ > > Are there any plans to incorporate this? I perused the latest CVS sources > and wasn't able to find t

[Dri-devel] FreeBSD SiS 630e/300 drm port: who's favorite drm implementationshould i mindlessly copy?

2002-01-23 Thread John Utz
hi again; is there a drm implementation in cvs that is looked upon with favor as being done 'more correctly than others'? is there a drm implementation in cvs that is looked upon with favor as being done 'more simply than others'? note that i have no expectation as to the shape of the venn di

[Dri-devel] how does drm handle chipset specific features in a generalized way?

2002-01-23 Thread John Utz
one last question before i knock off for the nite suppose one has two cards. the first, the FooBarTech VisiBlaster, has special hardware for optimizing the generation of very realistic clouds. the second, the BazGrafix RadiantTurkeyBaster XL6000 AGP 4X Value Edition, has special hardware

Re: [Dri-devel] how does drm handle chipset specific features in a generalized way?

2002-01-23 Thread Daryll Strauss
On Thu, Jan 24, 2002 at 12:55:28AM -0600, John Utz wrote: > one last question before i knock off for the nite > > suppose one has two cards. > > the first, the FooBarTech VisiBlaster, has special hardware for optimizing > the generation of very realistic clouds. > > the second, the BazGraf