This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Support for Baud Rates above 250000 baud?
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 10 Jan 2007 10:02:20 +0100
- Subject: Re: Support for Baud Rates above 250000 baud?
- References: <45A422DE.8000302@avegasystems.com>
- Reply-to: cygwin at cygwin dot com
On Jan 10 10:18, David le Comte wrote:
> I'm wondering if the most general way of modifying fhandler_serial.cc
> (and cf[io]speed()?) is to do what SetCommState() is doing, ie,
> if the value that is passed is NOT equivalent to one of the Bnnnnn
> "define"s, then assume it is a literal speed and pass that.
Cygwin does this already for 230400 baud. See fhandler_serial.cc.
> This would mean changing "speed_t" to be an unsigned int (can we
> now assume that is 32bit?) rather than char?, and removing and/or
> changing any parsing that cfset[io]speed() are doing.
No. This would needlessly break backward compatibility. The way to
go is to define new Bxxx values in termios.h and support them in
fhandler_serial.cc, which is what Brian already said.
What's left at this point is just http://cygwin.com/acronyms/#SHTDI.
See http://cygwin.com/contrib.html.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
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/