On Tue, Nov 04, 2003 at 01:08:28PM -0800, Eric Anholt wrote: > On Tue, 2003-11-04 at 12:25, Otto Solares wrote: > > On Mon, Nov 03, 2003 at 09:09:58PM -0800, Jon Smirl wrote: > > > I currently have this info tacked onto the end of the statistics IOCTL (in > > > order to conserve IOCTL numbers) but there should be a better way to do it. > > > > while you are on it, can you check why DRM_IOCTL_SET_UNIQUE ioctl does need root > > privileges, it is more useful if access permissions could be managed via the > > filesystem (eg. /dev/dri/cardX). > > You shouldn't use SET_UNIQUE any more. Do SET_VERSION to 1.1 and then > get the unique (the busid).
The software i am wroting uses DRI from standalone Mesa, it works nicely, the only problem i have found is that DRI initialization stops if you are not root and the faulty code is in the r200 driver when SET_UNIQUE ioctl is called. Input, fbdev, sound, dri (via /dev/dri/cardX) all works nicely using filesystem permissions, so it could be really cool if that ioctl "does the right thing (tm)". -solca ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
