From: Grant Edwards <grante@visi.com>
To: Jonathan Larmour <jlarmour@redhat.com>
Cc: Dave Airlie <airlied@parthus.com>, ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] short reads on serial port..
Date: Thu, 26 Oct 2000 12:57:00 -0000 [thread overview]
Message-ID: <20001026145902.A17901@visi.com> (raw)
In-Reply-To: <39F8832A.F2AFAAF0@redhat.com>
On Thu, Oct 26, 2000 at 08:16:58PM +0100, Jonathan Larmour wrote:
> > Should I use select, what does it drag in the way of extra stuff to my
> > build ... I don't want to have to add POSIX stuff really...
>
> Um, serial reads do block by default. If you want to wait on multiple
> devices but avoid select, you could use multiple threads using blocking
> reads, which then signal your original thread when data arrives.
Does the serial driver support select?
--
Grant Edwards
grante@visi.com
next prev parent reply other threads:[~2000-10-26 12:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-26 9:59 Dave Airlie
2000-10-26 12:17 ` Jonathan Larmour
2000-10-26 12:57 ` Grant Edwards [this message]
2000-10-26 13:04 ` Jonathan Larmour
2000-10-26 13:01 ` Dave Airlie
2000-10-26 13:09 ` Jonathan Larmour
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20001026145902.A17901@visi.com \
--to=grante@visi.com \
--cc=airlied@parthus.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=jlarmour@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).