From: Dan Malek <dan@netx4.com>
To: Marcus Sundberg <marcus@cendio.se>
Cc: "Brown, David (dbrown03)" <DBrown03@harris.com>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: Is it normal for serial ports to drop characters at the end?
Date: Wed, 03 May 2000 15:53:48 -0400 [thread overview]
Message-ID: <391083CC.7E08CC54@embeddededge.com> (raw)
In-Reply-To: veya5rv3gj.fsf@lipta.cendio.se
Marcus Sundberg wrote:
> Right on target.
> rs_8xx_wait_until_sent() will wait for the *first* buffer descriptor
> to be finished, instead of waiting for the last one as it should.
> This patch fixes that problem:
That's part of it, but we also need to perform a graceful shutdown
of the port so we wait until the hardware FIFOs are empty. Waiting
for the buffer descriptor just means the CPM moved the last data
from the buffer, not that it has gone out the wire.
I thought I did this once.....but, why are you closing devices anyway :-).
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-05-03 19:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-03 15:30 Is it normal for serial ports to drop characters at the end? Brown, David (dbrown03)
2000-05-03 19:27 ` Marcus Sundberg
2000-05-03 19:53 ` Dan Malek [this message]
2000-05-03 20:05 ` Marcus Sundberg
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=391083CC.7E08CC54@embeddededge.com \
--to=dan@netx4.com \
--cc=DBrown03@harris.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=marcus@cendio.se \
/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;
as well as URLs for NNTP newsgroup(s).