On Feb 8, 2008 2:28 AM, Robert P. J. Day <[EMAIL PROTECTED]> wrote:

> see?  total freedom in terms of how you interpret the values, which is
> why ioctl() calls are actually deprecated these days -- they're just
> too unstructured, and are being phased out in terms of /proc or sysfs
> entries.  but there's obviously a lot of them still in the kernel.
>

They are being phased out? You mean they may not be supported in future
kernel versions?
And is the alternative to ioctl()s, reading/writing to special /proc or
/sysfs entries? Is that faster/slower than ioctl()s, or just cleaner.

Thanks for all your replies.
-Mayank

Reply via email to