From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: Dropped characters in serial connection without flow control
Date: Wed, 28 Oct 2009 11:05:44 -0700 [thread overview]
Message-ID: <20091028180544.GA3523@kroah.com> (raw)
In-Reply-To: <20091028175937.27472.qmail@stuge.se>
On Wed, Oct 28, 2009 at 06:59:37PM +0100, Peter Stuge wrote:
> Peter Stuge wrote:
> > I'm writing a line discipline for a serial port multiplexing
> > hardware
>
> There is no(!) support for flow control in the hardware.
>
> Is there anything I can do to reduce serial port interrupt latency or
> otherwise try to mitigate this in my ldisc or in Linux in general? I
> realize that it will never be quite reliable without any flow
> control.
What's wrong with XON/XOFF? That is a well-known flow control protocol
for systems without hardware support for it.
And since when is adding a UART to a hardware chip expensive these days?
thanks,
greg k-h
next prev parent reply other threads:[~2009-10-28 18:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 17:59 Dropped characters in serial connection without flow control Peter Stuge
2009-10-28 18:05 ` Greg KH [this message]
2009-10-28 18:19 ` Peter Stuge
2009-10-28 18:16 ` Alan Cox
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=20091028180544.GA3523@kroah.com \
--to=greg@kroah.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/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