On Wed, Jun 29, 2016 at 11:59:06PM +0200, Michael Walle wrote:
> Am 2016-05-27 20:02, schrieb Johan Hovold:
> > On Fri, May 13, 2016 at 12:17:24PM +0200, mich...@walle.cc wrote:
> >> Hi,
> >>
> >> if the internal buffer is full, a read() returns a steady stream of
> >> zeros until one valid
From: Michael Walle
...
> What comes directly to my mind is the handling of the break condition.
> Can't look into that at the moment. But if break conditions are
> translated into status-only packets, how are two consecutive breaks
> recognized. Ie. if the break condition flag is sticky (until a
Am 2016-05-27 20:02, schrieb Johan Hovold:
On Fri, May 13, 2016 at 12:17:24PM +0200, mich...@walle.cc wrote:
Hi,
if the internal buffer is full, a read() returns a steady stream of
zeros until one valid character is received. According to my
experiments
this happens if the FT232 receives
On Fri, May 13, 2016 at 12:17:24PM +0200, mich...@walle.cc wrote:
> Hi,
>
> if the internal buffer is full, a read() returns a steady stream of
> zeros until one valid character is received. According to my experiments
> this happens if the FT232 receives characters while the device is not
>
Hi,
if the internal buffer is full, a read() returns a steady stream of
zeros until one valid character is received. According to my experiments
this happens if the FT232 receives characters while the device is not
opened. After the 257th byte the device returns overrun errors, which
are
