diff options
| author | Gregory Nutt <gnutt@nuttx.org> | 2014-12-13 08:11:32 -0600 |
|---|---|---|
| committer | Gregory Nutt <gnutt@nuttx.org> | 2014-12-13 08:11:32 -0600 |
| commit | 9a632705357ece9571855f8be8f4c23f34629e52 (patch) | |
| tree | 6e80ce8e361638f023db6bdc4ceeab91d99bb1aa /nuttx/ChangeLog | |
| parent | fecb9040d0e54baf14b729e556a832febfe8229e (diff) | |
| download | nuttx-9a632705357ece9571855f8be8f4c23f34629e52.tar.gz nuttx-9a632705357ece9571855f8be8f4c23f34629e52.tar.bz2 nuttx-9a632705357ece9571855f8be8f4c23f34629e52.zip | |
Update ChangeLog
Diffstat (limited to 'nuttx/ChangeLog')
| -rwxr-xr-x | nuttx/ChangeLog | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/nuttx/ChangeLog b/nuttx/ChangeLog index 234edd776..7e1d6b69b 100755 --- a/nuttx/ChangeLog +++ b/nuttx/ChangeLog @@ -9208,3 +9208,13 @@ and the FS clock enable bits are set in FS mode, then the ARM never awakens from WFI due to a chip issue. This is only an issue if you are using the internal PHY. From Ken Pettit (2012-12-13). + * drivers/serial/serial.c: In case a thread is doing a blockingi + operation (e.g. read()) on a serial device, while it is being + terminated by pthread_cancel(), then uart_close() gets called, but + the semaphore (dev->recv.sem in the above example) is still blocked. + This means that once the serial device is opened next time, data will + arrive on the serial port (and driver interrupts handled as normal), + but the received characters never arrive in the reader thread. + Th problem was fixed by re-initializing the semaphores on the last + uart_close() on the device. From Harald Welte (2014-12-13). + |