Hi, On 18 August 2017 at 10:21, Daniel Vetter <daniel.vetter@xxxxxxxx> wrote: > +Recommended IOCTL Return Values > +=============================== > + > +In theory a driver's IOCTL callback is only allowed to return very few error > +codes. In practice it's good to abuse a few more. This section documents common > +practice within the DRM subsystem: > + > +ENOENT: > + Strictly speaking only when you try to open isn't there. There's a word from this sentence. > + We reuse that > + to signal any kind of object lookup failure, e.g. for unknown GEM buffer > + object handles, unknown KMS object handles and similar cases. > + > +ENOSPC: > + Some drivers use this to differiante 'differentiate' Cheers, Daniel _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
