From: David Woodhouse <dwmw2@infradead.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andrew Morton <akpm@osdl.org>,
rmk@arm.linux.org.uk,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Correctly flush 8250 buffers, notify ldisc of line status changes.
Date: Tue, 09 Nov 2004 14:39:15 +0000 [thread overview]
Message-ID: <1100011155.4542.139.camel@hades.cambridge.redhat.com> (raw)
In-Reply-To: <1099998926.15462.21.camel@localhost.localdomain>
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
prev parent reply other threads:[~2004-11-09 14:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-05 13:06 David Woodhouse
2004-11-05 13:08 ` David Woodhouse
2004-11-09 9:22 ` Andrew Morton
2004-11-09 11:07 ` David Woodhouse
2004-11-09 11:15 ` Alan Cox
2004-11-09 13:28 ` Russell King
2004-11-09 13:17 ` Alan Cox
2004-11-09 14:39 ` David Woodhouse
2004-11-09 13:49 ` Alan Cox
2004-11-09 14:47 ` Russell King
2004-11-09 14:47 ` Alan Cox
2004-11-13 18:10 ` Russell King
2004-11-13 20:52 ` Alan Cox
2004-11-13 22:40 ` Nicolas Pitre
2004-11-09 14:39 ` David Woodhouse [this message]
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=1100011155.4542.139.camel@hades.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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
all inboxes | Powered by JetHome®