From: "Hans Kester" <hans@ellips.nl>
To: "Dave Korn" <dk@artimi.com>, "Keith Seitz" <keiths@redhat.com>
Cc: <insight@sources.redhat.com>, <cygwin@cygwin.com>
Subject: RE: Cannot connect to remote target via serial port
Date: Mon, 22 Nov 2004 08:16:00 -0000 [thread overview]
Message-ID: <7772A37DE7948E4D995BC6733DC62B8227DB63@nt-server2.ellips.nl> (raw)
Dave is right, /dev/comX works fine. And it is indeed not fixed in 6.1.
Hans
-----Original Message-----
From: Dave Korn [mailto:dk@artimi.com]
Sent: Friday, November 19, 2004 6:10 PM
To: 'Keith Seitz'; Hans Kester
Cc: insight@sources.redhat.com; cygwin@cygwin.com
Subject: RE: Cannot connect to remote target via serial port
> -----Original Message-----
> From: insight-owner On Behalf Of Keith Seitz
> Sent: 19 November 2004 16:48
> To: Hans Kester
> On Fri, 2004-11-19 at 05:08, Hans Kester wrote:
> > When I try to connect to my remote target (sh-elf) with the
> serial port
> > (COM1) I get the following error message:
> > "com1: Inappropriate ioctl for device."
> >
>
> Does this really still happen with 6.1? A patch was committed which I
> thought fixed the problem.
>
> So it appears the latest is that cygwin must now use "/dev/ttySX"
> (X=0,1,...) instead of "/dev/comX".
No, /dev/comX should be fine for cygwin (unless I've missed a recent
change and the docs haven't yet been updated, but I don't think that's
happened), and if it isn't, it's a cygwin bug.
http://www.cygwin.com/cygwin-ug-net/using-specialnames.html
"Cygwin also has several Windows-specific devices: /dev/comX (the serial
ports, starting with COM1 which is the same as ttyS0)"
cheers,
DaveK
--
Can't think of a witty .sigline today....
next reply other threads:[~2004-11-22 8:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 8:16 Hans Kester [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-19 13:35 Hans Kester
2004-11-19 13:18 Hans Kester
2004-11-19 13:25 ` Jon Beniston
2004-11-19 13:08 Hans Kester
2004-11-19 13:13 ` Jon Beniston
2004-11-19 16:48 ` Keith Seitz
2004-11-19 17:11 ` Dave Korn
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=7772A37DE7948E4D995BC6733DC62B8227DB63@nt-server2.ellips.nl \
--to=hans@ellips.nl \
--cc=cygwin@cygwin.com \
--cc=dk@artimi.com \
--cc=insight@sources.redhat.com \
--cc=keiths@redhat.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).