On Sat, Jan 25, 2003 at 10:25:56PM +0100, Benjamin Herrenschmidt wrote:
quoted
quoted
quoted
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.
Also, I don't like the sysctl's as those need
allocating sysctl numbers, which are always a problem. In 2.5,
we could have these in sysfs, though for 2.4 I'm not sure what
to do.
I don't think you can do much better than sysctl or module parameters in 2.4.
--
Vojtech Pavlik
SuSE Labs
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
On Saturday 25 January 2003 22:29, Vojtech Pavlik wrote:
On Sat, Jan 25, 2003 at 10:25:56PM +0100, Benjamin Herrenschmidt wrote:
quoted
quoted
quoted
quoted
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/