[PATCH 0/3] Make the touchscreen filtering optional.

Andy Green andy at openmoko.com
Wed Jan 28 20:04:48 CET 2009

Hash: SHA1

Somebody in the thread at some point said:
| Cool thanks!
| The thing is, we would need to allow a dynamic configuration of the
| filter chain,
| but I guess this is out of scope!?  However, I'm still wondering why
we need

If you want to improve that, feel free to send a patch.

| those fancy filters in the kernel... What can we do here, that can't
be done in
| userspace? Please also keep in mind, that someone needs to maintain this
| stuff, even if it goes upstream.

Why service hardware requirements based off an ISR in userspace when it
can be decimated inside the ISR?  It's that which seems ass-backwards.

I read an interesting post on fedora-devel the other day about their
take on this issue.


''...our current long-term approach is to get support for input devices
into the kernel and then let evdev deal with it automagically*. The
times when X needed a separate driver for each device are gone and the
sooner we forget about it, the happier we'll be....''

- -Andy
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org


More information about the openmoko-kernel mailing list