public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Fulghum <paulkf@microgate.com>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: linux@horizon.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] SIIG 8-port serial boards support
Date: Fri, 17 Feb 2006 17:11:32 -0600	[thread overview]
Message-ID: <43F65824.8050204@microgate.com> (raw)
In-Reply-To: <20060217223938.GA24170@flint.arm.linux.org.uk>

Russell King wrote:
> On Fri, Feb 17, 2006 at 05:25:29PM -0500, linux@horizon.com wrote:
>>CRTSCTS	CRTSHDX	Handshaking
>>off	off	None.  (Computer might as well send RTS< but ignores CTS)
>>on	off	Full-duplex RTS/CTS
>>off	on	RS-485.  CTS ignored, RTS enables transmitter.
>>on	on	RS-232 half-duplex.  RTS is request, CTS is grant.
...
> Also, !CRTSCTS is most likely the state used by any existing userspace
> RS485 implementations which would be using TIOCMBIC/TIOCMBIS to
> manipulate the RTS signal, so having RTS manipulated in this state
> would be an undesirable change of behaviour.
> 
> Hence, I'm very much in favour of having the default flow control
> method to preserve in as many ways as possible existing behaviour
> for CRTSCTS.

It is important to maintain the "driver doesn't touch RTS/CTS"
semantics without regard to other (new) control flags.
An application might read the existing termios, and modify only
the bits it is aware of without verifying that new bits are zero.
CFLOWXXX also maintains a free setting for future flow modes, such as:
CFLOWZEN = alter RTS based on /dev/random

--
Paul Fulghum
Microgate Systems, Ltd

  reply	other threads:[~2006-02-17 23:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-17 22:25 [PATCH] SIIG 8-port serial boards support linux
2006-02-17 22:39 ` Russell King
2006-02-17 23:11   ` Paul Fulghum [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-02-17 20:32 Kilau, Scott
2006-02-17 21:26 ` Russell King
2006-01-24  8:25 Andrey Panin
2006-01-24 21:01 ` Russell King
2006-02-02 10:26   ` Russell King
2006-02-02 13:27     ` Andrey Panin
     [not found]       ` <20060202201734.GA17329@flint.arm.linux.org.uk>
2006-02-03  9:13         ` Andrey Panin
2006-02-03  9:24           ` Russell King
2006-02-17 11:39             ` Andrey Panin
2006-02-17 20:02               ` Russell King
2006-02-17 20:14                 ` Russell King
2006-02-17 21:27                 ` Paul Fulghum
2006-02-17 21:39                   ` Russell King
2006-02-17 21:52                     ` Paul Fulghum

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=43F65824.8050204@microgate.com \
    --to=paulkf@microgate.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@horizon.com \
    --cc=rmk+lkml@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox