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 13:03:10 +0500	[thread overview]
Message-ID: <1e62d137050915010361d10139@mail.gmail.com> (raw)
In-Reply-To: <a5986103050915004846d05841@mail.gmail.com>

On 9/15/05, Ivan Korzakow <ivan.korzakow@gmail.com> wrote:

> I have a number of functions that used to drive a device on an embedded
> system. Now that we are moving to Linux, these functions are part of the
> kernel space. My question is : what is the best way to access these
> from user space ?
> With a device driver, is it not a problem to implement about 15 commands through
> ioctl in addition to the usual open, close, read write ? It seems a bit
> awkward ...
> 
> Any advice on this will help a lot. Thanks in advance,
> 

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


-- 
Fawad Lateef

  reply	other threads:[~2005-09-15  8:03 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 [this message]
2005-09-15 12:18   ` Ivan Korzakow
2005-09-15 15:39     ` Fawad Lateef
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=1e62d137050915010361d10139@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