From: Paul Fulghum <paulkf@microgate.com>
To: Stuart MacDonald <stuartm@connecttech.com>
Cc: "'Alan Cox'" <alan@lxorguk.ukuu.org.uk>,
"'Samuel Thibault'" <samuel.thibault@ens-lyon.org>,
"'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, 06 Oct 2004 20:47:31 -0500 [thread overview]
Message-ID: <1097113651.6013.8.camel@at2.pipehead.org> (raw)
In-Reply-To: <043c01c4ac0d$2c8bac80$294b82ce@stuartm>
On Wed, 2004-10-06 at 20:30, Stuart MacDonald wrote:
> RS485 is a driver-transparent electrical interface.
Yes.
This protocol issue is independent of the electrical interface.
> I haven't seen this style of flow control before. What uses it?
terminal visio-braille (TVB)
A device for the sight impaired.
--
Paul Fulghum
paulkf@microgate.com
next prev parent reply other threads:[~2004-10-07 1:48 UTC|newest]
Thread overview: 23+ 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-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 [this message]
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-07 11:08 Nick Craig-Wood
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-04 22:54 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=1097113651.6013.8.camel@at2.pipehead.org \
--to=paulkf@microgate.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 \
--cc=stuartm@connecttech.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.