All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Ebrahim Byagowi <ebrahim@gnu.org>
Cc: Johan Hovold <johan@kernel.org>, linux-usb@vger.kernel.org
Subject: USB: serial: pl2303: add Delock Infrared device id
Date: Mon, 11 Feb 2019 09:24:31 +0100	[thread overview]
Message-ID: <20190211082431.GT4686@localhost> (raw)

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

             reply	other threads:[~2019-02-11  8:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-11  8:24 Johan Hovold [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-02-11 10:17 USB: serial: pl2303: add Delock Infrared device id ebrahim
2019-02-09 22:19 ebrahim
2019-02-09 15:41 Johan Hovold
2019-02-09 10:44 ebrahim
2019-02-09  9:46 Johan Hovold
2019-02-09  9:08 Greg Kroah-Hartman
2019-02-09  8:48 ebrahim

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190211082431.GT4686@localhost \
    --to=johan@kernel.org \
    --cc=ebrahim@gnu.org \
    --cc=linux-usb@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.