diff options
author | Stefan Zegenhagen <[email protected]> | 2013-05-29 16:50:43 +0200 |
---|---|---|
committer | Björn-Egil Dahlberg <[email protected]> | 2013-07-22 11:27:36 +0200 |
commit | 02986f8623e02b5afba41f7f593710e74b3c8a7f (patch) | |
tree | 1e5a14930b7ab7526ceb20b93de3b070be25b1bc /lib/cosTime | |
parent | 3c12a584fc8b88625902342747c7b3d8a3eb06b3 (diff) | |
download | otp-02986f8623e02b5afba41f7f593710e74b3c8a7f.tar.gz otp-02986f8623e02b5afba41f7f593710e74b3c8a7f.tar.bz2 otp-02986f8623e02b5afba41f7f593710e74b3c8a7f.zip |
Fix changing terminal parameters in to_erl
One of our devices does not like 'to_erl' to be run over a serial port.
When to_erl is started, we see "Attaching to /tm<0xFF>" being printed
and the device then refuses to accept any input. Occasionally, we have
seen a linux kernel error message "serial8250: too much work for irq16"
simultaneously. After some debugging we found out that cause is a call
to tcsetattr() by to_erl, immediately preceeded by some printf().
The UART in our device doesn't like hardware parameters to be changed
while output is concurrently active. In fact, the GNU libc manual also
mentions that it might be dangerous to change UART hardware parameters
when a transmission is ongoing.
The patch attached to this e-mail changes the behaviour of to_erl to use
TCSADRAIN instead of TCSANOW when changing terminal parameters. This
makes the serial driver wait for the output queues to be empty before
applying the terminal parameter change.
Diffstat (limited to 'lib/cosTime')
0 files changed, 0 insertions, 0 deletions