The dynamic extension code has made the radeon drivers
dependent on the GLX subsystem. I just imported the
current r200 driver into my version of the embedded
Mesa system. Embedded Mesa doesn't have a GLX
subsystem. Neither does DirectFB.
What do you think about reworking these functions to
depend on minimal new definitions in dri_util.h and
then add code at a higher level to map from GLX to the
dri based interface.
Here another case where I need to replace
__driCreateScreen with one that doesn't depend on X
headers.
#ifndef _SOLO
void *__driCreateScreen(Display *dpy, int scrn,
__DRIscreen *psc,
int numConfigs,
__GLXvisualConfig *config)
{
__DRIscreenPrivate *psp;
psp = __driUtilCreateScreen(dpy, scrn, psc,
numConfigs, config, &r200API);
return (void *) psp;
}
#else
void *__driCreateScreen(struct DRIDriverRec *driver,
struct DRIDriverContextRec
*driverContext)
{
__DRIscreenPrivate *psp;
psp = __driUtilCreateScreen(driver, driverContext,
&r200API);
return (void *) psp;
}
#endif
=====
Jon Smirl
[EMAIL PROTECTED]
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
