From: Jonathan Larmour <jlarmour@redhat.com>
To: Andreas.Karlsson@combitechsystems.com
Cc: ecos-discuss@sourceware.cygnus.com, aeb@arm.com
Subject: Re: [ECOS] UART communication
Date: Wed, 06 Sep 2000 10:01:00 -0000 [thread overview]
Message-ID: <39B67876.B64D21FD@redhat.com> (raw)
In-Reply-To: <2253171AF143D21185A60000F8FA748B0229A950@pluto.combitech.se>
Andreas.Karlsson@combitechsystems.com wrote:
> > Can you clarify what you mean by CTS/RTS enabled? How did you
> > enable this?
>
> I enabled it with the cyg_io_set_config-function like this:
>
[snip]
> settings_buf.flags=CYG_SERIAL_FLAGS_RTSCTS; //enable CTS/RTS
I think you should find that setting this has no effect, which is why you
are seeing overruns. If you update to eCos from CVS, you will find that
"real" support for hardware flow control has been added to the generic
layer, although the only device driver that uses it currently is the ARM
PID serial driver.
However, it would not be difficult to make the same changes to the AEB
serial driver. Perhaps you should consider that?
Or if you update to CVS, you could try the software (XON/XOFF) flow control
which should "just work".
Jifl
--
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow." || These opinions are all my own fault
next prev parent reply other threads:[~2000-09-06 10:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-05 22:32 Andreas.Karlsson
2000-09-06 10:01 ` Jonathan Larmour [this message]
2000-09-07 0:25 ` Jesper Skov
-- strict thread matches above, loose matches on Subject: below --
2000-09-06 10:21 Andreas.Karlsson
2000-09-06 10:31 ` Jonathan Larmour
2000-09-05 6:16 Andreas.Karlsson
2000-09-05 8:52 ` Dave Airlie
2000-09-05 9:03 ` Gary Thomas
2000-09-05 9:04 ` 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=39B67876.B64D21FD@redhat.com \
--to=jlarmour@redhat.com \
--cc=Andreas.Karlsson@combitechsystems.com \
--cc=aeb@arm.com \
--cc=ecos-discuss@sourceware.cygnus.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).