From: Gary Thomas <gary@mlbassoc.com>
To: Ken Yee <kenkyee@excite.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Re: select doesn't work on stdin?
Date: Mon, 19 Nov 2012 17:56:00 -0000 [thread overview]
Message-ID: <50AA72D4.9090209@mlbassoc.com> (raw)
In-Reply-To: <20121119110802.31170@web007.roc2.bluetie.com>
On 2012-11-19 09:08, Ken Yee wrote:
> Gary Thomas wrote:
>> Have you tried using a serial port (not the diagnostic console)?
>> The problem with the diag port is that it is blocking which does
>> not play nice with select()
>
> Unfortunately, we're out of serial ports on our system. We only have 3. 1 goes to a modem, 1 is used for board-board comms, and the 3rd is the console port which we have shared w/ the diag port (eCos forces you to assign the diag port to a serial port and you can't assign it to /dev/null).
Not exactly true - you can use the serial driver (interrupt driven, etc)
alongside the polled diag driver, at least for output. I've done it
on many occasions and it works just fine.
>
> I can do ioctl w/ the FNONBIO flag to get it to run in non-blocking mode, but it only sees 1 in 18 characters (you hit the same key 17-18 times before one value gets to the read character function)-:
>
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
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:[~2012-11-19 17:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 16:09 Ken Yee
2012-11-19 17:56 ` Gary Thomas [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-11-30 14:49 Ken Yee
2012-11-15 21:16 Ken Yee
2012-11-15 21:33 ` Gary Thomas
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=50AA72D4.9090209@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=kenkyee@excite.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).