From: Lee Revell <rlrevell@joe-job.com>
To: "Kristian Høgsberg" <krh@bitplanet.net>
Cc: Vojtech Pavlik <vojtech@suse.cz>, Olav Kongas <olav@enif.ee>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: input system: EVIOCSABS(abs) ioctl disabled, why?
Date: Fri, 30 Jul 2004 23:48:53 -0400 [thread overview]
Message-ID: <1091245732.1677.56.camel@mindpipe> (raw)
In-Reply-To: <410B0486.6060706@bitplanet.net>
On Fri, 2004-07-30 at 22:31, Kristian Høgsberg wrote:
> Vojtech Pavlik wrote:
> > On Wed, Jul 28, 2004 at 03:41:28PM +0300, Olav Kongas wrote:
> >
> >
> >>When trying to feed calibration information to a touchscreen driver with
> >>the EVIOCSABS(abs) ioctl command, I noticed that this command is disabled
> >>in 2.6.7. Only after the modification given in the patch below it was
> >>possible to use this ioctl command.
> >>
> >>Why is the EVIOCSABS command disabled? I cannot imagine that nobody uses
> >
> >
> > It's a bug. I'll fix it.
>
> On a related note - shouldn't there also be a EVIOCSLED, or am I missing
> something obvious? How do you set keyboard LEDs?
>
Interesting you should mention keyboard LEDs. Here is a patch that was
recently posted to replace the old, broken method of setting keyboard
lights (issue a command an busy-wait until you get an ACK) with an
improved one (using work queues and a semaphore). It does not really
answer your question as such, but should be a good place to start.
http://lkml.org/lkml/2004/7/27/252
HTH,
Lee
next prev parent reply other threads:[~2004-07-31 3:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-28 12:41 input system: EVIOCSABS(abs) ioctl disabled, why? Olav Kongas
2004-07-28 13:43 ` Vojtech Pavlik
2004-07-31 2:31 ` Kristian Høgsberg
2004-07-31 3:48 ` Lee Revell [this message]
2004-07-31 4:54 ` Dmitry Torokhov
2004-07-31 9:34 ` Vojtech Pavlik
2004-07-31 9:33 ` Vojtech Pavlik
2004-07-31 15:21 ` Kristian Høgsberg
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=1091245732.1677.56.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=krh@bitplanet.net \
--cc=linux-kernel@vger.kernel.org \
--cc=olav@enif.ee \
--cc=vojtech@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).