-----BEGIN PGP SIGNED MESSAGE----- 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. https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01816.html ''...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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmArFAACgkQOjLpvpq7dMq5HACfYDW4AhJYcv4pSgb7UB6oQrcD LjMAn1BWxRMZoNKDxjMupFNVtsVhg+SM =Zcl5 -----END PGP SIGNATURE-----
