X-Spam-Check-By: sourceware.org Message-ID: Date: Fri, 6 Jan 2006 11:39:16 +0800 From: steven woody To: cygwin@cygwin.com Subject: Re: cat /dev/ttyS? In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline References: <43BDD742.53F71F56@dessent.net> X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k063dMPQ005159 On 1/6/06, steven woody wrote: > On 1/6/06, Brian Dessent wrote: > > steven woody wrote: > > > > > > why can't get incoming COM2 data by the following command: > > > > > > $ cat /dev/ttyS2 > > > > > > but i can get the data by other windows serial monitor programs on the > > > same port. > > > > ttyS2 is the third serial port. The first serial port is /dev/ttyS0, so > > for COM2 you want /dev/ttyS1. > > > > Brian > > > sorry, it's only a typo. the problem is still same. > > oh, i found the 'cat /dev/ttyS1' really outputs, but it has a very *big* delay that leads me thought it does not response. is the output buffered? what do i do? thanks! > > > > > > -- > > 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/ > > > > > > > -- > woody > -- woody -- 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/