From: Theodore Tso <tytso@mit.edu>
To: Grant Edwards <grante@visi.com>
Cc: linux-serial@vger.kernel.org
Subject: Re: Enabling auto RS485 half-duplex control
Date: Thu, 18 Dec 2008 23:10:42 -0500 [thread overview]
Message-ID: <20081219041042.GA20215@mit.edu> (raw)
In-Reply-To: <gidri8$7i6$1@ger.gmane.org>
On Thu, Dec 18, 2008 at 03:51:36PM +0000, Grant Edwards wrote:
> Yes there are. The standard is that RTS is asserted when one
> whishes to transmit (and de-asserted when one has finished
> transmitting). Optionally, one waits for CTS to be asserted
> before transmitting. Isn't that the definition of RTS and CTS
> that's in the standard?
There's a standard, which is not necessarily well adhered to. Heck,
full-duplex RTS/CTS standard was used by thousands if not millions of
modems in flagrent violation of the RS-232 standard for some 10 years
or more before TIA-232-E was released and bowed to reality.
I know I received all sorts of requests for very strange
implementations of half-duplex, with people sending me product specs
with all manner of requirements, both in terms of which RS-232 lines
were used (which may have been confusions caused by the fact that many
systems ship with random and wondrous DB9->DB25 cables, or strange
DTE/DCE conversion cables), but also in terms of mutually exclusive
requirements in terms of minimum and maximum turnaround times.
Someday when I'm board I can try to dig the requests out of the
archives, but I can definitely say that people asked for very strange
things, much of which was not in the standard (and as I pointed out,
until 1990 traditional full-duplex RTS/CTS hardware flow control was
not recognized by the RS-232 standard either).
- Ted
next prev parent reply other threads:[~2008-12-19 4:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-17 21:24 Enabling auto RS485 half-duplex control Matthias Fuchs
2008-12-18 3:32 ` Theodore Tso
2008-12-18 5:59 ` Matthias Fuchs
2008-12-18 15:51 ` Grant Edwards
2008-12-19 4:10 ` Theodore Tso [this message]
2008-12-18 9:35 ` Wolfram Sang
2008-12-18 23:42 ` Matthias Fuchs
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=20081219041042.GA20215@mit.edu \
--to=tytso@mit.edu \
--cc=grante@visi.com \
--cc=linux-serial@vger.kernel.org \
/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