From: Theodore Ts'o <tytso@mit.edu>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Tosoni <jp.tosoni@acksys.fr>, linux-serial@vger.kernel.org
Subject: Re: tcdrain / TCSBRK / wait_until_sent delay
Date: Mon, 9 May 2005 11:43:12 -0400 [thread overview]
Message-ID: <20050509154312.GA19091@thunk.org> (raw)
In-Reply-To: <20050509111338.C5674@flint.arm.linux.org.uk>
On Mon, May 09, 2005 at 11:13:38AM +0100, Russell King wrote:
>
> There are many different styles of use of RTS. The conventional one
> and your one are only two. There are more than two, and all of them
> are exclusive. I don't see why you made the above comment, since we
> obviously agree.
>
It's worse than this. Even with the ancient/historic RTS/CTS toggle
approach, I've heard all sorts of different timing constraints. For
example, in some implementations the implementation must wait at
_least_ (or in other cases no more than) some time period before
toggling CTS. The old RS-422 devices were so crufty that they all had
their own idiosyncratic requirements.
My suggestion would be to do this as a new line discpline, and have
the line displine act as a pass-through to the N_TTY line displine for
those things that it doesn't need to do differently.
- Ted
next prev parent reply other threads:[~2005-05-09 15:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-05 15:50 tcdrain / TCSBRK / wait_until_sent delay Andy Parkins
2005-05-05 17:51 ` rich+ml
2005-05-06 8:01 ` Andy Parkins
2005-05-06 19:14 ` rich+ml
2005-05-07 9:35 ` Andy Parkins
2005-05-07 18:09 ` rich+ml
2005-05-09 8:01 ` Andy Parkins
[not found] ` <Pine.LNX.4.58.0505090825470.750@deadrat.localdomain>
2005-05-10 7:44 ` Andy Parkins
2005-05-09 8:16 ` Tosoni
2005-05-09 8:59 ` Russell King
2005-05-09 10:03 ` Tosoni
2005-05-09 10:13 ` Russell King
2005-05-09 15:43 ` Theodore Ts'o [this message]
2005-05-07 10:32 ` Gerald Emig
2005-05-09 9:15 ` Christer Weinigel
2005-05-09 9:22 ` Christer Weinigel
2005-05-09 11:05 ` Andy Parkins
2005-05-09 15:53 ` Andy Parkins
2005-05-09 19:45 ` rich+ml
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=20050509154312.GA19091@thunk.org \
--to=tytso@mit.edu \
--cc=jp.tosoni@acksys.fr \
--cc=linux-serial@vger.kernel.org \
--cc=rmk@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.