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 really can never be
sure :(
> And it doesn't matter that the problem observed _precisely_ mirrors the
> problem seen in the C problem (gpsbabel)?
And that program uses the proper tty setup calls?
> If I look at an strace of gpsbabel, I can clearly see the first
> characters of certain transfers getting dropped with the type two
> adapter. The type one version works fine.
If you enable debugging in the driver:
modprobe pl2303 debug=1
what does the kernel log show? Is the data being received by the
kernel and dropped in the driver? Or does the device itself drop the
data?
If the device does it, not much the kernel can do about it :(
> If I replaced
> cat /dev/ttyUSB0 &
> sleep 1;
> echo 'foo' > /dev/ttyUSB0
>
> with
> perl -e ' open (IN ,'</dev/ttyUSB0'); open (OUT, '>/dev/ttyUSB0');
> print OUT "foo\n"; $_= <IN>;
> print $_;'
>
> Would that be OK?
No, use the tty setup calls please, to make sure that the line settings
are all properly set up.
thanks,
greg k-h
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users
