X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Message-ID: <48581FBC.7020801@gmail.com>
Date: Tue, 17 Jun 2008 16:34:04 -0400
From: Paul Rogers <prrogers AT gmail DOT com>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Is There a Reason for Limited "/dev/com" to 16 Ports?
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
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

Should "devices.in" really have a limit of 16 "/dev/com" ports when the 
"ttyS" ports are allowed up to 64 values (max of 63 since it is a 
zero-based index)?

I changed the upper limit on the "com" range for 1.5.25 to "64" along 
with the "ttyS" range and it compiles and allows using the "/dev/com" 
aliases above 16 ports without a problem.

Yet when using a recent snapshot only "ttyS" ports work above the 16th 
port. The "/dev/com" identifiers beyond "16" do not open.

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