public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Fawad Lateef <fawadlateef@gmail.com>
To: ivan.korzakow@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: best way to access device driver functions
Date: Thu, 15 Sep 2005 20:39:23 +0500	[thread overview]
Message-ID: <1e62d13705091508391832f897@mail.gmail.com> (raw)
In-Reply-To: <a598610305091505184a8aa8fd@mail.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

  reply	other threads:[~2005-09-15 15:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-15  7:48 best way to access device driver functions Ivan Korzakow
2005-09-15  8:03 ` Fawad Lateef
2005-09-15 12:18   ` Ivan Korzakow
2005-09-15 15:39     ` Fawad Lateef [this message]
2005-09-16 12:59       ` Nix
2005-09-16 14:07         ` Arjan van de Ven
2005-09-16 15:24           ` Nix
2005-09-16 16:02             ` linux-os (Dick Johnson)
2005-09-16 18:30               ` Kyle Moffett
2005-09-16 19:20                 ` linux-os (Dick Johnson)
2005-09-16 19:41                   ` Valdis.Kletnieks
2005-09-16 17:52         ` Alexey Dobriyan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1e62d13705091508391832f897@mail.gmail.com \
    --to=fawadlateef@gmail.com \
    --cc=ivan.korzakow@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox