public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
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:10:34 +0100	[thread overview]
Message-ID: <20041008001034.H8579@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20041007220851.GD2296@bouh.is-a-geek.org>; from samuel.thibault@ens-lyon.org on Fri, Oct 08, 2004 at 12:08:51AM +0200

On Fri, Oct 08, 2004 at 12:08:51AM +0200, Samuel Thibault wrote:
> 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.

Please note that I said "into the higher levels" and not "into line
disciplines" - I completely agree with you.  For the general case,
line disciplines do not need to know that the CTS signal has been
deasserted, or that DCD has deasserted - these are all meaningless
to the vast majority.

There are special cases though, such as the one being discussed in
this thread, where it does make sense for the line discipline to
override the default behaviour.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
                 2.6 Serial core

  reply	other threads:[~2004-10-07 23:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-05 16:46 [Patch] new serial flow control 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
2004-10-07 23:10         ` Russell King [this message]
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=20041008001034.H8579@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --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