From: "David S. Miller" <davem@davemloft.net>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH] SunSAB console problems in 2.6.x
Date: Fri, 27 Aug 2004 23:39:03 +0000 [thread overview]
Message-ID: <20040827163903.0141f798.davem@davemloft.net> (raw)
In-Reply-To: <20040825233247.237c1fb1.davem@redhat.com>
On Sat, 28 Aug 2004 00:34:12 +0100
"C.Newport" <crn@netunix.com> wrote:
> FWIW, I saw this problem in a completely different non-linux context
> a while ago. It is possible, if the code is tight enough, for modern fast
> processors to overwrite the character in a USART transmit register
> before the USART has moved it down the internal buffer.
> Introducing a suitable delay fixed it.
We protect this by spinning on the sunsab control register waiting
for it to say "character sent and FIFO empty, ready for next char".
It's busted udelay() on sparc64 which is causing this problem.
next prev parent reply other threads:[~2004-08-27 23:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 6:32 [PATCH] SunSAB console problems in 2.6.x David S. Miller
2004-08-26 8:31 ` Ralph Mitchell
2004-08-26 13:23 ` Ben Collins
2004-08-26 17:01 ` Ben Collins
2004-08-26 18:05 ` Ralph Mitchell
2004-08-26 20:19 ` David S. Miller
2004-08-27 0:43 ` Joshua Kwan
2004-08-27 1:10 ` David S. Miller
2004-08-27 10:30 ` Ralph Mitchell
2004-08-27 19:19 ` David S. Miller
2004-08-27 22:29 ` David S. Miller
2004-08-27 23:24 ` Joshua Kwan
2004-08-27 23:24 ` David S. Miller
2004-08-27 23:25 ` David S. Miller
2004-08-27 23:34 ` C.Newport
2004-08-27 23:39 ` David S. Miller [this message]
2004-08-28 0:01 ` Joshua Kwan
2004-08-28 0:04 ` David S. Miller
2004-08-28 7:06 ` Ralph Mitchell
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=20040827163903.0141f798.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=sparclinux@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.