From: Nuno Santos <nsantos@edigma.com>
To: linux-input@vger.kernel.org
Subject: Re: Interacting with a input kernel driver from user space
Date: Tue, 15 Nov 2011 09:41:40 +0000 [thread overview]
Message-ID: <4EC233D4.1060302@edigma.com> (raw)
In-Reply-To: <201111141534.49608.dmitry.torokhov@gmail.com>
On 11/14/2011 11:34 PM, Dmitry Torokhov wrote:
> On Monday, November 14, 2011 03:17:17 PM Oliver Neukum wrote:
>> Am Montag, 14. November 2011, 19:57:41 schrieb Dmitry Torokhov:
>>> On Monday, November 14, 2011 10:24:17 AM Nuno Santos wrote:
>>>> Hi,
>>>>
>>>> I have defined my first attribute in the following way:
>>>>
>>>> static ssize_t usbtouchscreen_update_sensibility(struct device *dev,
>>>>
>>>> struct device_attribute
>>>> *attr, const char *buf,
>>>> size_t count)
>>>>
>>>> {
>>>>
>>>> printk(KERN_INFO "update sensibility called");
>>> Updating sensibility is always a good thing but I gather you mean
>>> sensitivity here...
>>>
>>> BTW this should probably be a per-user setting and belong to the X
>>> driver, not kernel driver. I.e. kernel streams all data and userspace
>>> (X) decides what data do discard according to current user
>>> preferences.
>> Hi,
>>
>> before we define yet another interface specific to a driver, could we
>> discuss whether this interface could be applicable to a wider range of
>> devices?
> ... and whether it should be a kernel userspace at all...
>
Well, I can't really tell what it should because i'm little aware of all
the possibilities provided by the linux OS.
I'm a not a specialist in any OS. However, i'm a daily user of all the
main operating systems Mac, Windows and Linux.
As a kernel developer I have only developed the device driver for
Windows 7 and now i'm writing it to Linux.
Thanks,
Nuno
next prev parent reply other threads:[~2011-11-15 9:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 12:24 Interacting with a input kernel driver from user space Nuno Santos
2011-11-14 15:37 ` David Herrmann
2011-11-14 16:00 ` Nuno Santos
2011-11-14 16:09 ` David Herrmann
2011-11-14 16:31 ` Nuno Santos
2011-11-14 16:58 ` David Herrmann
2011-11-14 18:24 ` Nuno Santos
2011-11-14 18:57 ` Dmitry Torokhov
2011-11-14 23:17 ` Oliver Neukum
2011-11-14 23:34 ` Dmitry Torokhov
2011-11-15 9:41 ` Nuno Santos [this message]
2011-11-15 9:38 ` Nuno Santos
2011-11-15 9:35 ` Nuno Santos
2011-11-15 18:23 ` Dmitry Torokhov
2011-11-15 18:41 ` Nuno Santos
2011-11-15 19:20 ` Dmitry Torokhov
2011-11-14 17:13 ` Dmitry Torokhov
2011-11-15 10:32 ` Henrik Rydberg
2011-11-15 10:40 ` Nuno Santos
2011-11-15 19:07 ` Chase Douglas
2011-11-16 10:25 ` Nuno Santos
2011-11-16 10:28 ` Nuno Santos
2011-11-16 17:28 ` Nuno Santos
2011-11-16 19:27 ` Dmitry Torokhov
2011-11-17 15:39 ` Nuno Santos
2011-11-17 16:58 ` Nuno Santos
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=4EC233D4.1060302@edigma.com \
--to=nsantos@edigma.com \
--cc=linux-input@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.