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 it.
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 Cygwin ?
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 ?)
Nefastor
--
View this message in context:
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 paste at the
end of this message. The program is based
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 paste at the
end
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 : I
NightStrike wrote:
What motherboard do you have? It's always possible that there is a
riser pinout for a serial port somewhere in the front of the board for
connection to a front panel mount.
No, I checked for that. Besides, this port would appear in Windows' device
manager even if it
Thanks Dave, I kinda suspected the FTDI drivers for the COM3 issue (I've seen
worse : once, the COM port number would be incremented every time the cable
was unplugged and replugged). Unfortunately I'm stuck with FTDI chips as
they are, AFAIK, the only USB-to-serial adapters I can buy as chips
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
Dave Korn wrote:
RGH[*]! FTDIchip are the bane of my life at the moment. Buggy drivers.
I hate them so much spit.
[*] - 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
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 COM1, but that's a guess, and I'd prefer some
certainty.
Cygwin works the
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 COM1, but that's a guess,
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
13 matches
Mail list logo
