From: Ivan Korzakow <ivan.korzakow@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: best way to access device driver functions
Date: Thu, 15 Sep 2005 09:48:50 +0200 [thread overview]
Message-ID: <a5986103050915004846d05841@mail.gmail.com> (raw)
Hi,
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,
Ivan
next reply other threads:[~2005-09-15 7:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-15 7:48 Ivan Korzakow [this message]
2005-09-15 8:03 ` best way to access device driver functions Fawad Lateef
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=a5986103050915004846d05841@mail.gmail.com \
--to=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