From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Niko Rosvall <niko@fograven.net>
Cc: Christoph Fritz <chf.fritz@googlemail.com>,
Linux input <linux-input@vger.kernel.org>
Subject: Re: Reading keys
Date: Mon, 10 May 2010 13:48:44 -0700 [thread overview]
Message-ID: <20100510204843.GA30878@core.coreip.homeip.net> (raw)
In-Reply-To: <1273521263.2199.17.camel@localhost>
On Mon, May 10, 2010 at 10:54:23PM +0300, Niko Rosvall wrote:
> On Mon, 2010-05-10 at 18:55 +0200, Christoph Fritz wrote:
> > On Mon, 2010-05-10 at 19:01 +0300, Niko Rosvall wrote:
> > > Hi All,
> > >
> > > I'm new to Linux kernel and actually subscribed to this list today.
> > > So, i'm not even sure is this the right place to ask this, but:
> > >
> > > I want to make a kernel module which detects a keypress and then
> > > disables it. E.g someone presses F1 and my module would just "eat" it.
> >
> > Interesting usecase, is it for a kiosk? And why don't you disable the
> > keys in X or your application?
> >
> > > Any examples and/or hints where to start? Some nice, small peace of code
> > > would be very very nice.
> >
> > You could hack input_event() in drivers/input/input.c
> >
> > Thanks,
> > Christoph
>
> No, not for a kiosk or anything. Basically I'm just having fun here and
> trying to do a module which would disable caps lock key completely.
>
> Of course I can do that using xmodmap, but where's the fun then? ;)
>
> I did modify input.c (didn't test it yet thought), but what I really
> want is just a simple module so I can load and unload it when I want.
>
You need to define "filter" input handler - one that implements filter()
instead of event(). This requires recent kernel though.
--
Dmitry
prev parent reply other threads:[~2010-05-10 20:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 16:01 Reading keys Niko Rosvall
2010-05-10 16:55 ` Christoph Fritz
2010-05-10 19:54 ` Niko Rosvall
2010-05-10 20:48 ` Dmitry Torokhov [this message]
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=20100510204843.GA30878@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=chf.fritz@googlemail.com \
--cc=linux-input@vger.kernel.org \
--cc=niko@fograven.net \
/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).