Nonblocking UART driver using _write_r - error if no data was written?

Freddie Chopin
Wed Feb 26 14:58:00 GMT 2014

W dniu 2014-02-26 15:33, MikuslawProxy pisze:
> So, is it a bug that we don't check the write for EAGAIN errno, so we
> can loop on that in fflush?

Take a wider look - you expect your non-blocking driver to block (; Just 
convert your code to be blocking and the problem would be solved.


More information about the Newlib mailing list