From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Chuck Ebbert <76306.1226@compuserve.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
sebastien.hinderer@libertysurf.fr
Subject: Re: [Patch] new serial flow control
Date: Fri, 8 Oct 2004 00:08:51 +0200 [thread overview]
Message-ID: <20041007220851.GD2296@bouh.is-a-geek.org> (raw)
In-Reply-To: <20041007212722.G8579@flint.arm.linux.org.uk>
Le jeu 07 oct 2004 à 21:27:22 +0100, Russell King a écrit:
> I can't help but wonder whether moving some of the usual modem line
> status change processing should also be moved into the higher levels.
The more I'm thinking about it, the more I think it's not a good idea:
that would require *every* line discipline to implement hardware flow
control (just like xon/xoff), while I think they shouldn't really care
about it.
The asynchronous ppp ldisc for instance can be used on a serial line,
but can very well be used on a ssh tunnel (in which case rts/cts flow
control has no meaning).
I can understand that xon/xoff processing be implemented in ldiscs
since it is characters stuff, but one can't ask the ldisc to know
details about hardware flow control which depends on the tty it is
used on.
Regards,
Samuel Thibault
next prev parent reply other threads:[~2004-10-07 22:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-05 16:46 Chuck Ebbert
2004-10-05 17:25 ` Samuel Thibault
2004-10-07 19:08 ` Alan Cox
2004-10-07 20:27 ` Russell King
2004-10-07 22:08 ` Samuel Thibault [this message]
2004-10-07 23:10 ` Russell King
2004-10-07 21:43 ` Samuel Thibault
2004-10-07 22:55 ` Samuel Thibault
2004-10-08 18:59 ` Samuel Thibault
-- strict thread matches above, loose matches on Subject: below --
2004-10-07 11:08 Nick Craig-Wood
2004-10-04 22:54 Samuel Thibault
2004-10-04 22:55 ` Samuel Thibault
2004-10-05 22:51 ` Alan Cox
2004-10-06 7:11 ` Sébastien Hinderer
2004-10-06 7:38 ` Samuel Thibault
2004-10-06 13:29 ` Alan Cox
2004-10-07 1:30 ` Stuart MacDonald
2004-10-07 1:47 ` Paul Fulghum
2004-10-07 7:26 ` Sébastien Hinderer
2004-10-07 13:00 ` Alan Cox
2004-10-07 14:28 ` Samuel Thibault
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=20041007220851.GD2296@bouh.is-a-geek.org \
--to=samuel.thibault@ens-lyon.org \
--cc=76306.1226@compuserve.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=sebastien.hinderer@libertysurf.fr \
/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
all inboxes | Powered by JetHome®