From: Paul Fulghum <paulkf@microgate.com>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] SIIG 8-port serial boards support
Date: Fri, 17 Feb 2006 15:27:44 -0600 [thread overview]
Message-ID: <43F63FD0.3060300@microgate.com> (raw)
In-Reply-To: <20060217200213.GA13502@flint.arm.linux.org.uk>
Russell King wrote:
> So, there are three distinct flow control scenarios:
So I'm clear on how you interpret these,
am I correct with the following?
> - conventional RTS/CTS
RTS active = ready to receive
CTS active = allowed to send
> - alternative RTS/CTS
RTS active = on before send, off after send
CTS active = allowed to send
> - RS485
RTS active = on before send, off after send (RTS enables driver)
CTS ignored (2 wire mode, no CTS)
So maybe the extra control fields would be:
CRTSONTX - RTS on before send, off after send
CTXONCTS - wait for CTS before sending
--
Paul Fulghum
Microgate Systems, Ltd.
next prev parent reply other threads:[~2006-02-17 21:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 8:25 [PATCH] SIIG 8-port serial boards support Andrey Panin
2006-01-24 21:01 ` Russell King
2006-02-02 10:26 ` Russell King
2006-02-02 13:27 ` Andrey Panin
[not found] ` <20060202201734.GA17329@flint.arm.linux.org.uk>
2006-02-03 9:13 ` Andrey Panin
2006-02-03 9:24 ` Russell King
2006-02-17 11:39 ` Andrey Panin
2006-02-17 20:02 ` Russell King
2006-02-17 20:14 ` Russell King
2006-02-17 21:27 ` Paul Fulghum [this message]
2006-02-17 21:39 ` Russell King
2006-02-17 21:52 ` Paul Fulghum
-- strict thread matches above, loose matches on Subject: below --
2006-02-17 20:32 Kilau, Scott
2006-02-17 21:26 ` Russell King
2006-02-17 22:25 linux
2006-02-17 22:39 ` Russell King
2006-02-17 23:11 ` Paul Fulghum
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=43F63FD0.3060300@microgate.com \
--to=paulkf@microgate.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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