Bingo! I think.
Adding a short sleep right *before* turning on the break seems to have
solved it. My guess, the 'b' was still pending in the FTDI chip's
buffer, and when sending the break too early, it never had a chance to
reach the Link chip.
Stefano: patch commited in ftdi branch, can you give it a try? Also, can
you check if the read/write lengths looks better now? I.e. not claiming
it has written 4 million bytes...:)
Johan
On 01/03/16 22:24, Johan Ström wrote:
On 01/03/16 14:11, Stefano Miccoli wrote:
Really weird, since it should just use semi-low-level USB messages
to tell the device to send a Break; the OS should not interfere?
Further weirdness.
I just noticed that my main network (FreeBSD, same version, with
LinkUSB v1.5) suffers from the restore-baudrate/break-issue too.
I tried that LinkUSB dongle in my virtual Ubuntu, and it worked fine.
So I can rule out differences in the dongles at least.
Also tried with my full bus connected, and it still worked fine (on
the Ubuntu)...
So: two different machines, same OS, same dongle. Working on one,
broken on one. Could it be something with the USB host?
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
