Re: [Dri-devel] Re: [Mesa3d-dev] Re: Planning to merge vtx-0-2-branch soon

2003-11-12 Thread Brian Paul
Ian Romanick wrote: Michel DÃnzer wrote: - libGL.so Why not move this to Mesa as well? A single libGL which works with most things you can think of throwing it at would be great I think. I don't think it belongs there. The libGL in the DRI tree is 100% specific to X11. The amount of cod

[Dri-devel] Re: [Mesa3d-dev] Re: Planning to merge vtx-0-2-branch soon

2003-11-12 Thread Ian Romanick
Michel DÃnzer wrote: - libGL.so Why not move this to Mesa as well? A single libGL which works with most things you can think of throwing it at would be great I think. I don't think it belongs there. The libGL in the DRI tree is 100% specific to X11. The amount of code that is sharable with a n

[Dri-devel] Re: Planning to merge vtx-0-2-branch soon

2003-11-12 Thread Michel Dänzer
On Wed, 2003-11-12 at 16:22, Keith Whitwell wrote: > > We could set up the DRI tree to have *some* version of Mesa plus drivers > installed actually in the tree. One problem with this is it possibly extends > the chain to the user - Mesa->DRI->Xfree86->Distro->user... (Actually Mesa > updat

Re: [Dri-devel] Planning to merge vtx-0-2-branch soon

2003-11-12 Thread Keith Whitwell
Alex Deucher wrote: Currently all my mergedfb work has been in the 2D driver, but I'd like to start working on some 3d stuff (time permitting). however, I don't have write access to the mesa tree. It's not real important at this point I guess, but eventually... Also isn't mesa hosted on sourcefo

Re: [Dri-devel] Planning to merge vtx-0-2-branch soon

2003-11-12 Thread Alex Deucher
Currently all my mergedfb work has been in the 2D driver, but I'd like to start working on some 3d stuff (time permitting). however, I don't have write access to the mesa tree. It's not real important at this point I guess, but eventually... Also isn't mesa hosted on sourceforge? will there be

Re: [Dri-devel] the state of Parhelia on FreeBSD

2003-11-12 Thread Alex Deucher
I doubt many developers are going to work on it because the rest of the drivers are closed source and few if any developers have parhelia hardware. you'd probably be best off trying to port it yourself. you can look at how the drm modules differ from linux to freebsd for other drivers (radeon, mg

[Dri-devel] Planning to merge vtx-0-2-branch soon

2003-11-12 Thread Keith Whitwell
OK, I'm planning to merge the vtx-0-2-branch to Mesa CVS trunk fairly shortly. At the moment, it is well tested with the X11 driver, and it compiles with the r200 driver from linux-solo. I'll make sure the r200 driver works properly before merging, but there are a lot of other drivers out ther

[Dri-devel] [Bug 861] program exits with: drmRadeonCmdBuffer: -22

2003-11-12 Thread bugzilla-daemon
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter your comments there. http://bugs.xfree86.org/show_bug.cgi?id=861 [EMAIL PROTECTED] changed: What|Removed |Added ---

[Dri-devel] the state of Parhelia on FreeBSD

2003-11-12 Thread Mikhail Teterin
Hello! Matrox offers the sources for the Linux kernel part of mtx available. Has anyone looked into morphing those into the drm style, so an mtx.ko can be built on FreeBSD? It does not look like a big deal for someone, who knows the API already... Simply copying the mtx_drv.o into lib/modules/dr