On Mon, Jan 07, 2008 at 12:42:03PM +, Alan Cox wrote:
> > applied in reverse (a partial revert to 2.6.22) makes
> > the corruption go away, but is likely just papering over the root cause.
> > Cc'ed the gpsbabel developer mailing list, in case we have to
> > fix this in userspace.
>
> Please t
On Mon, Jan 07, 2008 at 12:42:03PM +, Alan Cox wrote:
> Please try the following
>
> drivers/char/tty_ioctl.c| 19 +++
> drivers/usb/serial/pl2303.c |7 +++
> include/linux/tty.h |1 +
> 3 files changed, 27 insertions(+)
Your patch works fine here, the re
> applied in reverse (a partial revert to 2.6.22) makes
> the corruption go away, but is likely just papering over the root cause.
> Cc'ed the gpsbabel developer mailing list, in case we have to
> fix this in userspace.
Please try the following
diff -u --new-file --recursive --exclude-from /usr/s
On Sat, Jan 05, 2008 at 02:09:32AM +, Alan Cox wrote:
> > first segment reverted -> works OK
> > first segment applied -> breaks
>
> So I would guess while data is being transferred your code sets the tty
> settings to the exact ones that were still in use, and this now drops
> bytes ?
Yes -
> The thing that's a little non-standard in the way we talk to the device is
> that we frequently reset VMIN/VTIME (but _not_ cflags) while the device may
> be streaming data at us. On Mac, at least, it looks like he PL2303 driver
> reprograms the device resulting in a brief interrupt of data tha
On Sat, 5 Jan 2008 01:02:54 +0100
Mirko Parthey <[EMAIL PROTECTED]> wrote:
> On Fri, Jan 04, 2008 at 10:41:48PM +, Alan Cox wrote:
> > On Fri, 4 Jan 2008 23:16:44 +0100
> > > first two segments applied, last segment reverted -> breaks
> > > first two segments reverted, last segment applied ->
On Fri, Jan 04, 2008 at 10:41:48PM +, Alan Cox wrote:
> On Fri, 4 Jan 2008 23:16:44 +0100
> > first two segments applied, last segment reverted -> breaks
> > first two segments reverted, last segment applied -> works OK
>
> Can you see which of the first two ?
first segment reverted -> works
On Fri, 4 Jan 2008 23:16:44 +0100
> first two segments applied, last segment reverted -> breaks
> first two segments reverted, last segment applied -> works OK
Can you see which of the first two ?
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message
On Fri, Jan 04, 2008 at 04:29:47PM +, Alan Cox wrote:
> > The appended patch applied in reverse (a partial revert to 2.6.22) makes
> > the corruption go away, but is likely just papering over the root cause.
> > Cc'ed the gpsbabel developer mailing list, in case we have to
> > fix this in users
> The appended patch applied in reverse (a partial revert to 2.6.22) makes
> the corruption go away, but is likely just papering over the root cause.
> Cc'ed the gpsbabel developer mailing list, in case we have to
> fix this in userspace.
Reverting it breaks the speed handling.
Can you apply just
Starting with Linux 2.6.23, I get corrupted data (lost and altered bytes)
when using the Prolific PL2303 USB-serial driver with GPSBabel
and the GlobalSat DG-100 GPS data logger.
(I am the author of GPSBabel's DG-100 support).
The appended patch applied in reverse (a partial revert to 2.6.22) make
11 matches
Mail list logo
