From: "Dave Airlie" <airlied@parthus.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] short reads on serial port..
Date: Thu, 26 Oct 2000 09:59:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.21.0010261803210.6680-100000@platinum.limerick.sslinc.com> (raw)
Does eCos support short reads? .. I want to read from the serial port for
a max len of 127 bytes, but if there is nothing there I want to
block until something appears .... I suppose I want to use select. .. but
I don't want to use select :-).....
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...
Is there another way?
Thanks,
Dave.
--
David Airlie, Software Engineer, Parthus Technologies plc.,
Mary Rosse Centre, National Tech Park, Limerick, Ireland.
t: +353-61-508116 / f: +353-61-508101 / David.Airlie@parthus.com
next reply other threads:[~2000-10-26 9:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-26 9:59 Dave Airlie [this message]
2000-10-26 12:17 ` Jonathan Larmour
2000-10-26 12:57 ` Grant Edwards
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=Pine.LNX.4.21.0010261803210.6680-100000@platinum.limerick.sslinc.com \
--to=airlied@parthus.com \
--cc=ecos-discuss@sources.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).