More than 16 Serial Ports

More than 16 Serial Ports

[Ralph Hempel]

I've got a few apps that still use serial ports, and now
that I'm using Bluetooth devices under XP, the serial
port numbers are getting really big - like COM40.

Yes, I've read about how to change the port number, and
for the Toshiba Bluetooth stack on my Dell D610, it's
not an option.

Yes, I've read the FAQ and the 16 port limit.

So now the question is, where do we poke around in the
source to increase the limit of serial ports under
Cygwin?

Or should I use another program like com2tcp to map the
serial ports to TCP ports?

Cheers, Ralph

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

RE: More than 16 Serial Ports

[Dave Korn]

Ralph Hempel wrote on 01 May 2008 16:37:

> So now the question is, where do we poke around in the
> source to increase the limit of serial ports under
> Cygwin?

  Look at winsup/cygwin/devices.in, which is a template that is used to
auto-generate the code in winsup/cygwin/devices.cc, using the
winsup/cygwin/gendevices script.

  Note that on mainline (as opposed to the 1.5.x release branch), the number
appears to have been raised to 64 quite some time ago.

http://cygwin.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/devices.in?cvsroot=src

 Revision 1.14 / (download) - annotate - [select for diffs] , Mon Oct 9
08:27:23 2006 UTC (18 months, 3 weeks ago) by corinna
Branch: MAIN
Changes since 1.13: +1 -1 lines
Diff to previous 1.13 (colored)

	* devices.in: Raise number of handled serial ports to 64.
	* devices.cc: Regenerate.

  You could copy that patch:

http://cygwin.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/devices.in.diff?r1=1.13
&r2=1.14&cvsroot=src



    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


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

Re: More than 16 Serial Ports

[Ralph Hempel]

Dave Korn wrote:
> Ralph Hempel wrote on 01 May 2008 16:37:
> 
>> So now the question is, where do we poke around in the
>> source to increase the limit of serial ports under
>> Cygwin?
> 
>   Look at winsup/cygwin/devices.in, which is a template that is used to
> auto-generate the code in winsup/cygwin/devices.cc, using the
> winsup/cygwin/gendevices script.
> 
>   Note that on mainline (as opposed to the 1.5.x release branch), the number
> appears to have been raised to 64 quite some time ago.

So to get the >16 port support, I download the source from the snapshot
area and build cygwin1.dll myself? Or can I just get prebuilt version
from the snapshot tree?

Sorry for the dumb questions. I've been using and loving cygwin for
a while now and have built things as complex as an ARM7 toolchain
and custom GDB debug stub for the target, but I've never poked around
cygwin itself since it pretty much "just works"

The serial port issue is the first major issue I've not been able
to work around easily, so far.

Cheers, Ralph

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

RE: More than 16 Serial Ports

[Dave Korn]

Ralph Hempel wrote on 01 May 2008 20:04:

> Dave Korn wrote:
>> Ralph Hempel wrote on 01 May 2008 16:37:
>> 
>>> So now the question is, where do we poke around in the
>>> source to increase the limit of serial ports under
>>> Cygwin?
>> 
>>   Look at winsup/cygwin/devices.in, which is a template that is used to
>> auto-generate the code in winsup/cygwin/devices.cc, using the
>> winsup/cygwin/gendevices script.
>> 
>>   Note that on mainline (as opposed to the 1.5.x release branch), the
>> number appears to have been raised to 64 quite some time ago.
> 
> So to get the >16 port support, I download the source from the snapshot
> area and build cygwin1.dll myself? Or can I just get prebuilt version
> from the snapshot tree?

  It's up to you.  The snapshots are all of mainline, which is a
work-in-progress at the moment that will become 1.7; it's pretty stable, but
has a lot of changes from 1.5.x and a bit risky for a production environment.
There'd be no particular advantage in building it from source versus
downloading the binary snapshot package, since (modulo non-determinacy bugs in
the compiler) you'd only get the exact same thing with minor variations in the
file paths in the debug info and the object/exe file timestamps.

  If you want minimal changes to your current system, to reduce the risk of
new and unknown bugs creeping in, your best bet is just use setup.exe to
install the source package corresponding to your current version of the DLL,
patch and rebuild that.

> Sorry for the dumb questions.

  Not dumb.  Everyone's gotta start somewhere, and your questions are
pertinent and clearly expressed :)

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


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