linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: linux-serial@vger.kernel.org
Subject: Re: tcflow(TCOON/TCOOFF) vs. received XON/XOFF characters
Date: Thu, 17 Jul 2014 14:03:17 +0000 (UTC)	[thread overview]
Message-ID: <lq8l35$cfa$1@ger.gmane.org> (raw)
In-Reply-To: 53C7CB1B.3010804@hurleysoftware.com

On 2014-07-17, Peter Hurley <peter@hurleysoftware.com> wrote:

> tcflow(TCOxxx) flow control is independent of IXON flow control.
> The union of both flow states determines if the tty can output;
>
>                       IXON = true        IXON = false
>                    START       STOP
> tcflow(TCOON)      on         off          on
> tcflow(TCOOFF)     off        off          off

Thanks, that's pretty much what I had decided based on tests and
browsing the source code.

Just to confirm:

  tcflow(TCION/TCIOFF): overrides the "input" side of xon/xoff flow
                        control and forces the sending of XON/XOFF.

  tcflow(TCOON/TCOOFF): does not have anything to do with the "output"
                        side of xon/xoff flow control, but controls
                        something completely orthogonal.

That rather counter-intuitive (not that counter-intuitive is exactly a
novel thing when it comes to Unix serial ports).
                        
That rasies this question: what does an application use to control the
"output" side of xon/xoff flow control?  There is a Windows API for
doing that, and I get asked how to do it in Linux.  I always tell them
they can't.

-- 
Grant Edwards               grant.b.edwards        Yow! Oh, I get it!!
                                  at               "The BEACH goes on", huh,
                              gmail.com            SONNY??


  reply	other threads:[~2014-07-17 14:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-16 17:20 tcflow(TCOON/TCOOFF) vs. received XON/XOFF characters Grant Edwards
2014-07-17 13:09 ` Peter Hurley
2014-07-17 14:03   ` Grant Edwards [this message]
2014-07-17 18:18     ` Peter Hurley

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='lq8l35$cfa$1@ger.gmane.org' \
    --to=grant.b.edwards@gmail.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;
as well as URLs for NNTP newsgroup(s).