mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: linux-kernel@vger.kernel.org,
	Kristian H?gsberg <krh@bitplanet.net>, Olav Kongas <olav@enif.ee>
Subject: Re: input system: EVIOCSABS(abs) ioctl disabled, why?
Date: Sat, 31 Jul 2004 11:34:45 +0200	[thread overview]
Message-ID: <20040731093445.GB1579@ucw.cz> (raw)
In-Reply-To: <200407302354.25041.dtor_core@ameritech.net>

On Fri, Jul 30, 2004 at 11:54:25PM -0500, Dmitry Torokhov wrote:
> On Friday 30 July 2004 09:31 pm, 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?
> > 
> 
> I think you can use KDSKBLED/KDSETLED ioctls, but I agree that that evdev
> should also provide access to the same functions.
 
It does, see my previous e-mail.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

  reply	other threads:[~2004-07-31  9:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-28 12:41 Olav Kongas
2004-07-28 13:43 ` Vojtech Pavlik
2004-07-31  2:31   ` Kristian Høgsberg
2004-07-31  3:48     ` Lee Revell
2004-07-31  4:54     ` Dmitry Torokhov
2004-07-31  9:34       ` Vojtech Pavlik [this message]
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=20040731093445.GB1579@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=dtor_core@ameritech.net \
    --cc=krh@bitplanet.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olav@enif.ee \
    /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

all inboxes | Powered by JetHome®