From: Grant Edwards <grant.b.edwards@gmail.com>
To: linux-serial@vger.kernel.org
Subject: Re: How to disable the transmit FIFO?
Date: Wed, 24 Nov 2010 14:56:55 +0000 (UTC) [thread overview]
Message-ID: <icj93m$9mh$1@dough.gmane.org> (raw)
In-Reply-To: E1PLEkX-0000u5-SZ@palantir.moria.de
On 2010-11-24, Michael Haardt <michael@moria.de> wrote:
>> Specifically, if you use setserial to configure a serial port so that
>> its UART is a 16450, it will force the transmit FIFO to be unused.
>
> I tried that, but no change. Sending a line of 21 characters to the port,
> I see only two trailing edges of CTS, which is consistent with receiving
> three characters by the SBC. The other characters are sent and lost.
>
> The SBC on the other end clears RTS immediatly after receiving a
> character. Linux may send one character at this moment, but that would
> be stored in the receiver buffer and the SBC only asserts RTS if the
> receiver buffer is empty. Instead it sends multiple characters, flooding
> the SBC.
But the Linux box does eventually stop sending, but it takes too long
to stop?
It sounds like you need to buy a serial card that does RTS/CTS flow
control in hardware.
--
Grant Edwards grant.b.edwards Yow! This PORCUPINE knows
at his ZIPCODE ... And he has
gmail.com "VISA"!!
next prev parent reply other threads:[~2010-11-24 14:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 9:15 How to disable the transmit FIFO? Michael Haardt
2010-11-18 16:41 ` Greg KH
2010-11-18 20:01 ` Michael Haardt
2010-11-18 20:05 ` Grant Edwards
2010-11-19 1:25 ` Ted Ts'o
2010-11-19 4:31 ` Grant Edwards
2010-11-24 12:47 ` Michael Haardt
2010-11-24 14:56 ` Grant Edwards [this message]
2010-11-18 20:11 ` Greg KH
2010-11-18 20:58 ` Michael Haardt
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='icj93m$9mh$1@dough.gmane.org' \
--to=grant.b.edwards@gmail.com \
--cc=linux-serial@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 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.