Date: Mon, 5 Dec 2005 11:28:22 -0800 From: Aaron Glenn <aaron.glenn@gmail.com> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-sparc64@freebsd.org Subject: Re: serial ports on the Ultra 5 Message-ID: <18f601940512051128i142fd714g22004d8452cff29a@mail.gmail.com> In-Reply-To: <200512051354.06372.jhb@freebsd.org> References: <18f601940512051025g71b9fc29y4ae37eb3ce2629df@mail.gmail.com> <200512051354.06372.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/5/05, John Baldwin <jhb@freebsd.org> wrote:
>
> You don't use sab(4) anymore, but uart(4).
I had a suspicion that was the case, but couldn't confirm it.
>
> Here are your SAB ports. /dev/ttyu0 and /dev/ttyu1
Then something more sinister is at work here. A 'cu -l /dev/ttyu0'
will "connect" me, however I get no prompt, and not input or output
seems to be passed to the console port. All input gets dumped to the
shell I executed the cu command from, *after* I kill the first (lowest
pid) cu process.
Example:
yang# ps -ax | grep ttyu
687 ?? I 0:00.01 /usr/libexec/getty std.9600 ttyu1
688 u0 Is+ 0:00.01 /usr/libexec/getty std.9600 ttyu0
741 p0 R+ 0:00.01 grep ttyu
yang# cu -l /dev/ttyu1 -s 9600
Connected
*hit enter a few times, type hello john, then kill the first cu
process from another shell*
yang#
yang#
yang#
yang#
yang#
yang#
yang# hello john
hello: Command not found.
yang#
Reading the handbook section on serial communications again, I don't
see anything wrong. I'll be the first to admit this type of stuff is
uncharted territory for me. If I skipped some required reading on the
subject, please don't hesitate to point me to it.
Regards,
aaron.glenn
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?18f601940512051128i142fd714g22004d8452cff29a>
