Re: [Dri-devel] reproducible VTK + DRI breakage

2003-03-11 Thread Keith Whitwell
Charl P. Botha wrote: Dear list, I've attached a wxPython + VTK example (just the wxVTKRenderWindowInteractor.py slightly modified) to illustrate the drmCmdBuffer: -22 bug that I'm actually seeing. It seems my glthreads.c attempts were off the track. In anycase, if you have wxPython and VTK with

Re: [Dri-devel] reproducible VTK + DRI breakage

2003-03-11 Thread Charl P. Botha
On Tue, 2003-03-11 at 10:16, Keith Whitwell wrote: Charl P. Botha wrote: In anycase, if you have wxPython and VTK with working Python wrappings installed, please run the attached example. Manipulate the 3D cone in both windows and then close the one window. Manipulating the remaining 3D

Re: [Mesa3d-dev] Re: [Dri-devel] Mesa C++ driver framework update

2003-03-11 Thread Gabriel Dos Reis
José Fonseca [EMAIL PROTECTED] writes: | On Mon, Mar 10, 2003 at 11:59:05PM +, Keith Whitwell wrote: | | Unless C++ can figure out at compile time *exactly* which class is being | invoked, I think... It's hard to know. | | It can, with templates. Even with no templates, current C++

Re: [Mesa3d-dev] Re: [Dri-devel] Mesa C++ driver framework update

2003-03-11 Thread Manfred Odenstein
No, because one of the things C++ does is pass around an extra parameter -- namely the 'self' pointer. The 'real' prototype looks something like: void Context::BlendFunc( Context *self, GLenum sfactor, GLenum dfactor ) Thats correct, but not with static methods (please correct me, if

Re: [Mesa3d-dev] Re: [Dri-devel] Mesa C++ driver framework update

2003-03-11 Thread Keith Whitwell
Gabriel Dos Reis wrote: Keith Whitwell [EMAIL PROTECTED] writes: [...] | struct function_table { |... |void (*BlendFunc)(GLcontext *ctx, GLenum sfactor, GLenum dfactor); |... | } driver; | and | class Context { |... |void BlendFunc(GLenum sfactor, GLenum dfactor); |

Re: [Dri-devel] reproducible VTK + DRI breakage

2003-03-11 Thread Keith Whitwell
Charl P. Botha wrote: On Tue, 2003-03-11 at 10:16, Keith Whitwell wrote: Charl P. Botha wrote: In anycase, if you have wxPython and VTK with working Python wrappings installed, please run the attached example. Manipulate the 3D cone in both windows and then close the one window. Manipulating

Re: [Mesa3d-dev] Re: [Dri-devel] Mesa C++ driver framework update

2003-03-11 Thread Gabriel Dos Reis
Keith Whitwell [EMAIL PROTECTED] writes: [...] | struct function_table { |... |void (*BlendFunc)(GLcontext *ctx, GLenum sfactor, GLenum dfactor); |... | } driver; | and | class Context { |... |void BlendFunc(GLenum sfactor, GLenum dfactor); |... | } ; | You can't

Re: [Dri-devel] reproducible VTK + DRI breakage

2003-03-11 Thread Keith Whitwell
Keith Whitwell wrote: Charl P. Botha wrote: On Tue, 2003-03-11 at 10:16, Keith Whitwell wrote: Charl P. Botha wrote: In anycase, if you have wxPython and VTK with working Python wrappings installed, please run the attached example. Manipulate the 3D cone in both windows and then close the one

Re: [Dri-devel] reproducible VTK + DRI breakage

2003-03-11 Thread Alan Hourihane
Keith, Do you want to try running two copies of the 'tunnel' demo ? Alan. --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list

Re: [Dri-devel] reproducible VTK + DRI breakage

2003-03-11 Thread Charl P. Botha
On Tue, 2003-03-11 at 12:44, Keith Whitwell wrote: Ah, actually this was my fault. Missed an installation step on the new box... glthreads is running ok here, now. Which is good -- but can you still post a summary of outstanding issues. I don't have vtk installed, but will do so if

Re: [Dri-devel] drm-filp-0-1-branch and radeon

2003-03-11 Thread Keith Whitwell
Keith Whitwell wrote: Linus Torvalds wrote: On Sun, 2 Mar 2003, Linus Torvalds wrote: The _second_ DRI-enabled X startup caused problems, even if I had done multiple non-DRI X sessions in between. This is what makes me think that the DRI kernel modules keep some history around that they

Re: [Dri-devel] drm-filp-0-1-branch and radeon

2003-03-11 Thread Michel Dänzer
On Die, 2003-03-11 at 14:41, Keith Whitwell wrote: Keith Whitwell wrote: Evidence for this: - The lockup is new, while the code has been suspicious forever... - I can exit and restart X just fine, it's only recycle that locks. From the kernel point of view, these should be

[Dri-devel] Corrupted textures on 64bit tuxracer

2003-03-11 Thread Mike A. Harris
On x86_64 (probably any 64bit arch also, but I haven't tested ia64 or alpha yet), tuxracer experiences texture corruption on ice patches and the sides of some hills. This is occurs on the very first race, so it's not hard to reproduce. AS you're gliding along, the grey patch approaches and

Re: [Dri-devel] Corrupted textures on 64bit tuxracer

2003-03-11 Thread Michel Dänzer
On Die, 2003-03-11 at 17:01, Mike A. Harris wrote: On x86_64 (probably any 64bit arch also, but I haven't tested ia64 or alpha yet), tuxracer experiences texture corruption on ice patches and the sides of some hills. This is occurs on the very first race, so it's not hard to reproduce. AS

Re: [Dri-devel] reproducible VTK + DRI breakage

2003-03-11 Thread Michel Dänzer
On Die, 2003-03-11 at 13:51, Charl P. Botha wrote: On Tue, 2003-03-11 at 12:44, Keith Whitwell wrote: Ah, actually this was my fault. Missed an installation step on the new box... glthreads is running ok here, now. Which is good -- but can you still post a summary of outstanding

[Dri-devel] Double define for radeon data structures?

2003-03-11 Thread Guido Landra
Hi all, This is my first post, be patient, please! :) I'm reading radeon code on CVS. In radeon_drm.h, on kernel side, I can see a lot of data structures already defined on client side in radeon_sarea.h. They

Re: [Dri-devel] Double define for radeon data structures?

2003-03-11 Thread Keith Whitwell
Guido Landra wrote: Hi all, This is my first post, be patient, please! :) I'm reading radeon code on CVS. In radeon_drm.h, on kernel side, I can see a lot of data structures already defined on client side in radeon_sarea.h. They are about shared area, but also about data types used by IOCTLs

Re: [Dri-devel] reproducible VTK + DRI breakage

2003-03-11 Thread Michel Dänzer
On Die, 2003-03-11 at 18:37, Charl P. Botha wrote: On Tue, 2003-03-11 at 18:29, Michel Dänzer wrote: On Die, 2003-03-11 at 13:51, Charl P. Botha wrote: On 4.3.0 however, the vtxfmt assert error (and application termination) seems to happen very often with applications with multiple

[Dri-devel] Stay young with our product. ocqhqoviwj fqjhcji

2003-03-11 Thread
*As seen on TV* The health discovery that reverses signs of aging naturally and that is completely safe and effective is on sale for a limited time! Buy a two-month supply of our product and we will give you one month free! All natural H_G_H Enhancer will help you with all of the following: -

Re: [Dri-devel] Corrupted textures on 64bit tuxracer

2003-03-11 Thread Dave Jones
On Tue, Mar 11, 2003 at 11:01:59AM -0500, Mike A. Harris wrote: On x86_64 (probably any 64bit arch also, but I haven't tested ia64 or alpha yet), tuxracer experiences texture corruption on ice patches and the sides of some hills. This is occurs on the very first race, so it's not hard to

[Dri-devel] Re: dri_driver_features.phtml dri_radeon_features.html

2003-03-11 Thread Brian Paul
Smitty wrote: Hi Brian In light of your well maintained: http://dri.sourceforge.net/doc/dri_driver_features.phtml I think it's about time that: http://dri.sourceforge.net/doc/dri_radeon_features.html crawled into a hole and died. Do you want to pull in anything from this page or can I get rid

[Dri-devel] drmScatterGatherAlloc missing from docs

2003-03-11 Thread Philip Brown
http://dri.sourceforge.net/doc/drm_low_level.html should be updated with a functional description of drmScatterGatherAlloc() [and probably a few other drmXXXYYY() routines that have appeared since 1999 ;-) ] --- This SF.net email is

[Dri-devel] Re: [XFree86] S3 Virge (3D)

2003-03-11 Thread Ian Romanick
Bellard, Karen L wrote: I have a HP Pavilion 7410P and it has S3 Virge (3D). Can this support OpenGL? It is /possible/, but the driver is not complete. There is a branch in the DRI tree where this work was being done. The person that was working on it seems to have stopped working on it a