Re: best way to access device driver functions

> 
> 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 ?

Regards,

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

---

• Follow-Ups:
  • Re: best way to access device driver functions
    • From: Fawad Lateef <[email protected]>

• References:
  • best way to access device driver functions
    • From: Ivan Korzakow <[email protected]>
  • Re: best way to access device driver functions
    • From: Fawad Lateef <[email protected]>

• Prev by Date: kernel networking - sys_socketcall() problem
• Next by Date: Re: PCI driver
• Previous by thread: Re: best way to access device driver functions
• Next by thread: Re: best way to access device driver functions
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]