Re: best way to access device driver functions

[Fawad Lateef <fawadlateef@gmail.com>]

On 9/15/05, Ivan Korzakow <ivan.korzakow@gmail.com> wrote:
> >
> > Adding ioctl in driver is not a good idea especially for 2.6.x series
> > kernel, rather use sysfs which is in kernel 2.6.x to support
> > user/kernel interaction too with other usage .....
> >
> 
> 
> Thanks for your answer. I started looking in sysfs and driver model.
> 
> Could you explain me why ioctl should be avoided ? Is it going to be
> deprecated in future kernel ?
> 

No ioctl are not deprecated, but they are just avoided b/c its not
good to mess kernel with new system-calls as there is a different way
for that !!!!

And for user/kernel interaction you have to look for sysfs/kobject and
don't need to go into the details of driver-model if you just need to
do user/kernel interaction and linux device driver 3rd edition's
chapter of driver-model will really help you in user/kernel
interaction (http://lwn.net/Kernel/ldd3/) ......  (for bi-directional
communication means kernel can also send messeges to user space you
can see netlink-sockets) .........


-- 
Fawad Lateef
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/