From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>
Cc: Chuck Ebbert <76306.1226@compuserve.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Russell King <rmk@arm.linux.org.uk>,
sebastien.hinderer@libertysurf.fr
Subject: Re: [Patch] new serial flow control
Date: Thu, 07 Oct 2004 20:08:56 +0100 [thread overview]
Message-ID: <1097176130.31557.117.camel@localhost.localdomain> (raw)
In-Reply-To: <20041005172522.GA2264@bouh.is-a-geek.org>
On Maw, 2004-10-05 at 18:25, Samuel Thibault wrote:
> No: data actually pass _after_ CTS and RTS are lowered back: the flow control
> only indicate the beginning of one frame.
Ok I've pondered this somewhat. I don't think the hack proposed is the
right answer for this. I believe you should implement a simple line
discipline for this device so that it stays out of the general code.
Right now that poses a challenge but if drivers were to implement
ldisc->modem_change() or a similar callback for such events an ldisc
could then handle many of the grungy suprises and handle them once and
in one place.
Thoughts ?
Alan
next prev parent reply other threads:[~2004-10-07 20:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-05 16:46 [Patch] new serial flow control Chuck Ebbert
2004-10-05 17:25 ` Samuel Thibault
2004-10-07 19:08 ` Alan Cox [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2004-10-07 11:08 Nick Craig-Wood
2004-10-04 22:54 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
2004-10-07 7:26 ` Sébastien Hinderer
2004-10-07 13:00 ` Alan Cox
2004-10-07 14:28 ` Samuel Thibault
2004-10-04 22:55 ` 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=1097176130.31557.117.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=76306.1226@compuserve.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=samuel.thibault@ens-lyon.org \
--cc=sebastien.hinderer@libertysurf.fr \
/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.