[Gllug] re: uart overrun problem

[t.clarke]

A search on the web reveals a setserial package at sourceforge whic has amongst
other features a 'latency' feature (which is presumably controlled by the rx
trigger level).   You could try downloading, compiling, and using this.
Setting a 'low latency' may then cure the problem.

However, the question still remains as to why this is happening anyway:
since uart overruns are simply due to the cpu not being able to clear the
receive buffer on the uart fast enough, the possibilities would seem to be:
a) running the serial line too fast
b) cpu too slow
c) cpu overloaded with other non-interruptible load
d) crap uart with too small a buffer (any decent mobo should be using a 16550
   or compatible uart)
e) problems with the serial driver code ??
f) shared interrupt not being handled efficiently ??

I have a vague feeling that the driver reports on receiver buffer overruns
- available by interrogating the appropriate /proc filesystem entry.

A post containing details of your hardware/o-s config might be helpful to
others to assist.

Tim

-- 
Gllug mailing list  -  Gllug at linux.co.uk
http://list.ftech.net/mailman/listinfo/gllug