Hi Greg... Thanks for the reply. See my reply below...
> Perhaps this cable is not a pl2303 device? How did you determine > that it is? Can you take it apart and see what chip is in it? Hm, not 100% sure either. I got the idea to put the ID inside pl2303.h purely because lsusb reported it has the same product and vendor ID (0e55:110b) like the patch posted on http://marc.theaimsgroup.com/?l=linux-usb-users&m=114435409524767&w=2. Taking the usb cable apart might lead a problem for me, since I plan to trade it with another cable (possibly MA 8620e) next week if I failed to make it work. However, if the store denies to trade my cable, I think I can "crack in". BTW, when hanging in an IRC channel, somebody said maybe I should try cypress_m8 kernel module. Could it be the solution? And what is the best way to find out the real problem ? Until now, I am still in doubt whether it is a driver problem or wvdial script problem... regards, Mulyadi ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
