public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Stuart MacDonald" <stuartm@connecttech.com>
To: "'Alan Cox'" <alan@lxorguk.ukuu.org.uk>,
	"'Samuel Thibault'" <samuel.thibault@ens-lyon.org>
Cc: "'Sébastien Hinderer'" <Sebastien.Hinderer@libertysurf.fr>,
	rmk@arm.linux.org.uk,
	"'Linux Kernel Mailing List'" <linux-kernel@vger.kernel.org>
Subject: RE: [Patch] new serial flow control
Date: Wed, 6 Oct 2004 21:30:04 -0400	[thread overview]
Message-ID: <043c01c4ac0d$2c8bac80$294b82ce@stuartm> (raw)
In-Reply-To: <1097069353.29251.4.camel@localhost.localdomain>

From: Alan Cox
> On Mer, 2004-10-06 at 08:38, Samuel Thibault wrote:
> > No: CRTSCTS is a one-signal-for-each-way flow control: each
> > side of the link tells whether it can receive data. CTVB is a
> > two-signals-for-only-one-way flow control: the device tells when it
> > wants to send data, the PC acknowledges that, and then one frame of
> > data can pass.
> 
> This sounds a lot like RS485 and some other related stuff. I need to
> poke my pet async guru and find out if they are the same thing. If so
> that would be useful.

RS485 is a driver-transparent electrical interface. Unfortunately the
half-duplex and master-slave(s) arrangements require some sort of
token passing to know when they can successfully transmit. This is
usually handled by the apps in some manner, although it's often wanted
to be handled by the serial driver. This could be one method of
signalling, but isn't sufficient to show RS485 operation.

I haven't seen this style of flow control before. What uses it?

..Stu


  reply	other threads:[~2004-10-07  1:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-04 22:54 [Patch] new serial flow control 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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
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
2004-10-07 11:08 Nick Craig-Wood

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='043c01c4ac0d$2c8bac80$294b82ce@stuartm' \
    --to=stuartm@connecttech.com \
    --cc=Sebastien.Hinderer@libertysurf.fr \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    --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