From: Paul Rogers <prrogers@gmail.com>
To: cygwin@cygwin.com
Subject: Is There a Reason for Limited "/dev/com" to 16 Ports?
Date: Wed, 18 Jun 2008 00:28:00 -0000 [thread overview]
Message-ID: <48581FBC.7020801@gmail.com> (raw)
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/
next reply other threads:[~2008-06-17 20:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 0:28 Paul Rogers [this message]
2008-06-18 1:06 ` Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48581FBC.7020801@gmail.com \
--to=prrogers@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).