Re: Still Problems with USB Remote control

Dear Jiri,

I have got new news. I was able to play with my remote again.

> This should only happen once per report, at the time that all fields from 
> the received report have been parsed and passed to the input driver as 
> EV_KEY (or anything else, according to the existing mapping in hid-input).
> 
> For every field received in report, the callchain is hid_input_report() ->
> hid_input_field() -> hid_process_event() -> hidinput_hid_event() -> 
> input_event() with values obtained by parsing the field in received 
> report.
> 
> After all the fields have been passed through input_event(), input_sync() 
> is called from hid_input_report() -> hidinput_report_event(), which is OK 
> - at that time, all the received fields should have already been passed to

I understand. First all the fields in the report is compiled and everything
is ready, it is submitted to the kernel, so finally the user realized an effect. Can a report consist of many events ?

> I still don't fully understand where do the events get lost in your case. 
> One possibility is that the machine is having a broken report descriptor, 
> resulting in the fields in received reports not being parsed correctly 
> (this wouldn't really be the first case of such a broken device). 
> 
>
 
> This is fine, but a bit more of messages would be needed, namely:
> 
> - report descriptor dump. This gets printed (in debug mode) upon the 
>   device connection. The dump should basically resemble 
> 
>   drivers/usb/input/hid-core.c: report descriptor (size 59, read 59) = 05 
>   01 09 06 a1 01 05 07 19 e0 29 e7 15 00 25 01 75 01 95 08 81 02 81 03 95 
>   05 05 08 19 01 29 05 91 02 95 01 75 03 91 01 95 06 75 08 15 00 26 a4 00 
>   05 07 19 00 2a a4 00 81 00 c0

Yes, I have exactly got such output. I found it in the log
Its attached to this mail. ITs called "dump"
> 
> - hid-input mapping. The respective dump should resemble
> 
>    INPUT[INPUT]
>      Field(0)
>        Usage(8)
>          Keyboard.00e0
>          Keyboard.00e1
>          Keyboard.00e2
> ... etc, then mapping dump, such as 
> Mapping: Keyboard.00e1 ---> Key.LeftShift
> Mapping: Keyboard.00e2 ---> Key.LeftAlt
> Mapping: Keyboard.00e3 ---> Key.LeftMeta
> ... etc should follow

This is also contained in "dump" but just that the mapping is IGNORED.
the line "Input[Input" I was not even able to find in the kernel code.
I hope It does not matter.

I have got the feeling, that my remote control is not implemented at all in linux, and it has to be done. So I started writing down the bytes which are
sent from the remote control. Its attached to the mail 'codes'

If its really new, I also like to contribute some work for kernel coding.
Maybe this is my chance. But my problem is that I dont have enough insight
into hid at the moment.



Can you tell me how to best proceed ?

nice greets from zuerich
-- 
"Feel free" - 5 GB Mailbox, 50 FreeSMS/Monat ...
Jetzt GMX ProMail testen: www.gmx.net/de/go/mailfooter/promail-out

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel