public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Chuck McManis <ecos@mcmanis.com>
To: ECOS Discussion Group <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] mysterious behavior in serial ports
Date: Fri, 02 Mar 2007 08:01:00 -0000	[thread overview]
Message-ID: <6.1.2.0.2.20070301235826.05150018@192.168.110.40> (raw)
In-Reply-To: <6.1.2.0.2.20070301233559.050a3cd0@192.168.110.40>

And a bit more information, I went back and enabled nonblocking on the 
serial driver and that fixes the input (basically it starts echoing as soon 
as I type) but output still pauses. I can fix that by putting an 
fflush(stdout); in there but this is not the behavior my user code is 
expecting and as I'm porting a fairly sizable chunk it seems I should be 
able to get this fixed in ecos instead ;-).

That being said I'm rummaging around the implementation of the standard i/o 
library both on FreeBSD and on ecos to see how they differ in this regard...

--Chuck

At 11:39 PM 3/1/2007, Chuck McManis wrote:
>So per Andrews comment I found that yes, I can force /dev/tty0 to be 
>stdin/out (cool) and as long as I talk to Redboot on COM1 first it becomes 
>/dev/ttydiag so no worries about stalling the system by polling the serial 
>port.
... elided


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2007-03-02  8:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-02  7:39 Chuck McManis
2007-03-02  8:01 ` Chuck McManis [this message]
2007-03-05  7:04   ` wang cui

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=6.1.2.0.2.20070301235826.05150018@192.168.110.40 \
    --to=ecos@mcmanis.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).