On Aug 20, 07 19:51:31 +0300, Daniel Stone wrote: > On Mon, Aug 20, 2007 at 05:27:43PM +0200, Matthias Hopf wrote: > > On Aug 12, 07 17:50:12 +0200, [EMAIL PROTECTED] wrote: > > > On Thu, Aug 02, 2007 at 07:31:01PM +0200, Jerome Glisse wrote: > > > > There should be master (possibly one for each card) which be the only > > > > one being able to do this call: > > > > DRM_IOCTL_MODE_SETCRTC - set CRTC parameters > > > > Please be sure that if you design this using ioctls the design should be > > forward and backward compatible. > > > > AFAICS the only way to ensure this is some sort of tag-based parameter > > space (parameters are a list of tag,value pairs, terminated by a special > > tag). Otherwise you're stuck with one parameter list, which you cannot > > enhance easily, and version control both in user and kernel space will > > be a nightmare. With tags you can just ignore the tags you don't know > > about. > > Well, either that, or you can have a version field as the very first > member (think: X11 requests), or simply bump the ioctl number every time > you change the API (think: shared libraries).
But that exactly makes version control difficult (lots of cases, especially if the exact requirements aren't clear from day one). Without a version field, this is made impossible, something that must be avoided at all costs. Matthias -- Matthias Hopf <[EMAIL PROTECTED]> __ __ __ Maxfeldstr. 5 / 90409 Nuernberg (_ | | (_ |__ [EMAIL PROTECTED] Phone +49-911-74053-715 __) |_| __) |__ R & D www.mshopf.de ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
