Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "Jon Schneider" <jon AT jschneider DOT n DOT e DOT t>
To: cygwin AT cygwin DOT com
Date: Tue, 29 Jul 2003 08:39:43 +0100
MIME-Version: 1.0
Subject: Re: tcflush waits
Message-ID: <3F2632CF.14205.3B61FD@localhost>
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body

Having now looked at the source I feel it is like this by design but
I don't understand why as there are no comments.If this is indeed
a best approximation to the intended behaviour should it be documented
as such ?

Jon

On 28 Jul 2003 at 14:49, cygwin AT cygwin DOT com wrote:

> I have an app that opens a serial port and sets VTIME to 1, VMIN to 0.
> 
> When it does tcflush(,TCIOFLUSH) or tcflush(,TCIFLUSH) it takes exactly 
> 100ms.

--
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/