>For the remote, the patch works great. There is only one key not working, the ENTER key, and that may be a problem with the device rather than the driver. Great work!
>Is there anything else I can do?
Very well. As said before, each key must be reported via one of the reports from the descriptor. So if there is no raw event (and no trace output with enabled HID debug option) on pressing ENTER, I guess there is nothing to do. But in this case, the prepackaged SW also should be unable to support the ENTER key (sounds strange).
I am currently collecting reports from other 0419:0001 devices, as now there seem to be at least four devices with the same vendor/class id but different report descriptors. After collecting those, I might submit a merged patch to the kernel list. If you get some news on the ENTER key meanwhile, this would be worth to clarify.
>For the remote, the patch works great. There is only one key not working, the ENTER key, and that may be a problem with the device rather than the driver. Great work!
>Is there anything else I can do?
Very well. As said before, each key must be reported via one of the reports from the descriptor. So if there is no raw event (and no trace output with enabled HID debug option) on pressing ENTER, I guess there is nothing to do. But in this case, the prepackaged SW also should be unable to support the ENTER key (sounds strange).
I am currently collecting reports from other 0419:0001 devices, as now there seem to be at least four devices with the same vendor/class id but different report descriptors. After collecting those, I might submit a merged patch to the kernel list. If you get some news on the ENTER key meanwhile, this would be worth to clarify.