Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
To: cygwin AT cygwin DOT com
From: Todd Rearick <trearick_news AT cox DOT net>
Subject:  Re: Socket read problem on Windows XP Pro & Cygwin
Date: Tue, 25 Oct 2005 04:09:20 +0000 (UTC)
Lines: 31
Message-ID:  <loom.20051025T054811-569@post.gmane.org>
References:  <20051022035348.RADA2767.eastrmmtao03.cox.net@[172.18.52.8]> <4359C50C DOT 76649CA1 AT dessent DOT net> <loom DOT 20051022T083200-857 AT post DOT gmane DOT org> <4359EB14 DOT E677A317 AT dessent DOT net> <loom DOT 20051022T153140-747 AT post DOT gmane DOT org> <435AAAB9 DOT 27CDE133 AT dessent DOT net> <loom DOT 20051022T234629-996 AT post DOT gmane DOT org> <20051023073820 DOT GF27476 AT calimero DOT vinschen DOT de>
Mime-Version:  1.0
Content-Type:  text/plain; charset=us-ascii
Content-Transfer-Encoding:  7bit
User-Agent: Loom/3.14 (http://gmane.org/)
X-IsSubscribed: yes

Corinna Vinschen <corinna-cygwin <at> cygwin.com> writes:

> You should nevertheless use /dev/com4 or /dev/ttyS3.  I might be wrong
> but it still looks like you don't quite see what Brian was up to.
> 
> Corinna
> 

Hmm...I think I see what you're getting at.  I'm (obviously) not really all that
knowledgeable of serial ports under Cygwin.  I was quite shocked actually that I
could just open "COM4" and write to it and it seemed to work OK....

....so...If I open "COM4" from cygwin, cygwin thinks I'm really just opening
some disk file..and probably all I can do is read/write..and perhaps even that
might not be totally reliable.  If I use /dev/com4 (or /dev/ttyS3), then the
underlying software understands that I am actually opening a serial port, and
all of the things like baud rate, parity, start, stop bits..etc..can all be
configured correctly...and there is probably a lot more testing that goes into
making sure /dev/com4 works properly.

Thanks to Brian for bringing it up, and thanks to you for the clarification.  I
was missing the point that COM4 is NOT the right way to access serial port #4
under cygwin.  It's easy enough to change...

Todd








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