[lkml]   [2001]   [May]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
On Sat, 12 May 2001, Alan Cox wrote:
> > Can somebody explain the use of ENOIOCTLCMD? There are order of 170
> > uses in the kernel, but I don't see any guidelines for that use (nor
> > what prevents it from being seen by user programs).
> It should never be seen by apps. If it can be then it is wrong code.
> Basically you use it in things like
> int err = dev->ioctlfunc(dev, op, arg);
> if( err != -ENOIOCTLCMD)
> return err;
> /* Driver specific code does not support this ioctl */
> switch(op)
> {
> ...
> default:
> return -ENOTTY;
> }
> Its a way of passing back 'you handle it'

Okay, but another way of looking at it is as an instance of the classic

Husband: What have I done wrong this time?
Wife: If you don't know, I'm not going to tell you!

IOW instead of getting back "this file doesn't know what that IOCTL
means", you get "error somewhere". It certainly would be nice to know
*which* parameter was invalid and *why* it was invalid. Changing this
would be against the lore, but I would rather throw away excess
information than never have received it in the first place. *sigh*

Mark H. Wood, Lead System Programmer mwood@IUPUI.Edu
Make a good day.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:52    [W:0.071 / U:7.068 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site