Openmoko Bug #2180: stable-tracking: 'rxserr' UART messages
Openmoko Public Trac
bugs at docs.openmoko.org
Tue Feb 3 23:56:05 CET 2009
#2180: stable-tracking: 'rxserr' UART messages
-----------------------------+----------------------------------------------
Reporter: laforge | Owner: openmoko-kernel
Type: defect | Status: new
Priority: high | Milestone: FSO
Component: System Software | Version:
Severity: major | Keywords: gps s3x24xx_serial rxerr
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by andy):
I looked at /dev/ttySAC0 with stty on GTA02 / FSO and the crtscts flag is
not set on it.
Quite aside from interrupt latencies, it should actually be impossible to
get RX FIFO overrun as seen by the RX UART anyway, when the UART is
dealing with the handshakes in hardware and the other side is honouring
them. It won't help with GPS case but that's of a different level of
symptom if we trash the occasional RX sentence compared to destroying the
GSM mux.
I confirmed that if we set it, with stty -F /dev/ttyUSB0 crtscts, then the
appropriate bit in the UART regs gets set to enable hardware management of
RTS.
What's the crtscts state on the glofiish ttySAC?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2180#comment:8>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
More information about the buglog
mailing list