* USB: serial: pl2303: add Delock Infrared device id
@ 2019-02-09 8:48 ebrahim
0 siblings, 0 replies; 8+ messages in thread
From: ebrahim @ 2019-02-09 8:48 UTC (permalink / raw)
To: linux-usb; +Cc: Ebrahim Byagowi
From: Ebrahim Byagowi <ebrahim@gnu.org>
This makes Delock Infrared adapter to work as a USB to Serial device.
---
drivers/usb/serial/pl2303.c | 1 +
drivers/usb/serial/pl2303.h | 3 +++
2 files changed, 4 insertions(+)
diff --git a/drivers/usb/serial/pl2303.c b/drivers/usb/serial/pl2303.c
index 98e7a5df0..d5ec72575 100644
--- a/drivers/usb/serial/pl2303.c
+++ b/drivers/usb/serial/pl2303.c
@@ -105,6 +105,7 @@ static const struct usb_device_id id_table[] = {
{ USB_DEVICE(SANWA_VENDOR_ID, SANWA_PRODUCT_ID) },
{ USB_DEVICE(ADLINK_VENDOR_ID, ADLINK_ND6530_PRODUCT_ID) },
{ USB_DEVICE(SMART_VENDOR_ID, SMART_PRODUCT_ID) },
+ { USB_DEVICE(DELOCK_VENDOR_ID, DELOCK_PRODUCT_ID) },
{ } /* Terminating entry */
};
diff --git a/drivers/usb/serial/pl2303.h b/drivers/usb/serial/pl2303.h
index 4e2554d55..01936de13 100644
--- a/drivers/usb/serial/pl2303.h
+++ b/drivers/usb/serial/pl2303.h
@@ -153,3 +153,6 @@
#define SMART_VENDOR_ID 0x0b8c
#define SMART_PRODUCT_ID 0x2303
+/* Delock Infrared Adapter */
+#define DELOCK_VENDOR_ID 0x1685
+#define DELOCK_PRODUCT_ID 0x2000
^ permalink raw reply related [flat|nested] 8+ messages in thread
* USB: serial: pl2303: add Delock Infrared device id
@ 2019-02-09 9:08 Greg Kroah-Hartman
0 siblings, 0 replies; 8+ messages in thread
From: Greg Kroah-Hartman @ 2019-02-09 9:08 UTC (permalink / raw)
To: ebrahim; +Cc: linux-usb
On Sat, Feb 09, 2019 at 12:18:40PM +0330, ebrahim@gnu.org wrote:
> From: Ebrahim Byagowi <ebrahim@gnu.org>
>
> This makes Delock Infrared adapter to work as a USB to Serial device.
> ---
> drivers/usb/serial/pl2303.c | 1 +
> drivers/usb/serial/pl2303.h | 3 +++
> 2 files changed, 4 insertions(+)
>
> diff --git a/drivers/usb/serial/pl2303.c b/drivers/usb/serial/pl2303.c
> index 98e7a5df0..d5ec72575 100644
> --- a/drivers/usb/serial/pl2303.c
> +++ b/drivers/usb/serial/pl2303.c
> @@ -105,6 +105,7 @@ static const struct usb_device_id id_table[] = {
> { USB_DEVICE(SANWA_VENDOR_ID, SANWA_PRODUCT_ID) },
> { USB_DEVICE(ADLINK_VENDOR_ID, ADLINK_ND6530_PRODUCT_ID) },
> { USB_DEVICE(SMART_VENDOR_ID, SMART_PRODUCT_ID) },
> + { USB_DEVICE(DELOCK_VENDOR_ID, DELOCK_PRODUCT_ID) },
> { } /* Terminating entry */
> };
>
> diff --git a/drivers/usb/serial/pl2303.h b/drivers/usb/serial/pl2303.h
> index 4e2554d55..01936de13 100644
> --- a/drivers/usb/serial/pl2303.h
> +++ b/drivers/usb/serial/pl2303.h
> @@ -153,3 +153,6 @@
> #define SMART_VENDOR_ID 0x0b8c
> #define SMART_PRODUCT_ID 0x2303
>
> +/* Delock Infrared Adapter */
> +#define DELOCK_VENDOR_ID 0x1685
> +#define DELOCK_PRODUCT_ID 0x2000
> --
> 2.20.1
>
Hi,
This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him
a patch that has triggered this response. He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created. Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.
You are receiving this message because of the following common error(s)
as indicated below:
- Your patch does not have a Signed-off-by: line. Please read the
kernel file, Documentation/SubmittingPatches and resend it after
adding that line. Note, the line needs to be in the body of the
email, before the patch, not at the bottom of the patch or in the
email signature.
If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.
thanks,
greg k-h's patch email bot
^ permalink raw reply [flat|nested] 8+ messages in thread
* USB: serial: pl2303: add Delock Infrared device id
@ 2019-02-09 9:46 Johan Hovold
0 siblings, 0 replies; 8+ messages in thread
From: Johan Hovold @ 2019-02-09 9:46 UTC (permalink / raw)
To: ebrahim; +Cc: linux-usb
On Sat, Feb 09, 2019 at 12:18:40PM +0330, ebrahim@gnu.org wrote:
> From: Ebrahim Byagowi <ebrahim@gnu.org>
>
> This makes Delock Infrared adapter to work as a USB to Serial device.
> ---
> drivers/usb/serial/pl2303.c | 1 +
> drivers/usb/serial/pl2303.h | 3 +++
> 2 files changed, 4 insertions(+)
>
> diff --git a/drivers/usb/serial/pl2303.c b/drivers/usb/serial/pl2303.c
> index 98e7a5df0..d5ec72575 100644
> --- a/drivers/usb/serial/pl2303.c
> +++ b/drivers/usb/serial/pl2303.c
> @@ -105,6 +105,7 @@ static const struct usb_device_id id_table[] = {
> { USB_DEVICE(SANWA_VENDOR_ID, SANWA_PRODUCT_ID) },
> { USB_DEVICE(ADLINK_VENDOR_ID, ADLINK_ND6530_PRODUCT_ID) },
> { USB_DEVICE(SMART_VENDOR_ID, SMART_PRODUCT_ID) },
> + { USB_DEVICE(DELOCK_VENDOR_ID, DELOCK_PRODUCT_ID) },
> { } /* Terminating entry */
> };
>
> diff --git a/drivers/usb/serial/pl2303.h b/drivers/usb/serial/pl2303.h
> index 4e2554d55..01936de13 100644
> --- a/drivers/usb/serial/pl2303.h
> +++ b/drivers/usb/serial/pl2303.h
> @@ -153,3 +153,6 @@
> #define SMART_VENDOR_ID 0x0b8c
> #define SMART_PRODUCT_ID 0x2303
>
> +/* Delock Infrared Adapter */
> +#define DELOCK_VENDOR_ID 0x1685
> +#define DELOCK_PRODUCT_ID 0x2000
Please post the output of lsusb -v for this device, and perhaps also a
log from when connecting the device with driver debugging enabled.
How did you determine that this a pl2303 device?
Johan
^ permalink raw reply [flat|nested] 8+ messages in thread
* USB: serial: pl2303: add Delock Infrared device id
@ 2019-02-09 10:44 ebrahim
0 siblings, 0 replies; 8+ messages in thread
From: ebrahim @ 2019-02-09 10:44 UTC (permalink / raw)
To: Johan Hovold; +Cc: linux-usb
On 2/9/19 1:16 PM, Johan Hovold wrote:
> On Sat, Feb 09, 2019 at 12:18:40PM +0330, ebrahim@gnu.org wrote:
>> From: Ebrahim Byagowi <ebrahim@gnu.org>
>>
>> This makes Delock Infrared adapter to work as a USB to Serial device.
>> ---
>> drivers/usb/serial/pl2303.c | 1 +
>> drivers/usb/serial/pl2303.h | 3 +++
>> 2 files changed, 4 insertions(+)
>>
>> diff --git a/drivers/usb/serial/pl2303.c b/drivers/usb/serial/pl2303.c
>> index 98e7a5df0..d5ec72575 100644
>> --- a/drivers/usb/serial/pl2303.c
>> +++ b/drivers/usb/serial/pl2303.c
>> @@ -105,6 +105,7 @@ static const struct usb_device_id id_table[] = {
>> { USB_DEVICE(SANWA_VENDOR_ID, SANWA_PRODUCT_ID) },
>> { USB_DEVICE(ADLINK_VENDOR_ID, ADLINK_ND6530_PRODUCT_ID) },
>> { USB_DEVICE(SMART_VENDOR_ID, SMART_PRODUCT_ID) },
>> + { USB_DEVICE(DELOCK_VENDOR_ID, DELOCK_PRODUCT_ID) },
>> { } /* Terminating entry */
>> };
>>
>> diff --git a/drivers/usb/serial/pl2303.h b/drivers/usb/serial/pl2303.h
>> index 4e2554d55..01936de13 100644
>> --- a/drivers/usb/serial/pl2303.h
>> +++ b/drivers/usb/serial/pl2303.h
>> @@ -153,3 +153,6 @@
>> #define SMART_VENDOR_ID 0x0b8c
>> #define SMART_PRODUCT_ID 0x2303
>>
>> +/* Delock Infrared Adapter */
>> +#define DELOCK_VENDOR_ID 0x1685
>> +#define DELOCK_PRODUCT_ID 0x2000
> Please post the output of lsusb -v for this device, and perhaps also a
> log from when connecting the device with driver debugging enabled.
lsusb -v -d 1685:0200
Bus 002 Device 019: ID 1685:0200 Delock Infrared adapter
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 1
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x1685 Delock
idProduct 0x0200 Infrared adapter
bcdDevice 0.08
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0027
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 440mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 0
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x000a 1x 10 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
I've uploaded a screenshot here
https://commons.wikimedia.org/wiki/File:A_modified_kernel_screenshot_on_QEMU.png
which shows it understands a remote control commands also.
>
> How did you determine that this a pl2303 device?
I tried to find a compatible driver from different IR adapters I have
around, one of them a 0df7:0620 which identifies itself as a `Mobile
Action Technology, Inc. MA-620 Infrared Adapter`, enlisted on the same
header, uses the driver and I found the same driver works for this dongle.
Uploaded the patch with signed-off tag and correcting a copy paste
error, please ignore the original. Thanks!
>
> Johan
>
>
From 05164e35fca7c2b2bc3bb14e50c744a778460f6a Mon Sep 17 00:00:00 2001
From: Ebrahim Byagowi <ebrahim@gnu.org>
Date: Sat, 9 Feb 2019 11:05:23 +0330
Subject: [PATCH] USB: serial: pl2303: add Delock Infrared device id
This makes Delock Infrared adapter to work as a USB to Serial device.
Signed-off-by: Ebrahim Byagowi <ebrahim@gnu.org>
---
drivers/usb/serial/pl2303.c | 1 +
drivers/usb/serial/pl2303.h | 3 +++
2 files changed, 4 insertions(+)
From 05164e35fca7c2b2bc3bb14e50c744a778460f6a Mon Sep 17 00:00:00 2001
From: Ebrahim Byagowi <ebrahim@gnu.org>
Date: Sat, 9 Feb 2019 11:05:23 +0330
Subject: [PATCH] USB: serial: pl2303: add Delock Infrared device id
This makes Delock Infrared adapter to work as a USB to Serial device.
Signed-off-by: Ebrahim Byagowi <ebrahim@gnu.org>
---
drivers/usb/serial/pl2303.c | 1 +
drivers/usb/serial/pl2303.h | 3 +++
2 files changed, 4 insertions(+)
diff --git a/drivers/usb/serial/pl2303.c b/drivers/usb/serial/pl2303.c
index 98e7a5df0..d5ec72575 100644
--- a/drivers/usb/serial/pl2303.c
+++ b/drivers/usb/serial/pl2303.c
@@ -105,6 +105,7 @@ static const struct usb_device_id id_table[] = {
{ USB_DEVICE(SANWA_VENDOR_ID, SANWA_PRODUCT_ID) },
{ USB_DEVICE(ADLINK_VENDOR_ID, ADLINK_ND6530_PRODUCT_ID) },
{ USB_DEVICE(SMART_VENDOR_ID, SMART_PRODUCT_ID) },
+ { USB_DEVICE(DELOCK_VENDOR_ID, DELOCK_PRODUCT_ID) },
{ } /* Terminating entry */
};
diff --git a/drivers/usb/serial/pl2303.h b/drivers/usb/serial/pl2303.h
index 4e2554d55..6e6df7823 100644
--- a/drivers/usb/serial/pl2303.h
+++ b/drivers/usb/serial/pl2303.h
@@ -153,3 +153,6 @@
#define SMART_VENDOR_ID 0x0b8c
#define SMART_PRODUCT_ID 0x2303
+/* Delock Infrared Adapter */
+#define DELOCK_VENDOR_ID 0x1685
+#define DELOCK_PRODUCT_ID 0x0200
--
2.20.1
^ permalink raw reply related [flat|nested] 8+ messages in thread
* USB: serial: pl2303: add Delock Infrared device id
@ 2019-02-09 15:41 Johan Hovold
0 siblings, 0 replies; 8+ messages in thread
From: Johan Hovold @ 2019-02-09 15:41 UTC (permalink / raw)
To: Ebrahim Byagowi; +Cc: Johan Hovold, linux-usb
On Sat, Feb 09, 2019 at 02:14:21PM +0330, Ebrahim Byagowi wrote:
>
> On 2/9/19 1:16 PM, Johan Hovold wrote:
> > On Sat, Feb 09, 2019 at 12:18:40PM +0330, ebrahim@gnu.org wrote:
> >> From: Ebrahim Byagowi <ebrahim@gnu.org>
> >>
> >> This makes Delock Infrared adapter to work as a USB to Serial device.
> >> ---
> >> drivers/usb/serial/pl2303.c | 1 +
> >> drivers/usb/serial/pl2303.h | 3 +++
> >> 2 files changed, 4 insertions(+)
> >> +/* Delock Infrared Adapter */
> >> +#define DELOCK_VENDOR_ID 0x1685
> >> +#define DELOCK_PRODUCT_ID 0x2000
> > Please post the output of lsusb -v for this device, and perhaps also a
> > log from when connecting the device with driver debugging enabled.
> lsusb -v -d 1685:0200
>
> Bus 002 Device 019: ID 1685:0200 Delock Infrared adapter
> Couldn't open device, some information will be missing
> Device Descriptor:
> bLength 18
> bDescriptorType 1
> bcdUSB 1.10
> bDeviceClass 255 Vendor Specific Class
> bDeviceSubClass 1
> bDeviceProtocol 0
> bMaxPacketSize0 8
> idVendor 0x1685 Delock
> idProduct 0x0200 Infrared adapter
> bcdDevice 0.08
> iManufacturer 0
> iProduct 0
> iSerial 0
> bNumConfigurations 1
> Configuration Descriptor:
> bLength 9
> bDescriptorType 2
> wTotalLength 0x0027
> bNumInterfaces 1
> bConfigurationValue 1
> iConfiguration 0
> bmAttributes 0x80
> (Bus Powered)
> MaxPower 440mA
> Interface Descriptor:
> bLength 9
> bDescriptorType 4
> bInterfaceNumber 0
> bAlternateSetting 0
> bNumEndpoints 3
> bInterfaceClass 0
> bInterfaceSubClass 0
> bInterfaceProtocol 0
> iInterface 0
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x81 EP 1 IN
> bmAttributes 3
> Transfer Type Interrupt
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x000a 1x 10 bytes
> bInterval 1
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x02 EP 2 OUT
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0040 1x 64 bytes
> bInterval 0
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x83 EP 3 IN
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0040 1x 64 bytes
> bInterval 0
These descriptors do no look like they come from a pl2303 device (e.g.
the device descriptor class and protocol is 255/1/0 and not 0/0/0).
> I've uploaded a screenshot here
> https://commons.wikimedia.org/wiki/File:A_modified_kernel_screenshot_on_QEMU.png
> which shows it understands a remote control commands also.
It shows that you receive something over the bulk-in endpoint at the
default line speed, but those -EPIPE errors also tells us that this is
not a pl2303 device.
I suspect there are further errors in the log after you've opened the
device which can involve setting the baudrate.
> > How did you determine that this a pl2303 device?
>
> I tried to find a compatible driver from different IR adapters I have
> around, one of them a 0df7:0620 which identifies itself as a `Mobile
> Action Technology, Inc. MA-620 Infrared Adapter`, enlisted on the same
> header, uses the driver and I found the same driver works for this dongle.
Some quick searching for the MA-620 descriptors show that those are
indeed from a pl2303 and are quite different from the ones you posted
above:
https://sparcher.blogspot.com/2016/11/howto-some-experience-with-usb-irda.html
There are other usb-serial chips that can be found in other ir-devices
too.
Would you be able to open the device to see if you can identify a
generic usb-serial chip inside?
Johan
^ permalink raw reply [flat|nested] 8+ messages in thread
* USB: serial: pl2303: add Delock Infrared device id
@ 2019-02-09 22:19 ebrahim
0 siblings, 0 replies; 8+ messages in thread
From: ebrahim @ 2019-02-09 22:19 UTC (permalink / raw)
To: Johan Hovold; +Cc: linux-usb
On 2/9/19 7:11 PM, Johan Hovold wrote:
> On Sat, Feb 09, 2019 at 02:14:21PM +0330, Ebrahim Byagowi wrote:
>> On 2/9/19 1:16 PM, Johan Hovold wrote:
>>> On Sat, Feb 09, 2019 at 12:18:40PM +0330, ebrahim@gnu.org wrote:
>>>> From: Ebrahim Byagowi <ebrahim@gnu.org>
>>>>
>>>> This makes Delock Infrared adapter to work as a USB to Serial device.
>>>> ---
>>>> drivers/usb/serial/pl2303.c | 1 +
>>>> drivers/usb/serial/pl2303.h | 3 +++
>>>> 2 files changed, 4 insertions(+)
>
>>>> +/* Delock Infrared Adapter */
>>>> +#define DELOCK_VENDOR_ID 0x1685
>>>> +#define DELOCK_PRODUCT_ID 0x2000
>>> Please post the output of lsusb -v for this device, and perhaps also a
>>> log from when connecting the device with driver debugging enabled.
>> lsusb -v -d 1685:0200
>>
>> Bus 002 Device 019: ID 1685:0200 Delock Infrared adapter
>> Couldn't open device, some information will be missing
>> Device Descriptor:
>> bLength 18
>> bDescriptorType 1
>> bcdUSB 1.10
>> bDeviceClass 255 Vendor Specific Class
>> bDeviceSubClass 1
>> bDeviceProtocol 0
>> bMaxPacketSize0 8
>> idVendor 0x1685 Delock
>> idProduct 0x0200 Infrared adapter
>> bcdDevice 0.08
>> iManufacturer 0
>> iProduct 0
>> iSerial 0
>> bNumConfigurations 1
>> Configuration Descriptor:
>> bLength 9
>> bDescriptorType 2
>> wTotalLength 0x0027
>> bNumInterfaces 1
>> bConfigurationValue 1
>> iConfiguration 0
>> bmAttributes 0x80
>> (Bus Powered)
>> MaxPower 440mA
>> Interface Descriptor:
>> bLength 9
>> bDescriptorType 4
>> bInterfaceNumber 0
>> bAlternateSetting 0
>> bNumEndpoints 3
>> bInterfaceClass 0
>> bInterfaceSubClass 0
>> bInterfaceProtocol 0
>> iInterface 0
>> Endpoint Descriptor:
>> bLength 7
>> bDescriptorType 5
>> bEndpointAddress 0x81 EP 1 IN
>> bmAttributes 3
>> Transfer Type Interrupt
>> Synch Type None
>> Usage Type Data
>> wMaxPacketSize 0x000a 1x 10 bytes
>> bInterval 1
>> Endpoint Descriptor:
>> bLength 7
>> bDescriptorType 5
>> bEndpointAddress 0x02 EP 2 OUT
>> bmAttributes 2
>> Transfer Type Bulk
>> Synch Type None
>> Usage Type Data
>> wMaxPacketSize 0x0040 1x 64 bytes
>> bInterval 0
>> Endpoint Descriptor:
>> bLength 7
>> bDescriptorType 5
>> bEndpointAddress 0x83 EP 3 IN
>> bmAttributes 2
>> Transfer Type Bulk
>> Synch Type None
>> Usage Type Data
>> wMaxPacketSize 0x0040 1x 64 bytes
>> bInterval 0
> These descriptors do no look like they come from a pl2303 device (e.g.
> the device descriptor class and protocol is 255/1/0 and not 0/0/0).
>
>> I've uploaded a screenshot here
>> https://commons.wikimedia.org/wiki/File:A_modified_kernel_screenshot_on_QEMU.png
>> which shows it understands a remote control commands also.
> It shows that you receive something over the bulk-in endpoint at the
> default line speed, but those -EPIPE errors also tells us that this is
> not a pl2303 device.
Oh, understandable. And very sorry that I was misleading here.
>
> I suspect there are further errors in the log after you've opened the
> device which can involve setting the baudrate.
>
>>> How did you determine that this a pl2303 device?
>> I tried to find a compatible driver from different IR adapters I have
>> around, one of them a 0df7:0620 which identifies itself as a `Mobile
>> Action Technology, Inc. MA-620 Infrared Adapter`, enlisted on the same
>> header, uses the driver and I found the same driver works for this dongle.
> Some quick searching for the MA-620 descriptors show that those are
> indeed from a pl2303 and are quite different from the ones you posted
> above:
>
> https://sparcher.blogspot.com/2016/11/howto-some-experience-with-usb-irda.html
>
> There are other usb-serial chips that can be found in other ir-devices
> too.
>
> Would you be able to open the device to see if you can identify a
> generic usb-serial chip inside?
Here is a picture of its inside[1] and that 3606 apparently is the usb
to serial chip.
We suspected it is related to[2] but its pins doesn't match and I
couldn't yet test the module provided there is related for some reason
so any pointer will be nice.
Thanks!
[1]:
https://commons.wikimedia.org/wiki/File:Infrared_Device,_VID1685_PID0200.jpg
[2]:
https://www.asix.com.tw/products.php?op=pItemdetail&PItemID=112;74;109&PLine=74
>
> Johan
>
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* USB: serial: pl2303: add Delock Infrared device id
@ 2019-02-11 8:24 Johan Hovold
0 siblings, 0 replies; 8+ messages in thread
From: Johan Hovold @ 2019-02-11 8:24 UTC (permalink / raw)
To: Ebrahim Byagowi; +Cc: Johan Hovold, linux-usb
On Sun, Feb 10, 2019 at 01:49:16AM +0330, Ebrahim Byagowi wrote:
>
> On 2/9/19 7:11 PM, Johan Hovold wrote:
> > On Sat, Feb 09, 2019 at 02:14:21PM +0330, Ebrahim Byagowi wrote:
> >> On 2/9/19 1:16 PM, Johan Hovold wrote:
> >>> On Sat, Feb 09, 2019 at 12:18:40PM +0330, ebrahim@gnu.org wrote:
> >>>> From: Ebrahim Byagowi <ebrahim@gnu.org>
> >>>>
> >>>> This makes Delock Infrared adapter to work as a USB to Serial device.
> >>>> ---
> >>>> drivers/usb/serial/pl2303.c | 1 +
> >>>> drivers/usb/serial/pl2303.h | 3 +++
> >>>> 2 files changed, 4 insertions(+)
> > These descriptors do no look like they come from a pl2303 device (e.g.
> > the device descriptor class and protocol is 255/1/0 and not 0/0/0).
> >
> >> I've uploaded a screenshot here
> >> https://commons.wikimedia.org/wiki/File:A_modified_kernel_screenshot_on_QEMU.png
> >> which shows it understands a remote control commands also.
> > It shows that you receive something over the bulk-in endpoint at the
> > default line speed, but those -EPIPE errors also tells us that this is
> > not a pl2303 device.
> Oh, understandable. And very sorry that I was misleading here.
No, problem.
> > Would you be able to open the device to see if you can identify a
> > generic usb-serial chip inside?
>
> Here is a picture of its inside[1] and that 3606 apparently is the usb
> to serial chip.
>
> We suspected it is related to[2] but its pins doesn't match and I
> couldn't yet test the module provided there is related for some reason
> so any pointer will be nice.
No, sorry. It's seems unlikely to be a mcs7780 given the pins.
Perhaps looking closer at the windows driver and snooping traffic might
provide some insights into the protocol used.
A search also revealed one libusb project for this device on
sourcefourge, but judging from a very quick look it also just did reads
and writes over the bulk-endpoints without any control commands. But
perhaps someone has done some research in this area before you.
Johan
> [1]:
> https://commons.wikimedia.org/wiki/File:Infrared_Device,_VID1685_PID0200.jpg
>
> [2]:
> https://www.asix.com.tw/products.php?op=pItemdetail&PItemID=112;74;109&PLine=74
^ permalink raw reply [flat|nested] 8+ messages in thread
* USB: serial: pl2303: add Delock Infrared device id
@ 2019-02-11 10:17 ebrahim
0 siblings, 0 replies; 8+ messages in thread
From: ebrahim @ 2019-02-11 10:17 UTC (permalink / raw)
To: Johan Hovold; +Cc: linux-usb
Fantastic, thank you so much for the help.
On 2/11/19 11:54 AM, Johan Hovold wrote:
> On Sun, Feb 10, 2019 at 01:49:16AM +0330, Ebrahim Byagowi wrote:
>> On 2/9/19 7:11 PM, Johan Hovold wrote:
>>> On Sat, Feb 09, 2019 at 02:14:21PM +0330, Ebrahim Byagowi wrote:
>>>> On 2/9/19 1:16 PM, Johan Hovold wrote:
>>>>> On Sat, Feb 09, 2019 at 12:18:40PM +0330, ebrahim@gnu.org wrote:
>>>>>> From: Ebrahim Byagowi <ebrahim@gnu.org>
>>>>>>
>>>>>> This makes Delock Infrared adapter to work as a USB to Serial device.
>>>>>> ---
>>>>>> drivers/usb/serial/pl2303.c | 1 +
>>>>>> drivers/usb/serial/pl2303.h | 3 +++
>>>>>> 2 files changed, 4 insertions(+)
>>> These descriptors do no look like they come from a pl2303 device (e.g.
>>> the device descriptor class and protocol is 255/1/0 and not 0/0/0).
>>>
>>>> I've uploaded a screenshot here
>>>> https://commons.wikimedia.org/wiki/File:A_modified_kernel_screenshot_on_QEMU.png
>>>> which shows it understands a remote control commands also.
>>> It shows that you receive something over the bulk-in endpoint at the
>>> default line speed, but those -EPIPE errors also tells us that this is
>>> not a pl2303 device.
>> Oh, understandable. And very sorry that I was misleading here.
> No, problem.
>
>>> Would you be able to open the device to see if you can identify a
>>> generic usb-serial chip inside?
>> Here is a picture of its inside[1] and that 3606 apparently is the usb
>> to serial chip.
>>
>> We suspected it is related to[2] but its pins doesn't match and I
>> couldn't yet test the module provided there is related for some reason
>> so any pointer will be nice.
> No, sorry. It's seems unlikely to be a mcs7780 given the pins.
>
> Perhaps looking closer at the windows driver and snooping traffic might
> provide some insights into the protocol used.
>
> A search also revealed one libusb project for this device on
> sourcefourge, but judging from a very quick look it also just did reads
> and writes over the bulk-endpoints without any control commands. But
> perhaps someone has done some research in this area before you.
>
> Johan
>
>> [1]:
>> https://commons.wikimedia.org/wiki/File:Infrared_Device,_VID1685_PID0200.jpg
>>
>> [2]:
>> https://www.asix.com.tw/products.php?op=pItemdetail&PItemID=112;74;109&PLine=74
>
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2019-02-11 10:17 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-02-09 9:46 USB: serial: pl2303: add Delock Infrared device id Johan Hovold
-- strict thread matches above, loose matches on Subject: below --
2019-02-11 10:17 ebrahim
2019-02-11 8:24 Johan Hovold
2019-02-09 22:19 ebrahim
2019-02-09 15:41 Johan Hovold
2019-02-09 10:44 ebrahim
2019-02-09 9:08 Greg Kroah-Hartman
2019-02-09 8:48 ebrahim
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).