On Wed, 2003-10-22 at 13:59, Michel Dänzer wrote: > On Wed, 2003-10-22 at 04:56, Eric Anholt wrote: > > - What should the DRM do if the minor number for either DI or DD > > interface is greater than the DRM knows about? > > Return DRM_ERR( EINVAL ) ?
Okay, that's what it's doing. > > - Do we want to put some reserved fields in the SET_VERSION ioctl in > > case we want to extend it in some manner in the future? > > The versioning could be used to extend it? :) That would be messy, unfortunately, on BSD at least. The ioctl handler checks that the data size the user specified and that got copied in by the kernel matches the size the kernel expects. Actually, I suppose it would be doable, by marking the specific ioctl as expecting the smaller of the two sizes, making the size check be usersize >= kerenelexpectedsize, and then the specific ioctl handler would special-case the larger size. So I guess as long as there's no real expectation of needing to extend it, it can be ignored. > > - Should the libdri minor version be bumped for the new > > DRICreatePCIBusID function? > > I think so. > > > Is using xf86LoaderCheckSymbol the way to see if it's available, > > That or the minor version I guess, whichever is more convenient. > > > and does it need to be in the symbol lists for the drivers? > > Yes, or it will probably be reported as unresolved when the dri module > isn't loaded. Okay, I'll do these. -- Eric Anholt [EMAIL PROTECTED] http://people.freebsd.org/~anholt/ [EMAIL PROTECTED] ------------------------------------------------------- This SF.net email is sponsored by OSDN developer relations Here's your chance to show off your extensive product knowledge We want to know what you know. Tell us and you have a chance to win $100 http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54 _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
