[Linux-usb-users] Re: pl2303 problem, more data

2005-03-24 Thread Brian Perkins
Greg KH wrote: On Tue, Mar 22, 2005 at 07:13:49PM -0500, Brian Perkins wrote: Hm, can you send the values of /proc/bus/usb/devices for both the type one and type two controllers? type1 (good): T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 6 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub

[Linux-usb-users] Re: pl2303 problem, more data

2005-03-23 Thread Brian Perkins
Greg KH wrote: On Mon, Mar 21, 2005 at 11:45:38PM -0500, Brian Perkins wrote: So it doesn't matter that the "type one" variety works fine with this script, and the "type two" variety doesn't? Who knows? :) As these devices are undocumented, in the end, we reall

[Linux-usb-users] pl2303 problem, more data

2005-03-19 Thread Brian Perkins
So I've been having problems with my pl2303 adapter. The symptom is that it will download data from my GPS only some of the time. Upon closer examination, it appears that it will sometimes drop the first character on a read. I have a bit more data on this now. I got my hands on another pl2303 a

Re: [Linux-usb-users] pl2303 problem

2005-01-17 Thread Brian Perkins
ged to get it to work once also (it printed out "foo" correctly) Here's the log file for that: http://netspace.org/~bperkins/pl2303bad.text And perhaps, more usefully the diff: http://netspace.org/~bperkins/pl2303diff.text which seems closer to the realm of readable. Greg KH wrote: On Su

Re: [Linux-usb-users] pl2303 problem

2004-11-21 Thread Brian Perkins
Greg KH wrote: On Sun, Nov 14, 2004 at 05:08:31PM -0500, Brian Perkins wrote: I'm running 2.6.10-rc1, and I'm having trouble with the PL2303 driver. Can you try 2.6.10-rc2 and let us know if you still have the same problems there? I tried rc2, and the pl2303 problems seemed to be the

[Linux-usb-users] pl2303 problem

2004-11-14 Thread Brian Perkins
I'm running 2.6.10-rc1, and I'm having trouble with the PL2303 driver. I noticed that about half the time, when using my GPS, gpsbabel drops the first character after an open. At first I suspect GPSbabel, but I can roughly reproduce the problem by shorting send and receive on the rs232, and runn