Let me try this again. Programing the uart directly means directly
manipulating the serial port chip. Programing in c or c++ does not usually
do this, as you normally would open the device/file and simply read or
write to it. In opening the device you need to set it to unbuffered in the
flag
On 2006-06-22 13:55, Andrew Falanga <[EMAIL PROTECTED]> wrote:
> On 6/22/06, Derek Ragona <[EMAIL PROTECTED]> wrote:
> >
> > Kermit may be manipulating the uart directly.
> >
> >Unless you are not getting the uart to flush the characters. I have only
> >had that problem with doing low-level direct
On 6/22/06, David Kelly <[EMAIL PROTECTED]> wrote:
On Thu, Jun 22, 2006 at 12:19:41PM -0600, Andrew Falanga wrote:
> Derek,
>
> No I didn't disable the getty on the port. To be honest, I didn't know
one
> was running.
Its not going to be running by default. Even if it was then it would be
on /
I'm not sure I understand what you mean.
Andy
On 6/22/06, Derek Ragona <[EMAIL PROTECTED]> wrote:
Kermit may be manipulating the uart directly.
Unless you are not getting the uart to flush the characters. I have only
had that problem with doing low-level direct programing. Typically not a
Unfortunately, it looks like getty isn't running on /dev/cuad1. I did the
ps command you suggest below and it apears that getty is only running on the
virtual terminals (ttyvx).
Would you have any idea what it is that kermit is doing differently that I?
Andy
On 6/22/06, Derek Ragona <[EMAIL PR
On Thu, Jun 22, 2006 at 12:19:41PM -0600, Andrew Falanga wrote:
> Derek,
>
> No I didn't disable the getty on the port. To be honest, I didn't know one
> was running.
Its not going to be running by default. Even if it was then it would be
on /dev/ttyd1 not /dev/cuad1. What is supposed to happen
Your code looked OK, but I would add some debugging print statements.
silo overflow is a stack overflow, so you should figure where this is
happening.
The getty may be managing the port IO, which is why I would disable
it. Getty is listening to the port for traffic.
Depending on the OS, so
Derek,
No I didn't disable the getty on the port. To be honest, I didn't know one
was running.
Second, the errors I'm receiving are:
sio1: 2 more silo overflows (total 9)
sio1: 280221 more tty-level buffer overflows (total 576898)
One question I have is, why would kermit able to receive/send
Andy,
Did you kill the getty running on the port?
Are you getting any errors?
-Derek
At 10:28 AM 6/22/2006, Andrew Falanga wrote:
Hello,
I've got a case where I'm writing a simply serial program to send bytes from
one system to another over a serial cable. The program works in Linux
Hello,
I've got a case where I'm writing a simply serial program to send bytes from
one system to another over a serial cable. The program works in Linux, but
when I use it in FreeBSD nothing happens. The program starts and, in the
case of receiving, waits for data to appear on the /dev/cuad1 p
10 matches
Mail list logo