ill the scancode table for a particular device.
>
> In the case of your remote, you'll likely will want to add support for those
> currently unknown scancodes.
>
> Those "unkonwn keypad keypress" type of messages are now obsolete, as users
> can get it anytime in user
Em Sun, 24 Feb 2013 21:19:30 +0100
Kevin Baradon escreveu:
> My 15c2:0036 device floods syslog when a keypad key is pressed:
>
> Feb 18 19:00:57 homeserver kernel: imon 5-1:1.0: imon_incoming_packet:
> unknown keypress, code 0x100fff2
> Feb 18 19:00:57 homeserver kernel: imon 5-1:1.0: imon_inco
Em Sun, 24 Feb 2013 21:19:30 +0100
Kevin Baradon escreveu:
> My 15c2:0036 device floods syslog when a keypad key is pressed:
>
> Feb 18 19:00:57 homeserver kernel: imon 5-1:1.0: imon_incoming_packet:
> unknown keypress, code 0x100fff2
> Feb 18 19:00:57 homeserver kernel: imon 5-1:1.0: imon_inco
My 15c2:0036 device floods syslog when a keypad key is pressed:
Feb 18 19:00:57 homeserver kernel: imon 5-1:1.0: imon_incoming_packet: unknown
keypress, code 0x100fff2
Feb 18 19:00:57 homeserver kernel: imon 5-1:1.0: imon_incoming_packet: unknown
keypress, code 0x100fef2
Feb 18 19:00:57 homeserv
4 matches
Mail list logo