On the mailing list, some have come to the conclusion that the 0.17 and 1.0
behaviour of ftdi_read_data() is the most sensible, but needs mor
explanation.
Hopefully the added explanation fullfills this target.
--
Uwe Bonnes bon@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
>From eec274ebd929611180b3524c66ea61025cd391d9 Mon Sep 17 00:00:00 2001
From: Uwe Bonnes <bon@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 29 Mar 2011 16:17:43 +0200
Subject: Better explanation of ftdi_read_data() behaviour
---
src/ftdi.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/src/ftdi.c b/src/ftdi.c
index c7856a4..8a7b2ba 100644
--- a/src/ftdi.c
+++ b/src/ftdi.c
@@ -1590,6 +1590,7 @@ int ftdi_write_data_get_chunksize(struct ftdi_context
*ftdi, unsigned int *chunk
/**
Reads data in chunks (see ftdi_read_data_set_chunksize()) from the chip.
+ Returns when at least one byte is available or when the latency timer has
elapsed
Automatically strips the two modem status bytes transfered during every
read.
\param ftdi pointer to ftdi_context
--
1.7.1
--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
|
