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
Date: Mon, 22 Nov 2004 10:52:24 -0500
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Newbie question regarding tcsetattr
Message-ID: <20041122155224.GA31161@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <20041119131523 DOT 58dd206d DOT rpryor AT pryor-and-pryor DOT com> <20041122071247 DOT 4fbbe9e3 DOT rpryor AT pryor-and-pryor DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20041122071247.4fbbe9e3.rpryor@pryor-and-pryor.com>
User-Agent: Mutt/1.4.1i

On Mon, Nov 22, 2004 at 07:12:47AM -0800, Roger Pryor wrote:
>On Fri, 19 Nov 2004 13:15:23 -0800
>Roger Pryor <rpryor AT pryor-and-pryor DOT com> wrote:
>>I'm a new cygwin user, attepting to port a Linux package that uses the
>>COM ports to drive a remote device.  I'm finding that calls to
>>tcsetattr don't seem to work.  What is happening is that although the
>>speed is being setup correctly, the values that I want for c_iflag and
>>c_cflag are not being set, but left as they were before.  Is this a
>>known bug (there were conversations about this last year in the
>>archives) and if so is there any idea when it will be fixed?, or am I
>>confused (equally likely!)
>
>This seems to have dropped into a black hole, does anyone know what is
>the status of tcsetattr w.r.t serial ports?

Possibly the reason this "dropped into a black hole" is that you used
the word "newbie" in the subject, you didn't follow the reporting
guidelines at http://cygwin.com/problems.html, and while you did provide
a code snippet showing what you meant, you did not provide a simple,
compilable test case illustrating your problem.  For something like serial
I/O, it's unlikely that anyone is going to want to hack together their own
test case to confirm or deny your theory that setting the baud rate is
broken.

cgf

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