Re: Blocking read() from a USB->Serial adapter.
- From: Grant Edwards <grante@xxxxxxxx>
- Date: Sat, 25 Nov 2006 14:16:58 -0000
On 2006-11-25, Floyd L. Davidson <floyd@xxxxxxxxxx> wrote:
Grant Edwards <grante@xxxxxxxx> wrote:
On 2006-11-25, Charles Sullivan <cwsulliv@xxxxxxxxxxxx> wrote:
If that's the case, then that answers my questions. I thought
blocking meant blocking until the specified number of
characters is read, or until the read is interrupted.
Or until the driver decides to return for whatever reason it
chooses. On success, you're guaranteed a minimum of one byte.
Maybe. (Maybe not too!)
There's the case where the file is at EOF. Is there another
case where read() will return success with 0 bytes?
--
Grant Edwards
grante@xxxxxxxx
.
- Follow-Ups:
- Re: Blocking read() from a USB->Serial adapter.
- From: jasen
- Re: Blocking read() from a USB->Serial adapter.
- From: Rainer Weikusat
- Re: Blocking read() from a USB->Serial adapter.
- From: Floyd L. Davidson
- Re: Blocking read() from a USB->Serial adapter.
- References:
- Blocking read() from a USB->Serial adapter.
- From: Charles Sullivan
- Re: Blocking read() from a USB->Serial adapter.
- From: Floyd L. Davidson
- Re: Blocking read() from a USB->Serial adapter.
- From: Charles Sullivan
- Re: Blocking read() from a USB->Serial adapter.
- From: Grant Edwards
- Re: Blocking read() from a USB->Serial adapter.
- From: Floyd L. Davidson
- Blocking read() from a USB->Serial adapter.
- Prev by Date: Re: bind() vs netstat
- Next by Date: Re: Signals and threads
- Previous by thread: Re: Blocking read() from a USB->Serial adapter.
- Next by thread: Re: Blocking read() from a USB->Serial adapter.
- Index(es):
Relevant Pages
|