Standalone Mesa doesn't have the Xfree code for walking the PCI bus so the
simplest way for me to find the hardware is to make the DRI drivers aware of
the OS's PCI probing support. I've already have PCI probing support added to
all of the DRI drivers, but I need to come up with an API that won't break
existing Xfree binaries.

My first attempt was to make DRM_IOCTL_GET_UNIQUE be already filled out with
the hardware name. But this doesn't work since apps check to see if UNIQUE is
null before assigning a device. I would have though that they would also check
to see if it was equal to the device they were looking for.

Would it be better to add a new IOCTL like GET_SUGGESTED_UNIQUE? This would
allow Xfree to continue as is, and standalone Mesa would get the suggested ID
and then store it back with SET_UNIQUE.

I was hoping to do this without adding another IOCTL but I can't seem to come
up with a scheme that works.

=====
Jon Smirl
[EMAIL PROTECTED]

__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to