Hi Karl,
I don't know but as documented by usbsnoop log the value written from
kernel driver make my device to fail.
Windows driver after some assumption write back the original value (0xc3)
Regards,
Eddi
On Sun, Feb 8, 2015 at 2:54 AM, Karl Palsson ka...@tweak.net.au wrote:
My work in
Eddi De Pieri e...@depieri.net wrote:
Hi Karl,
I don't know but as documented by usbsnoop log the value written from
kernel driver make my device to fail.
Windows driver after some assumption write back the original value
(0xc3)
Ok,
I'm still progressing on more of that init code,
My work in
Eddi De Pieri e...@depieri.net wrote:
Bus 003 Device 014: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial
adapter
ch431 kernel driver don't work correctly with this device,
when URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER answer/send wrong character
After some experiment by
Hi list,
I've got recently following device.
Bus 003 Device 014: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
ch431 kernel driver don't work correctly with this device,
when URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER answer/send wrong character
After some experiment by passing