On Sun, 16 Feb 2003, Philip Brown wrote:

> On Sun, Feb 16, 2003 at 05:55:55PM -0600, D. Hageman wrote:
> > > So, why not do it by PCI vendor/devid ? That sort of information is visible
> > > from the DRI level, I believe. I think its just another Xserver internal
> > > call, isnt it?  
> > 
> > I thought about PCI vendors/devid ... problem with that is that we would 
> > like to have a sane configuration for a normal user.  I think using that 
> > would be too confusing for the user.  If we use the identifier that is 
> > specified in the XF86Config I think it would be the most logical route - 
> > don't you think?
> 
> What's your definition of "sane configuration" ?
> 
> Nothing is stopping you from using the PCI ids as the *actual* tagging
> mechanism, but perhaps using the xfree86 card name as a comment to
> help the user out a bit.
> 
> IMO, that extra "config comment" stuff should be handled at user-level.
> Keep that sort of stuff out of the kernel.

This won't go into the kernel.  This will go into the driver that 
gets loaded by Mesa that communicates to the module that gets loaded up 
into the kernel.  

You can find the source for these drivers in:

xc/lib/GL/mesa/src/drv/

You can see what current config options exist by doing:

grep -r getenv *

I really do appreciate your comments and feedback, but please ask 
questions if you are unsure of certain aspects of the problem.  

-- 
//========================================================\\
||  D. Hageman                    <[EMAIL PROTECTED]>  ||
\\========================================================//


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to