[1.3.3] breaks serial i/o?

["William A. Gatliff" <bgat@saturn.billgatliff.com>]

Guys:


I was recently working with Cygwin 1.3.2, doing remote serial
debugging with an ARM Evaluator-7T board using gdb-5.0.  Everything
was just peachy.

Then I upgraded, and things got bad in a hurry.  :^(

Cygwin 1.3.3 seems less stable serialio-wise than 1.3.2.  After
several days of trying, I have yet to establish a complete serial
connection with the board.  And 1.3.3 also seems to require/support
only hardware flow control on the serial lines, where 1.3.2 did not.

I'm running on Win98SE, and can test on NT4 and 2000 if necessary.

At this point, I would be happy just to be able to get Cygwin 1.3.2
back, but alas, I haven't found an archive of it anywhere on the 'net.

To make matters worse, a magazine article I'm writing that describes
how to use Cygwin and GNU tools for arm-elf development is set to
appear in in the December issue of Circuit Cellar Ink magazine.  The
article was written for 1.3.2, and won't currently work with 1.3.3
unless I can figure out what's going on by next Wednesday.  I really
would rather avoid disappointing a new crop of Cygwin and GNU tool
users.

I'm developing patches for gdb-5.0, binutils-2.11.2 and gcc-2.95.3 to
make them build under 1.3.3 (to fix the new export conflicts), but I
haven't figured out what the problem with serial communications is.
If I can't fix the problem, then the article is basically doa.

A draft of the manuscript for the article is at:

http://billgatliff.com/articles/gnu/gnu-arm7t/index.html .

Suggestions, patches, signs of moral support, etc. would all be most
graciously accepted.  Thanks for the help,


b.g.
-- 
Bill Gatliff
bgat@billgatliff.com