Re: [Patch] new serial flow control
From: Alan Cox (alan_at_lxorguk.ukuu.org.uk)
Date: 10/07/04
- Previous message: Aaron Peterson: "Maximum block dev size / filesystem size"
- In reply to: Samuel Thibault: "Re: [Patch] new serial flow control"
- Next in thread: Russell King: "Re: [Patch] new serial flow control"
- Reply: Russell King: "Re: [Patch] new serial flow control"
- Reply: Samuel Thibault: "Re: [Patch] new serial flow control"
- Reply: Samuel Thibault: "Re: [Patch] new serial flow control"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: Samuel Thibault <samuel.thibault@ens-lyon.org> Date: Thu, 07 Oct 2004 20:08:56 +0100
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Previous message: Aaron Peterson: "Maximum block dev size / filesystem size"
- In reply to: Samuel Thibault: "Re: [Patch] new serial flow control"
- Next in thread: Russell King: "Re: [Patch] new serial flow control"
- Reply: Russell King: "Re: [Patch] new serial flow control"
- Reply: Samuel Thibault: "Re: [Patch] new serial flow control"
- Reply: Samuel Thibault: "Re: [Patch] new serial flow control"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
