From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
To: Vojtech Pavlik <vojtech@suse.cz>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Vojtech Pavlik <vojtech@suse.cz>,
Till Straumann <Till.Straumann@TU-Berlin.de>,
linuxppc-dev@lists.linuxppc.org, George Staikos <staikos@kde.org>
Subject: Re: [patch] ignore trackpad/mouse while typing
Date: Mon, 27 Jan 2003 20:16:24 +0100 [thread overview]
Message-ID: <200301272016.25024@enzo.bigblue.local> (raw)
In-Reply-To: <20030125222902.A18919@ucw.cz>
On Saturday 25 January 2003 22:29, Vojtech Pavlik wrote:
> On Sat, Jan 25, 2003 at 10:25:56PM +0100, Benjamin Herrenschmidt wrote:
> > > > > Well... the problem happpens in console as well, and with other
> > > > > non-X apps like MacOnLinux. Some Apple PowerBooks have
> > > > > over-sensitive trackpad. Apple themselves implement a similar
> > > > > mecanism in the kernel driver of OS X.
> > > >
> > > > Mine is one of those machines. I have to turn off gpm for sure,
> > > > and X is quite oversensitive too (tuned it in KDE, but still this
> > > > functionality would be very nice).
> > >
> > > How about implementing it in mousedev.c?
> >
> > Right, though it would need hooks in kbddev or something to know
> > about keystrokes.
>
> It could accept keyboards as an event source for this purpose. I'd like
> to keep this out of the input core.
Hmm, this reminds me of one feature I would need in the input core to support
1-button mices in userspace (or at least in a totally self-contained module),
namely the ability to register "filters" that are called early in
input_event() and where a return value !=0 lets it return immediately from
input_event() without processing the event.
Eg. something along these lines:
ret = 0;
list_for_each_entry(filter, &dev->f_list, d_node)
if (filter->open)
ret |= filter->handler->event(handle, type, code,
value);
if (ret) return;
Comments?
Franz.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-01-27 19:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-29 1:34 [patch] ignore trackpad/mouse while typing Till Straumann
2002-11-29 5:31 ` Ethan Benson
2002-12-03 1:47 ` Michel Dänzer
2002-12-03 5:03 ` Till Straumann
2003-01-25 17:47 ` Vojtech Pavlik
2003-01-25 19:04 ` Benjamin Herrenschmidt
2003-01-25 20:58 ` George Staikos
2003-01-25 21:04 ` Vojtech Pavlik
2003-01-25 21:25 ` Benjamin Herrenschmidt
2003-01-25 18:04 ` Till Straumann
2003-01-26 9:59 ` Vojtech Pavlik
2003-01-25 21:29 ` Vojtech Pavlik
2003-01-27 19:16 ` Franz Sirl [this message]
2003-01-27 19:25 ` Vojtech Pavlik
2003-01-27 21:33 ` Till Straumann
2003-01-27 21:49 ` Franz Sirl
2003-01-27 22:00 ` Vojtech Pavlik
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=200301272016.25024@enzo.bigblue.local \
--to=franz.sirl-kernel@lauterbach.com \
--cc=Till.Straumann@TU-Berlin.de \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=staikos@kde.org \
--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 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.