On Wed, 2004-04-21 at 04:17, Adam Jackson wrote:
> On Monday 19 April 2004 20:08, Michel DÃnzer wrote:
> > On Tue, 2004-04-20 at 02:13, ajax wrote:
> > > All drivers except savage emit the "Direct rendering disabled" message as
> > > an informational message; savage makes it an error. Technically it's not
> > > an error, since the server can continue, but it should probably be at
> > > least a warning. This would make troubleshooting easier, because users
> > > know to look for lines with a (WW) or (EE) on them.
> > >
> > > Attached patch makes this message a warning across all drivers.
> >
> > IMHO it should only be a warning if it was intended to be enabled in the
> > first place.
>
> I tend to agree. I don't think there's any list of requested modules
> maintained anywhere. tdfx does xf86LoaderCheckSymbol("DRIQueryVersion") to
> see if libdri.a loaded though, which is probably good enough; if the check
> fails the message can be degraded to an X_INFO. Sound reasonable?
I think so. But, while you're at it... the drivers need an option to
enable/disable the DRI, otherwise there's no way to control which
card(s) to enable it on in a multi-card setup.
--
Earthling Michel DÃnzer | Debian (powerpc), X and DRI developer
Libre software enthusiast | http://svcs.affero.net/rm.php?r=daenzer
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
--
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
