From: Chris E. <ch...@in...> - 2000-08-15 22:25:26
|
I'm trying to understand how DRI and Mesa interact. I see in xc\lib\GL\mesa\dri\dri_mesa.c that a structure called MesaAPI gets setup with pointers to HW specific functions (InitDriver, CreateWindowBuffer, ...), but in grepping through the tree I don't see anything (other than minimal usage in dri_mesa.c) that uses the function pointers setup in the MesaAPI structure. In fact, I don't see anywhere that the InitDriver function gets called? Am I missing something? Thanks, -Chris |
From: Chris E. <ch...@in...> - 2000-08-16 19:32:47
|
> I'm trying to understand how DRI and Mesa interact. I see in xc\lib\GL\mesa\dri\dri_mesa.c > that a structure called MesaAPI gets setup with pointers to HW specific functions > (InitDriver, CreateWindowBuffer, ...), but in grepping through the tree I don't see > anything (other than minimal usage in dri_mesa.c) that uses the function pointers setup in > the MesaAPI structure. In fact, I don't see anywhere that the InitDriver function gets > called? Am I missing something? Ok, here's the deal. I incorrectly assumed that the MesaAPI struct members would be used indirectly. So, my grep for ->zzz returned nothing! Turns out the MesaAPI members seem to only be used in the dri_mesa.c file, and the driMesaZZZ functions are the ones that are called from the outside world. -Chris |
From: Brian P. <br...@va...> - 2000-08-16 21:51:47
|
Chris Edgington wrote: > > > I'm trying to understand how DRI and Mesa interact. I see in > xc\lib\GL\mesa\dri\dri_mesa.c > > that a structure called MesaAPI gets setup with pointers to HW specific functions > > (InitDriver, CreateWindowBuffer, ...), but in grepping through the tree I don't see > > anything (other than minimal usage in dri_mesa.c) that uses the function pointers setup > in > > the MesaAPI structure. In fact, I don't see anywhere that the InitDriver function gets > > called? Am I missing something? > > Ok, here's the deal. I incorrectly assumed that the MesaAPI struct members would be used > indirectly. So, my grep for ->zzz returned nothing! Turns out the MesaAPI members seem to > only be used in the dri_mesa.c file, and the driMesaZZZ functions are the ones that are > called from the outside world. Right. That code in there isn't as clear as it could be. But it was even worse a few months ago. If you have specific questions in there don't hesitate to ask. I'll try to answer promptly. -Brian |
From: Michael H. <mdh...@ho...> - 2000-08-16 23:20:59
|
On Wed, 16 Aug 2000 14:55:59 -0600, Brian Paul <br...@va...> said: > If you have specific questions in there don't hesitate to ask. Of what use is the Mesa code in the xc tree, since it only builds libGL, which seems to have no purpose without libGLU and libglut? -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdh...@ho... aa...@aa... If God lived on Earth, people would knock out all His windows. -- Yiddish saying |
From: Brian P. <br...@va...> - 2000-08-17 13:18:44
|
Michael Harnois wrote: > > On Wed, 16 Aug 2000 14:55:59 -0600, Brian Paul <br...@va...> said: > > > If you have specific questions in there don't hesitate to ask. > > Of what use is the Mesa code in the xc tree, since it only builds > libGL, which seems to have no purpose without libGLU and libglut? I can assure you that libGL has LOTS of uses without libGLU or GLUT. Mesa is in the xc/extras/ directory and used by both the client and server sides of X. On the client side, it's the basis for the 3D DRI hardware drivers that we've written. On the server side, it provides the rendering core for the GLX extension which allows indirect rendering. Hope I understood you correctly. -Brian |
From: Michael H. <mdh...@ho...> - 2000-08-17 18:55:25
|
On Thu, 17 Aug 2000 06:22:54 -0600, Brian Paul <br...@va...> said: > Michael Harnois wrote: >> >> Of what use is the Mesa code in the xc tree, since it only >> builds libGL, which seems to have no purpose without libGLU and >> libglut? > I can assure you that libGL has LOTS of uses without libGLU or > GLUT. > Mesa is in the xc/extras/ directory and used by both the client > and server sides of X. > On the client side, it's the basis for the 3D DRI hardware > drivers that we've written. On the server side, it provides the > rendering core for the GLX extension which allows indirect > rendering. OK. But then how does one build external clients that work when they require libGL, libGLU, and libglut? I see that there are pre-built Linux libraries for libGLU and libglut which "match" the libGL from the DRI xc tree, but as a FreeBSD user those do me no good at all. How do I get the full Mesa source, providing libGLU and libGLUT, that will mesh with the libGL built by the DRI xc tree? -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdh...@ho... aa...@aa... I have always been among those who believed that the greatest freedom of speech was the greatest safety, because if a man is a fool the best thing to do is to encourage him to advertise the fact by speaking. --Woodrow Wilson |
From: Daniel D. <da...@br...> - 2000-08-17 19:15:17
|
Feel free to correct me if I'm wrong but I assumed that only libGL was included because it is the only one with changes specific to DRI. In other words, you should be able to download the source to the others, compile them, and they should work correctly. This is not true for libGL. Mesa (normal version) wouldn't work correctly with DRI hence the inclusion of the DRI specific version. Daniel ----- Original Message ----- From: "Michael Harnois" <mdh...@ho...> To: "Brian Paul" <br...@va...> Cc: <Dri...@li...> Sent: Thursday, August 17, 2000 2:55 PM Subject: Re: [Dri-devel] DRI / Mesa Interaction > On Thu, 17 Aug 2000 06:22:54 -0600, Brian Paul <br...@va...> said: > > > Michael Harnois wrote: > >> > >> Of what use is the Mesa code in the xc tree, since it only > >> builds libGL, which seems to have no purpose without libGLU and > >> libglut? > > > > I can assure you that libGL has LOTS of uses without libGLU or > > GLUT. > > > Mesa is in the xc/extras/ directory and used by both the client > > and server sides of X. > > > On the client side, it's the basis for the 3D DRI hardware > > drivers that we've written. On the server side, it provides the > > rendering core for the GLX extension which allows indirect > > rendering. > > OK. But then how does one build external clients that work when they > require libGL, libGLU, and libglut? I see that there are pre-built > Linux libraries for libGLU and libglut which "match" the libGL from > the DRI xc tree, but as a FreeBSD user those do me no good at all. How > do I get the full Mesa source, providing libGLU and libGLUT, that will > mesh with the libGL built by the DRI xc tree? > > -- > Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA > mdh...@ho... aa...@aa... > I have always been among those who believed that > the greatest freedom of speech was the greatest safety, > because if a man is a fool the best thing to do > is to encourage him to advertise the fact by speaking. --Woodrow Wilson > > _______________________________________________ > Dri-devel mailing list > Dri...@li... > http://lists.sourceforge.net/mailman/listinfo/dri-devel |
From: Brian P. <br...@va...> - 2000-08-17 19:33:01
|
Daniel Davis wrote: > > Feel free to correct me if I'm wrong but I assumed that only libGL was > included because it is the only one with changes specific to DRI. In other > words, you should be able to download the source to the others, compile > them, and they should work correctly. This is not true for libGL. Mesa > (normal version) wouldn't work correctly with DRI hence the inclusion of the > DRI specific version. Exactly right. -Brian |
From: Nathan H. <na...@ma...> - 2000-08-17 16:29:24
|
On Wed, Aug 16, 2000 at 06:20:59PM -0500, Michael Harnois wrote: > On Wed, 16 Aug 2000 14:55:59 -0600, Brian Paul <br...@va...> said: > > > If you have specific questions in there don't hesitate to ask. > > Of what use is the Mesa code in the xc tree, since it only builds > libGL, which seems to have no purpose without libGLU and libglut? Mesa is used to build some server side modules/libraries specifically for the benefit of the DRI. The libGL.so is the client side aspect of Mesa which works closely with the server side components of Mesa. The libGLU and libglut libraries are entirely client side things, and so they are distributed seperately. -- Microsoft Windows 2000. Now with more than 63000 known innovations. |
From: Brian P. <br...@va...> - 2000-08-17 19:31:58
|
Michael Harnois wrote: > > On Thu, 17 Aug 2000 06:22:54 -0600, Brian Paul <br...@va...> said: > > > Michael Harnois wrote: > >> > >> Of what use is the Mesa code in the xc tree, since it only > >> builds libGL, which seems to have no purpose without libGLU and > >> libglut? > > > I can assure you that libGL has LOTS of uses without libGLU or > > GLUT. > > > Mesa is in the xc/extras/ directory and used by both the client > > and server sides of X. > > > On the client side, it's the basis for the 3D DRI hardware > > drivers that we've written. On the server side, it provides the > > rendering core for the GLX extension which allows indirect > > rendering. > > OK. But then how does one build external clients that work when they > require libGL, libGLU, and libglut? I see that there are pre-built > Linux libraries for libGLU and libglut which "match" the libGL from > the DRI xc tree, but as a FreeBSD user those do me no good at all. How > do I get the full Mesa source, providing libGLU and libGLUT, that will > mesh with the libGL built by the DRI xc tree? Download Mesa from www.mesa3d.org and compile libGLU and GLUT yourself. -Brian |
From: Michael H. <mdh...@ho...> - 2000-08-17 19:56:31
|
On Thu, 17 Aug 2000 12:37:07 -0600, Brian Paul <br...@va...> said: > Exactly right. So you're telling me specifically that there is no concern for version matching? This does stretch the imagination just a wee bit ... -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdh...@ho... aa...@aa... Some folks you don't have to satirize, you just quote 'em. --Tom Paxton |
From: Brian P. <br...@va...> - 2000-08-17 20:18:17
|
Michael Harnois wrote: > > On Thu, 17 Aug 2000 12:37:07 -0600, Brian Paul <br...@va...> said: > > > Exactly right. > > So you're telling me specifically that there is no concern for version > matching? This does stretch the imagination just a wee bit ... I didn't say that. Currently Mesa's libGL is version 1.2 and so is the DRI's libGL. That's not going to change until there's an OpenGL 1.3. And there's no immediate signs of that. If I misunderstood your comment, please elaborate. -Brian |
From: Michael H. <mdh...@ho...> - 2000-08-17 21:13:19
|
On Thu, 17 Aug 2000 13:19:15 -0600, Brian Paul <br...@va...> said: > I didn't say that. > Currently Mesa's libGL is version 1.2 and so is the DRI's libGL. > That's not going to change until there's an OpenGL 1.3. And > there's no immediate signs of that. > If I misunderstood your comment, please elaborate. Mesa has a stable version (3.2.1), a development version (3.3), and a CVS tree. Which of these corresponds with the libGL in the DRI tree? -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdh...@ho... aa...@aa... The first thing you should do when you get up is read the obituaries. You never know when you'll see a name that will just make your day. --Ed Salisbury |
From: Brian P. <br...@va...> - 2000-08-17 21:51:26
|
Michael Harnois wrote: > > On Thu, 17 Aug 2000 13:19:15 -0600, Brian Paul <br...@va...> said: > > > I didn't say that. > > > Currently Mesa's libGL is version 1.2 and so is the DRI's libGL. > > That's not going to change until there's an OpenGL 1.3. And > > there's no immediate signs of that. > > > If I misunderstood your comment, please elaborate. > > Mesa has a stable version (3.2.1), a development version (3.3), and a > CVS tree. Which of these corresponds with the libGL in the DRI tree? The DRI trunk has a beta snapshot of 3.3. The tdfx-2-1 branch has the latest Mesa 3.4 sources. I expect that the next official release of XFree86 with the DRI will have 3.4. -Brian |