linux-kernel - Re: PROBLEM: NUDAM (USB-485) nowaday not detected by pl2303 module

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] [day] [month] [year] [list]

Message-ID: <20080304235214.GC3773@kroah.com>
Date:	Tue, 4 Mar 2008 15:52:14 -0800
From:	Greg KH <greg@...ah.com>
To:	rafa400@...gandia.com
Cc:	linux-kernel@...r.kernel.org
Subject: Re: PROBLEM: NUDAM (USB-485) nowaday not detected by pl2303 module

On Tue, Mar 04, 2008 at 09:14:53AM -0800, rafa400@...gandia.com wrote:
> [1.] new NUDAM (USB-485) converter not recogniced by pl2303. Little change
> required.
> [2.] Until now NUDAM USB to RS-485/422 RS232 converter was detected by USB
> system and pl2303 module working fine in my Debian as /dev/ttyUSB0
> 
> # dmesg
> ....
> usb 5-1.3: new full speed USB device using ehci_hcd and address 17
> usb 5-1.3: configuration #1 chosen from 1 choice
> pl2303 5-1.3:1.0: pl2303 converter detected
> usb 5-1.3: pl2303 converter now attached to ttyUSB0
> 
> # lsusb
> Bus 005 Device 017: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
> 
>  They changed USB ID and now its like:
> 
> # lsusb
> Bus 005 Device 016: ID 0b63:6530 ADLink Technology, Inc.
> 
> but this ID is not detected by PD2303 module.
> a little change in pl2303 solve the problem

Are you sure that the chip is still a pl2303 device?  If so, can you
send us a patch for this device id as per the
Documentation/SubmittingPatches directions?

thanks,

greg k-h
--
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/