mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Stephan Rose <stephan@eciinternational.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: PL2303 Driver missing support for USB to Serial Cable
Date: Sat, 16 Feb 2008 13:52:10 +0100	[thread overview]
Message-ID: <47B6DC7A.3040308@gmail.com> (raw)
In-Reply-To: <1203001060.8420.11.camel@software>

On 02/14/2008 03:57 PM, Stephan Rose wrote:
> I recently purchased a USB->Com Port serial cable from Radio Shack
> (Model number 26-183) which did no seem to want to work. After looking
> into it I discovered that it is based on the Prolific chipset using the
> PL2303 driver. 
> 
> I then checked the Vendor and Product ID against the list in the drive
> and sure enough, the IDs were missing in the driver.
> 
> So here are my modifications to the PL2303 driver which have been
> working flawlessly on my system the whole week:
> 
> drivers/usb/serial/pl2303.h
> --------
> 
> /* Radio Shack 26-183 */
> #define RADIOSHACK26183_VENDOR_ID 0x05ad
> #define RADIOSHACK26183_PRODUCT_ID 0x0fba
> 
> drivers/usb/serial/pl2303.c
> --------
> 
> Added to struct usb_device_id id_table
> 
> { USB_DEVICE(RADIOSHACK26183_VENDOR_ID RADIOSHACK26183_PRODUCT_ID) }
> 
> I still have to manually modprobe the module as the kernel won't
> automatically load it when I connect the device, no idea what I would
> need to change where for that to happen.
> 
> The above though does successfully add support for that serial cable so
> I thought I'd share it with the kernel list so that it can possibly be
> added to the kernel and I can stop having to re-compile the driver every
> kernel update. :)

Well, would you mind creating, testing and posting a patch?

  reply	other threads:[~2008-02-16 12:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-14 14:57 Stephan Rose
2008-02-16 12:52 ` Jiri Slaby [this message]
2008-02-16 13:05   ` David Newall
2008-02-18  5:06     ` Greg KH
2008-02-20 14:46       ` Stephan Rose

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=47B6DC7A.3040308@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stephan@eciinternational.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome