Why my USB keyboard doesn't generate scancodes?

[Hans Petter Selasky]

On Sunday 27 January 2013 03:56:12 Yuri wrote:
> ---usbdump log---
> # usbdump -i usbus1 -s 160 -v
> 17:40:16.961544 usbus1.2 
> DONE-INTR-EP=00000082,SPD=FULL,NFR=1,SLEN=8,IVAL=1,ERR=0
>   frame[0] READ 5 bytes
>   0000  16 00 00 27 00 -- -- --  -- -- -- -- -- -- -- -- |...'.           |
> 17:40:16.961551 usbus1.2 SUBM-INTR-EP=00000082,SPD=FULL,NFR=1,SLEN=0,IVAL=1
>   frame[0] READ 10 bytes
> 17:40:17.113540 usbus1.2 
> DONE-INTR-EP=00000082,SPD=FULL,NFR=1,SLEN=8,IVAL=1,ERR=0
>   frame[0] READ 5 bytes
>   0000  16 00 00 00 00 -- -- --  -- -- -- -- -- -- -- -- |.....           |
> 17:40:17.113545 usbus1.2 SUBM-INTR-EP=00000082,SPD=FULL,NFR=1,SLEN=0,IVAL=1
>   frame[0] READ 10 bytes

Hi,

These messages should usually be 8 bytes long for keyboards. Probably you need 
to parse the HID descriptor to figure this out, which we currently don't do.

Maybe you can dump the HID descriptor of this device?

--HPS