Re: Blocking read() from a USB->Serial adapter.
- From: floyd@xxxxxxxxxx (Floyd L. Davidson)
- Date: Fri, 24 Nov 2006 21:09:28 -0900
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!)
--
Floyd L. Davidson <http://www.apaflo.com/floyd_davidson>
Ukpeagvik (Barrow, Alaska) floyd@xxxxxxxxxx
.
- Follow-Ups:
- Re: Blocking read() from a USB->Serial adapter.
- From: Grant Edwards
- 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
- Blocking read() from a USB->Serial adapter.
- Prev by Date: Re: Blocking read() from a USB->Serial adapter.
- 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
|