From: Jesper Skov <jskov@redhat.com>
To: Jonathan Larmour <jlarmour@redhat.com>
Cc: Andreas.Karlsson@combitechsystems.com,
ecos-discuss@sourceware.cygnus.com, aeb@arm.com
Subject: Re: [ECOS] UART communication
Date: Thu, 07 Sep 2000 00:25:00 -0000 [thread overview]
Message-ID: <otd7igvf2t.fsf@thinktwice.zoftcorp.dk> (raw)
In-Reply-To: <39B67876.B64D21FD@redhat.com>
>>>>> "Jonathan" == Jonathan Larmour <jlarmour@redhat.com> writes:
Jonathan> 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:
>>
Jonathan> [snip]
>> settings_buf.flags=CYG_SERIAL_FLAGS_RTSCTS; //enable CTS/RTS
Jonathan> I think you should find that setting this has no effect,
Jonathan> which is why you are seeing overruns. If you update to eCos
Jonathan> from CVS, you will find that "real" support for hardware
Jonathan> flow control has been added to the generic layer, although
Jonathan> the only device driver that uses it currently is the ARM PID
Jonathan> serial driver.
Jonathan> However, it would not be difficult to make the same changes
Jonathan> to the AEB serial driver. Perhaps you should consider that?
I'm plotting on restructuring the 16450/1655x serial drivers just as I
have just done with the SH SCI/SCIF serial drivers.
I haven't looked into all the details yet, but I believe I should be
able to make a generic 16450/1655x serial driver which is shared
between all the platforms that presently have a dedicated driver for
such a beast. This would affect at least PID, Cogent and AEB -
possibly other platforms as well.
I would base that reorg on the PID driver, thus extending the current
PID BREAK+CTS/RTS support to the other affected platforms.
By the looks of things, however, I wouldn't get around to that for
some weeks, so changing the AEB driver would probably be a good (and
necessary) short term fix.
Jesper
next prev parent reply other threads:[~2000-09-07 0:25 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
2000-09-07 0:25 ` Jesper Skov [this message]
-- 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=otd7igvf2t.fsf@thinktwice.zoftcorp.dk \
--to=jskov@redhat.com \
--cc=Andreas.Karlsson@combitechsystems.com \
--cc=aeb@arm.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=jlarmour@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).