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:	"Dave Korn" <dk AT artimi DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: Cygwin serial issues
Date:	Wed, 14 Jan 2004 15:24:04 -0000
MIME-Version:	1.0
In-Reply-To:	<Pine.GSO.4.58.0401131455340.23399@eos>
Message-ID:	<NUTMEGsM5sGmhZ26yJK00000120@NUTMEG.CAM.ARTIMI.COM>
X-OriginalArrivalTime:	14 Jan 2004 15:24:04.0640 (UTC) FILETIME=[71E56A00:01C3DAB2]

 

> -----Original Message-----
> From: cygwin-owner AT cygwin DOT com 
> [mailto:cygwin-owner AT cygwin DOT com] On Behalf Of Brian Ford

 
> I only know of the following two issues:
> 1.) tcflush can hang for a while if the device constantly 
> streams data.
> 2.) Communications can cease if the device overflows the input buffer.

  What about non-blocking serial I/O not working, at any rate for me, as I
described in the thread titled "/dev/com1 definitely broken between 1.5.5-1
and 20031218" ?  

[ http://sources.redhat.com/ml/cygwin/2004-01/msg00168.html ]


  I included a very trivial testcase to reproduce the problem - the call to
read() never returns.  Does it hang up for you too?


   cheers,
     DaveK 


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

- Raw text -