linux-kernel - Re: PL2303 Driver missing support for USB to Serial Cable

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <47B6DC7A.3040308@gmail.com>
Date:	Sat, 16 Feb 2008 13:52:10 +0100
From:	Jiri Slaby <jirislaby@...il.com>
To:	Stephan Rose <stephan@...international.de>
CC:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: PL2303 Driver missing support for USB to Serial Cable

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?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/