This is the mail archive of the newlib@sourceware.org mailing list for the newlib project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

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

From: Freddie Chopin <freddie_chopin at op dot pl>
To: newlib at sourceware dot org
Date: Wed, 26 Feb 2014 15:57:59 +0100
Subject: Re: Nonblocking UART driver using _write_r - error if no data was written?
Authentication-results: sourceware.org; auth=none
References: <CAMym-+z-1ABKQnJaR_eKDTxqk_+0ZgeGdnq_++efJGTBy6o2yA at mail dot gmail dot com> <CAMym-+wVa4HiMNj_LbriWV1WnroxNuNYPnkAe_K24g7EFiMk0Q at mail dot gmail dot com> <530DD434 dot 1 at op dot pl> <CAMym-+yqCAZ3wx8r+3Zijg-DagdzpFbsMs_UJd=UnCYb0USdKw at mail dot gmail dot com>

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 (; Justconvert your code to be blocking and the problem would be solved.


Regards,
FCh

Follow-Ups:
- Re: Nonblocking UART driver using _write_r - error if no data was written?
  - From: MikuslawProxy

References:
- Nonblocking UART driver using _write_r - error if no data was written?
  - From: MikuslawProxy
- Re: Nonblocking UART driver using _write_r - error if no data was written?
  - From: MikuslawProxy
- Re: Nonblocking UART driver using _write_r - error if no data was written?
  - From: Freddie Chopin
- Re: Nonblocking UART driver using _write_r - error if no data was written?
  - From: MikuslawProxy

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]