From: Andrew Lunn <andrew@lunn.ch>
To: aprakash@tataelxsi.co.in
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Serial Port , Raw Mode using cyg_io_read
Date: Wed, 06 Jul 2005 10:49:00 -0000 [thread overview]
Message-ID: <20050706104943.GM30398@lunn.ch> (raw)
In-Reply-To: <14445914377f.14377f144459@vsnl.net>
On Wed, Jul 06, 2005 at 03:06:33PM +0500, aprakash@tataelxsi.co.in wrote:
> Ok. Thanks andrew...
>
> Is there any function or call to know, howmany bytes available to read in my serial buffer ?.
Yes, it is described in the documentation, which you might want to
read.
http://ecos.sourceware.org/docs-latest/ref/io-serial-driver-details.html
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2005-07-06 10:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-06 10:27 aprakash
2005-07-06 10:49 ` Andrew Lunn [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-06 8:41 Annamalai Prakash
2005-07-06 9:02 ` Edgar Grimberg
2005-07-06 9:18 ` Annamalai Prakash
2005-07-06 9:30 ` Andrew Lunn
2005-07-06 9:33 ` Edgar Grimberg
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=20050706104943.GM30398@lunn.ch \
--to=andrew@lunn.ch \
--cc=aprakash@tataelxsi.co.in \
--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).