--- Eric Anholt <[EMAIL PROTECTED]> wrote: > If the Linux drivers go to probing PCI IDs, could it also start creating > /dev/dri/cardXs which are associated with a specific piece of hardware? > The get/set unique thing is a problem, though. It seems to me that we > ought to have /dev/dri/cardX start with a unique value reporting > sufficient information to identify it. A new server would do getuniques > on the /dev/dri/cardXs until it found one matching the hardware it was > trying to use the drm for. If an old server does a setunique, then it > overrides what the kernel had, and at some unspecified time in the > future we could deprecate that interface. This eliminates the need for > a separate get_suggested_unique ioctl. > This was the first way I coded it. But when you specificy a driver name in xconfig and no BUSID, xfree uses drmOpenByName(). OpenByName searches the drivers for the driver name and a bank unique id, then sets it. Since the only driver with the right driver name already has the unique id filled in, Xfree fails to load. To fix this you would have to change the existing binaries.
===== 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
