On Wed, May 07, 2008 at 12:03:19PM +0200, Corinna Vinschen wrote:
>On May 2 20:27, Nefastor wrote:
>>
>> Your trick worked as advertised, and on the first try, thank you very much
>> :handshake:
>>
>> Anyone know where this problem with tcsetattr() comes from ? Is it
>> documented or specific to
On May 2 20:27, Nefastor wrote:
>
> Your trick worked as advertised, and on the first try, thank you very much
> :handshake:
>
> Anyone know where this problem with tcsetattr() comes from ? Is it
> documented or specific to Cygwin ? (or both ?)
The reason is probably: Nobody ever implemented i
-documentation-on-Cygwin-and-Serial-Ports-tp16827997p17031175.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ
On 2008-05-01, Nefastor wrote:
> Nefastor wrote:
> >
> > Thanks for all the info, everyone :-D. I'm gonna try a few things and get
> > back to you.
> >
>
> So I've tried a few things, and obviously all hell broke loose, sort of.
> I've written a very simple "Hello World" program, which I'll past
= IGNPAR;
params.c_oflag = 0;
params.c_lflag = ICANON;
tcflush (tty, TCIFLUSH);
tcsetattr (tty,TCSANOW,¶ms);
write (tty,"Hello World",11);
close (tty);
return 0;
}
--
View this message in context:
http://www.nabble.com/Looking-for-basic-documentation-on-Cygwin-and-
Dave Korn wrote:
RGH[*]! FTDIchip are the bane of my life at the moment. Buggy drivers.
I hate them so much .
[*] - I just got back from rebooting a testrig that locked up due to buggy
ftdichip drivers at about the twentytwo-hour point into a twentyseven-hour
testrun. I am not happy.
Nefastor wrote on 25 April 2008 17:26:
> Thanks Dave, I kinda suspected the FTDI drivers for the COM3 issue
One tip I've learned is never, ever, ever, unplug them while you're still
running your terminal software (or whatever) and it's got the port open.
Disconnect, or exit the application, or
astor
--
View this message in context:
http://www.nabble.com/Looking-for-basic-documentation-on-Cygwin-and-Serial-Ports-tp16827997p16897467.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports:
able).
Nefastor
--
View this message in context:
http://www.nabble.com/Looking-for-basic-documentation-on-Cygwin-and-Serial-Ports-tp16827997p16896990.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem re
Nefastor wrote on 24 April 2008 23:08:
> case : My machine has two serial port, one on the MoBo and a USB-serial
> adapter, yet Windows calls them COM1 and COM3.
Or /dev/ttyS0 and /dev/ttyS2, as they'll be known to cygwin.
> Speaking of Windows' DM, it's rather quirky on the serial
> ports :
On 4/24/08, Nefastor <[EMAIL PROTECTED]> wrote:
>
>
> Brian Dessent wrote:
> >
> > Nefastor wrote:
> >
> >> (...) I don't know which of Cygwin's /dev/tty device corresponds to which
> >> serial
> >> port on my PC (that is, I only know the COM port number). I can "sort of
> >> guess" /dev/tty0 is CO
tion on how to retrieve device /
driver info from my program ? That way, worst case scenario, I can have the
program look for the correct port on its own.
Thank you for your time, I know I'm asking for a lot of stuff but I've got
the feeling the answers would be useful to many.:-)
Ne
Nefastor wrote:
> I want to write simple programs which use the serial port (for example, a
> program that will trap and log activity on a serial port, nothing fancy). I
> know how to do that under Linux, and under DOS as well. The problem is I
> don't know which of Cygwin's /dev/tty device corres
27;t hesitate to ask me : my English is a bit lacking.)
--
View this message in context:
http://www.nabble.com/Looking-for-basic-documentation-on-Cygwin-and-Serial-Ports-tp16827997p16827997.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
Unsubscribe info: http://cygwin.c
14 matches
Mail list logo
