Re: [PATCH] Correctly flush 8250 buffers, notify ldisc of linestatus changes.

From: David Woodhouse
Date: Tue Nov 09 2004 - 09:41:57 EST


On Tue, 2004-11-09 at 11:15 +0000, Alan Cox wrote:
> This is the wrong way to do it. I've been trying this and discarded it.
> The problem is that data arrival is asynchronous to the event which
> means you've not got a clue how to combine the status change and the
> data stream. This in itself makes the whole feature useless.
>
> Modem changes have to go inline with the data just like break and
> parity.

That's not the problem I'm trying to solve. I'm interested in the
transmission path. I have a shared bus, much like CAN, with automatic
contention detection -- if I transmit a 0 while someone else transmits a
1, the adapter automatically aborts its transmission and asserts CTS for
a while. I need to respond to CTS by immediately stopping my own
transmission -- otherwise when the adapter goes back into the normal
state it'll start transmitting again half way through my original
packet.

--
dwmw2

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/