Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Dave Korn" To: "'Keith Seitz'" , "'Hans Kester'" Cc: , Subject: RE: Cannot connect to remote target via serial port Date: Fri, 19 Nov 2004 17:10:03 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <1100882868.2771.1.camel@lindt.uglyboxes.com> Message-ID: X-OriginalArrivalTime: 19 Nov 2004 17:10:03.0578 (UTC) FILETIME=[9C2CD9A0:01C4CE5A] > -----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.... -- 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/