Re: Blocking read() from a USB->Serial adapter.
- From: floyd@xxxxxxxxxx (Floyd L. Davidson)
- Date: Fri, 24 Nov 2006 15:54:24 -0900
Charles Sullivan <cwsulliv@xxxxxxxxxxxx> wrote:
A blocking read() of more than one character from an actual RS232 serial
port returns when the number of characters specified has been read.
Not necessarily true.
However I've found that a blocking read() of more than one character from
a USB->Serial adapter reads only the first character before returning and
I have to loop to read all the characters.
Which makes it the same as a regular port. There may well be timing
differences though, I don't know.
I've tried this with several different USB->Serial adapters with several
different Linux kernel versions, 2.4 and 2.6, all with the same result.
Is this a Linux bug, or is there something extra I need to do in setting
up the port in my code?
Post the code you use to configure your port. It isn't really
possible to know what should be happening without looking at
what your configuration is.
--
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: Charles Sullivan
- Re: Blocking read() from a USB->Serial adapter.
- References:
- Blocking read() from a USB->Serial adapter.
- From: Charles Sullivan
- Blocking read() from a USB->Serial adapter.
- Prev by Date: Re: Blocking read() from a USB->Serial adapter.
- Next by Date: Re: C++: conditional static data member possible?
- 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
|