Re: [PATCH] HID: core: assign usbhid to handle EETI PID=0x0001 HID device

Hi, On 2017-08-22 11:33, Benjamin Tissoires wrote: On Aug 11 2017 or thereabouts, JamChen wrote: From: Jam Chen The vendor used the same PID(0x0001) for multiple touch IC controllers. The newer ICs can support HID class and report the multitouch collection in the

Re: [PATCH] HID: core: assign usbhid to handle EETI PID=0x0001 HID device

Hi, On 2017-08-22 11:33, Benjamin Tissoires wrote: On Aug 11 2017 or thereabouts, JamChen wrote: From: Jam Chen The vendor used the same PID(0x0001) for multiple touch IC controllers. The newer ICs can support HID class and report the multitouch collection in the descriptor. So they were

Re: [PATCH] HID: core: assign usbhid to handle EETI PID=0x0001 HID device

On Aug 11 2017 or thereabouts, JamChen wrote: > From: Jam Chen > > The vendor used the same PID(0x0001) for multiple touch IC controllers. > The newer ICs can support HID class and report the multitouch collection > in the descriptor. So they were handled by the

Re: [PATCH] HID: core: assign usbhid to handle EETI PID=0x0001 HID device

On Aug 11 2017 or thereabouts, JamChen wrote: > From: Jam Chen > > The vendor used the same PID(0x0001) for multiple touch IC controllers. > The newer ICs can support HID class and report the multitouch collection > in the descriptor. So they were handled by the hid-multitouch driver. > But some

Re: [PATCH] HID: core: assign usbhid to handle EETI PID=0x0001 HID device

Hi, it's a funny thing. Currently I can't reproduce the problem. This was the situation that occurred previously: At the first touch after X started, the pointer went to the correct location. Moving the finger made the pointer move with the finger, the pointer location was always good. Then

Re: [PATCH] HID: core: assign usbhid to handle EETI PID=0x0001 HID device

Hi, it's a funny thing. Currently I can't reproduce the problem. This was the situation that occurred previously: At the first touch after X started, the pointer went to the correct location. Moving the finger made the pointer move with the finger, the pointer location was always good. Then

[PATCH] HID: core: assign usbhid to handle EETI PID=0x0001 HID device

From: Jam Chen The vendor used the same PID(0x0001) for multiple touch IC controllers. The newer ICs can support HID class and report the multitouch collection in the descriptor. So they were handled by the hid-multitouch driver. But some customized firmwares don't

[PATCH] HID: core: assign usbhid to handle EETI PID=0x0001 HID device

From: Jam Chen The vendor used the same PID(0x0001) for multiple touch IC controllers. The newer ICs can support HID class and report the multitouch collection in the descriptor. So they were handled by the hid-multitouch driver. But some customized firmwares don't support multitouch protocol