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]

Intended semantics for syscalls function _read?


   Hello list,

The documentation of this function does not describe how this function is to behave.
Is it blocking, or can it also be non-blocking.
What is the meaning of the return value? Or is it intentionally left ambiguous?
My guess would be:
   >=0  number of characters actually read
         zero meaning: zero characters read.
   < 0  error code (including eof?)

I want to use this function to read from serial/usb ports, using (man 2) read and scanf.
But also to test for the availability of a character on a port: a character_ready function.

Can I use (man 2) read in a non-blocking way? Or is there an other way?
Or should I directly use the _read function to make the character_ready function?

   Thanks in advance,
       Sietse Achterop


PS. I am using newlib as part of the GNU Embedded toolchain for a number of arm systems (stm32f4 based).

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature


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