From: Paul Ingemi <pingemi@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Problem using select() with com0com virtual serial ports
Date: Sat, 24 Jan 2009 22:55:00 -0000 [thread overview]
Message-ID: <7701e1400901241230k43f9f8cbub8740e7f517ab8e4@mail.gmail.com> (raw)
In-Reply-To: <20090122155522.GA5369@ednor.casa.cgf.cx>
* On Thu, Jan 22, 2009 at 10:55:22AM -0500 Christopher Faylor wrote:
> On Thu, Jan 22, 2009 at 10:25:32AM -0500, Paul Ingemi wrote:
[...]
> It is a simple enough hack that I don't mind adding it, if it fixes your
> problem but I am not convinced that your driver is operating correctly.
>
> As I had added serial port access to the Windows version of VICE one or
> two months ago, I can tell that the com0com driver is indeed buggy.
>
> IMHO, the better solution is to fix com0com, and not to apply some
> hotfixes to other software (cygwin, VICE, whatever). That's the approach
> I followed, too, ignoring com0com completely. If I might have some time,
> I might want to debug com0com myself, but don't hold your breath on it.
I agree and adding a hack to cygwin isn't necessary due to the
existance of a workaround. That said, I think it's premature to blame
com0com without finding the root cause of the problem.
Over the past two days I've been attempting to create an -mno-cygwin
executable that can reproduce the behavior I'm seeing under Cygwin.
Thus far I haven't successfully reproduced this behavior outside of a
Cygwin environment despite copying most of the code for how Cygwin
performs select() and read().
Hopefully in the future I'll be able to provide more helpful information.
--
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 prev parent reply other threads:[~2009-01-24 20:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 15:44 Paul Ingemi
2009-01-22 16:24 ` Christopher Faylor
2009-01-23 14:16 ` Spiro Trikaliotis
2009-01-24 22:55 ` Paul Ingemi [this message]
2009-01-24 22:55 ` Christopher Faylor
2009-01-25 10:45 Paul Ingemi
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=7701e1400901241230k43f9f8cbub8740e7f517ab8e4@mail.gmail.com \
--to=pingemi@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).