Hi Luiz On Mon, Sep 17, 2012 at 12:46 PM, Luiz Augusto von Dentz <luiz.dentz@xxxxxxxxx> wrote: > HI Antonio, >> >> Reviewed-by: Antonio Ospite <ospite@xxxxxxxxxxxxxxxxx> >> >> I just did a syntax/style review, maybe I will take another look at the >> actual logic in the future to see if the report decoding procedure can >> be improved but for now I think it's OK, we want to have this driver in >> ASAP. >> >> David D. please bring up again the issue about missing keypresses on >> re-connection when sending the driver to linux-input with a full >> description of what you observed, I don't have a clue about these >> matters but people on linux-input might. > > I now have the remote, I tried using xinput test and most keys seems > to be working fine except the special buttons like subtitle, colors, > x, l1... Im not sure if they are not being mapped because they don't > have any representation or there is something wrong in the parser > itself (Bastien do they used to work for you?). Also got a problem on > suspend but I will have to reproduce it again to see if it is because > of the new driver or not. For debugging of input devices I recommend: http://cgit.freedesktop.org/evtest/tree/evtest.c Simply run it as ./evtest /dev/input/eventX And it shows you all events that are sent. You can use it to see whether the special-buttons are actually handled by the kernel. The suspend problems are Bluetooth-related. We never actually got that right. It's always the HIDP code that fails somewhere. Regards David -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
