Re: Moving towards a single driver binary for solo and DRI

2004-05-28 Thread Jon Smirl
--- Robert Voigt <[EMAIL PROTECTED]> wrote: > If you build the same *_dri.so for solo and DRI, what happens to > Mesa/src/mesa/drivers/dri/radeon/*/server/*_dri.c ? As I understand it, > they're only used by solo, and derived from and different to the > corresponding files in dri. > > I'm askin

Re: Moving towards a single driver binary for solo and DRI

2004-05-28 Thread Robert Voigt
If you build the same *_dri.so for solo and DRI, what happens to Mesa/src/mesa/drivers/dri/radeon/*/server/*_dri.c ? As I understand it, they're only used by solo, and derived from and different to the corresponding files in dri. I'm asking because if you get solo to use *_dri.c from dri, we wo

Re: Moving towards a single driver binary for solo and DRI

2004-05-27 Thread Dave Airlie
> > The final file shuffling step will be to make the DRI tree and the Mesa tree > use the libdrm.a build in the drm module. Right now we have *3* copies of the > same code. There is a copy in each of: drm/libdrm, xc/xc/lib/GL/dri/drm, and > src/mesa/drivers/dri/dri_client. That's just nuts (but

Re: Moving towards a single driver binary for solo and DRI

2004-05-27 Thread Ian Romanick
Keith Packard wrote: Around 12 o'clock on May 27, Ian Romanick wrote: I'm pretty sure that XFree86 and Xorg will continue to want to build 3D drivers as part of their distribution process. Even so, there are parts of Mesa that are needed to build libGL.so and libglx.a. With stable interfaces and

Re: Moving towards a single driver binary for solo and DRI

2004-05-27 Thread Keith Packard
Around 12 o'clock on May 27, Ian Romanick wrote: > I'm pretty sure that XFree86 and Xorg will continue to want to build 3D > drivers as part of their distribution process. Even so, there are parts > of Mesa that are needed to build libGL.so and libglx.a. With stable interfaces and published M

Re: Moving towards a single driver binary for solo and DRI

2004-05-27 Thread Keith Packard
Around 20 o'clock on May 27, Keith Whitwell wrote: > If the X server starts dynamically loading XYZ_dri.so and falling back to > software_dri.so if that fails, you mean? That would be great; no GL bits inside the X server > In that case, I guess X no longer needs an extras/Mesa, though they ma

Re: Moving towards a single driver binary for solo and DRI

2004-05-27 Thread Ian Romanick
Alex Deucher wrote: --- Keith Whitwell <[EMAIL PROTECTED]> wrote: As the xc/ tree will continue having to import Mesa to extras/Mesa, the libGL code could pick it up from there. could that be avoided with a SW only DRI driver like we've discussed several times on IRC and the ML? if libGLcore goes

Re: Moving towards a single driver binary for solo and DRI

2004-05-27 Thread Keith Whitwell
Alex Deucher wrote: --- Keith Whitwell <[EMAIL PROTECTED]> wrote: Jon Smirl wrote: --- Ian Romanick <[EMAIL PROTECTED]> wrote: I'm going to try and wrap up the remaining issues preventing a single driver binary. As part of that, I'm going to move the Mesa copies of dri_util.[ch] and glcontext

Re: Moving towards a single driver binary for solo and DRI

2004-05-27 Thread Alex Deucher
--- Keith Whitwell <[EMAIL PROTECTED]> wrote: > Jon Smirl wrote: > > --- Ian Romanick <[EMAIL PROTECTED]> wrote: > > > >>I'm going to try and wrap up the remaining issues preventing a > single > >>driver binary. As part of that, I'm going to move the Mesa copies > of > >>dri_util.[ch] and glco

Re: Moving towards a single driver binary for solo and DRI

2004-05-27 Thread Jon Smirl
There is another copy: xc/lib/XvMC/hw/i810/xf86drm.c = Jon Smirl [EMAIL PROTECTED] __ Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger. http://messenger.yahoo.com/ ---

Re: Moving towards a single driver binary for solo and DRI

2004-05-27 Thread Ian Romanick
Keith Whitwell wrote: Which reminds me; we will need to get an uptodate Mesa into extras/Mesa and go back to periodically updating it... I was thinking that right after we get all this stuff taken care of would be a perfect time. :) --- This S

Re: Moving towards a single driver binary for solo and DRI

2004-05-27 Thread Keith Whitwell
Keith Whitwell wrote: Jon Smirl wrote: --- Ian Romanick <[EMAIL PROTECTED]> wrote: I'm going to try and wrap up the remaining issues preventing a single driver binary. As part of that, I'm going to move the Mesa copies of dri_util.[ch] and glcontextmodes.[ch]. I'm also going to remove the DRI

Re: Moving towards a single driver binary for solo and DRI

2004-05-27 Thread Keith Whitwell
Jon Smirl wrote: --- Ian Romanick <[EMAIL PROTECTED]> wrote: I'm going to try and wrap up the remaining issues preventing a single driver binary. As part of that, I'm going to move the Mesa copies of dri_util.[ch] and glcontextmodes.[ch]. I'm also going to remove the DRI copies. Since dri_uti

Re: Moving towards a single driver binary for solo and DRI

2004-05-27 Thread Ian Romanick
Jon Smirl wrote: --- Ian Romanick <[EMAIL PROTECTED]> wrote: I'm going to try and wrap up the remaining issues preventing a single driver binary. As part of that, I'm going to move the Mesa copies of dri_util.[ch] and glcontextmodes.[ch]. I'm also going to remove the DRI copies. Since dri_uti

Re: Moving towards a single driver binary for solo and DRI

2004-05-27 Thread Jon Smirl
--- Ian Romanick <[EMAIL PROTECTED]> wrote: > I'm going to try and wrap up the remaining issues preventing a single > driver binary. As part of that, I'm going to move the Mesa copies of > dri_util.[ch] and glcontextmodes.[ch]. I'm also going to remove the DRI > copies. Since dri_util.[ch] ar

Moving towards a single driver binary for solo and DRI

2004-05-27 Thread Ian Romanick
I'm going to try and wrap up the remaining issues preventing a single driver binary. As part of that, I'm going to move the Mesa copies of dri_util.[ch] and glcontextmodes.[ch]. I'm also going to remove the DRI copies. Since dri_util.[ch] are only used by the drivers, I'm going to move them