This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

tcdrain


Hello

It looks like tcdrain in cygwin doesn't wait until data are transmitted,
but just drains the software buffer, and doesn't drain the buffer in the
16550A chip. Can you please confirm that this is really how Cygwin
works?

I got data corrupted because of this because the data rate was switched
before all the old data got transmitted.

If it's this case, I suggest to add a note about this exception into
http://www.cygwin.com/cygwin-api/std-posix.html

Doesn't POSIX say "tcdrain()  waits  until all output written to the
object referred to by fd has been transmitted" (taken from man tcdrain),
in which case the aforementioned behaviour would not be POSIX compliant.

CL<

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]