public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
	akpm@osdl.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: [patch 3/4] new serial flow control
Date: Sun, 9 Oct 2005 01:01:53 +0100	[thread overview]
Message-ID: <20051009000153.GA23083@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20051008222711.GA5150@bouh.residence.ens-lyon.fr>

On Sun, Oct 09, 2005 at 12:27:11AM +0200, Samuel Thibault wrote:
> Hi,
> 
> I'm re-opening a somewhat old thread about serial flow control methods:
> 
> Russell King, le Wed 05 Jan 2005 23:53:01 +0000, a ?crit :
> > we have other people
> > who want to use their on-board hardware RS485 flow control options on
> > UARTs for their application, which means we need an RS485 flow control
> > method.  (They can't select it without accessing the hardware directly.)
> > 
> > So, we now seem to have:
> > 
> > 	Standard flow control
> > 	CTVB flow control
> > 	RS485 RTS flow control
> 
> Let's add a new one: Inka braille devices, which uses RTS/CTS as
> acknowledge strobes for each character.
> 
> > I still believe that flow control should be enabled by CRTSCTS, but
> > the flow control personality set by other means.
> > 
> > Therefore, I think this requires further discussion, especially with
> > Alan (who seems to be the tty layer god now) to work out some sort of
> > reasonable interface.
> 
> How could this look like in userspace? Something like
> 
> #define CRTSCTS_RS232 0
> #define CRTSCTS_RS485 1
> #define CRTSCTS_TVB 2
> #define CRTSCTS_INKA 3
> 	int method = CRTSCTS_RS485;
> 	ioctl(fd,TIOCMSFLOWCTRL,&method);
> 
> (and the converse TIOCMGFLOWCTRL)?

I think they should be termios settings - existing programs know how
to handle termios to get what they want.  Why make the situation more
complex for them?

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

  parent reply	other threads:[~2005-10-09  0:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200501052341.j05Nfod27823@mail.osdl.org>
     [not found] ` <20050105235301.B26633@flint.arm.linux.org.uk>
2005-10-08 22:27   ` [patch 3/4] new serial flow control Samuel Thibault
2005-10-08 22:58     ` Samuel Thibault
2005-10-09  0:01     ` Russell King [this message]
2005-10-09  0:21       ` Samuel Thibault
2005-10-09  8:37         ` Russell King
2005-10-09 10:09           ` Samuel Thibault
2005-10-09 11:17             ` Russell King
2005-10-09 11:33               ` Samuel Thibault
2005-10-09 11:44                 ` Samuel Thibault
2005-10-09 23:04                   ` Alan Cox
2005-10-09 13:29           ` 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=20051009000153.GA23083@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=samuel.thibault@ens-lyon.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