D. Hageman wrote:
What would we use as the device key, then? Would this match the device's name from the XF86Config file? There are a few odd corner cases that we need to make sure and get right the first time. User's changing cards and multi-head cards (even though we don't support direct rendering on them now) are the two big ones that I can think of.On Tue, 28 Jan 2003, Ian Romanick wrote:How do we want to handle the case where a user changes video cards? Some of the parameters are likely to be generic, but a lot will be very device specific. The issue here is that the set of available parameters will change. A releated issue is when the set of availble parameters change from one driver release to another. So, do we want to key options on hardware device, screen (in the X sense), or something else? The answer to this question will likely dictate how we handle multi-head.The more I play around with this in my head the more I lean towards keying to the device. The screen is a very generic term and it is supposed to be that way for the abstraction of X11 to work. It however does not lend itself to specific driver tweaking ... hence why the option parameters go in the "Device" section.
I'm coming to conclusion more the more I think about it. I really can't come up with a good, real-world case to argue for application-then-device. Most of the cases where you'd want the application at the top level could be handled by putting a '<device id="*">' around it.I think we're going to end up with two keys. One is the application (with a default available) and the other will be something to identify the device and/or screen. How do we want to specify them? By this I mean, do we want to select the application then the screen (like you suggest above) or the other way around?In all honesty I threw out my example to start some discussion. Not too much thought had went into it. I saw a couple let us see a schema posts so I thought I would see what happen if I posted one. I think the real
way it should be done is device, then application.
<device id="0">
<application name="...
...
</application>
<application name="...
...
</application>
</device>
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
