sergiotarxz/nuttx
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update ChangeLog

Browse Source
This commit is contained in:
Gregory Nutt 2014-12-13 08:11:32 -06:00
parent d09bb13833
commit dcd6608050
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
ChangeLog
View File

@ -9208,3 +9208,13 @@
and the FS clock enable bits are set in FS mode, then the ARM never 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 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). 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).