On Mon, Jun 08, 2009 at 07:39:43PM +0200, Luca Capello wrote: > Should I go directly with the above one or do you think that the headset > button behavior will be fixed soon? I would prefer to wait for that, it > this means a short time...
At the xev level I don't mind. At the /dev/input level, it is quite
weird that a button is reported pressed when it's not, and vice-versa.
My gut feeling is that the input driver should report it "properly"
("pressed" when it is pressed) and then whatever generates xev events
can choose to reverse it.
However, this is just my gut feeling: I understand that there can be
reasons to do otherwise that I just do not know. In the end, either way
it can be made to work, so I could even say that I personally do not
know enough to care.
Ciao,
Enrico
--
GPG key: 4096R/E7AD5568 2009-05-08 Enrico Zini <enr...@enricozini.org>
signature.asc
Description: Digital signature
_______________________________________________ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
