> > It looks like I was indeed supposed to use cua, and I can now get a file
> > descriptor. However, I'm still not able to set the baud rate, it's stuck
> > at 19200 whether I try to set it with tty01 or cua01. cua00 corresponds
> > with tty00, which is the serial console, so I shouldn't use that.
On Mon, Jul 7, 2008 at 4:43 PM, Anthony Roberts
<[EMAIL PROTECTED]> wrote:
> It looks like I was indeed supposed to use cua, and I can now get a file
> descriptor. However, I'm still not able to set the baud rate, it's stuck
> at 19200 whether I try to set it with tty01 or cua01. cua00 corresponds
> It looks like I was indeed supposed to use cua, and I can now get a file
> descriptor. However, I'm still not able to set the baud rate, it's stuck
> at 19200 whether I try to set it with tty01 or cua01. cua00 corresponds
> with tty00, which is the serial console, so I shouldn't use that.
BTW, u
> In this case, you need to use the "callout" device for the first serial
> port, /dev/cua00 in this case.
>
> Good luck, see tty(4) or cua(4).
Hi,
Thanks for the response. :)
It looks like I was indeed supposed to use cua, and I can now get a file
descriptor. However, I'm still not able to set
Hi,
In this case, you need to use the "callout" device for the first serial
port, /dev/cua00 in this case.
Good luck, see tty(4) or cua(4).
I'm working with a Portwell NAR-5520 (dmesg follows). These machines have
an LCD on the front that uses a serial port to talk to the OS. I've been
having trouble with these:
# stty 2400 < /dev/tty01
...hangs forever...
^Cksh: cannot open /dev/tty01: Interrupted system call
# stty -f /dev/tty01 240
6 matches
Mail list logo
