X-Spam-Check-By: sourceware.org Date: Wed, 10 Jan 2007 10:02:20 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Support for Baud Rates above 250000 baud? Message-ID: <20070110090220.GI23638@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <45A422DE DOT 8000302 AT avegasystems DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45A422DE.8000302@avegasystems.com> User-Agent: Mutt/1.4.2.2i Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list 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/