From: Ricardo Scop <scop@vanet.com.br>
To: Jean-Denis Boyer <jdboyer@mediatrix.com>
Cc: "'Dan Malek'" <dan@embeddededge.com>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re[2]: 8260 - Spurious interrupt when calling __sti()
Date: Wed, 10 Apr 2002 13:59:33 -0300 [thread overview]
Message-ID: <10583.020410@vanet.com.br> (raw)
In-Reply-To: <F1BED55F35F4D3118C0F00E0295CFF4DFF9F92@mail.mediatrix.com>
Jean-Denis,
Wednesday, April 10, 2002, 1:31:05 PM, you wrote:
<snip>
JDB> What is even more strange, I can put the 'sync' everywhere in the '__sti'
JDB> function, that is before the 'mfmsr', before the 'ori', or before the
JDB> 'mtmsr',
JDB> and the problem of spurious interrupt simply disappear. Remove it, it
JDB> reappears.
<snip>
JDB> Hard to explain...
Even harder to explain is why you're having to put those syncs in
__sti, since both my copies of 2.4.16 and 2.4.18-pre9 kernel sources
already have them in the code... and with the comment
"/* Some chip revs have problems here... */" !!!
[]'s, Scop mailto:scop@vanet.com.br
------------------------------------------------------------------
"We all lie in the gutter, but some of us look up at the stars."
-- Oscar Wilde
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-04-10 16:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-10 16:31 8260 - Spurious interrupt when calling __sti() Jean-Denis Boyer
2002-04-10 15:50 ` Dan Malek
2002-04-10 16:59 ` Ricardo Scop [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-10 17:16 Re[2]: " Jean-Denis Boyer
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=10583.020410@vanet.com.br \
--to=scop@vanet.com.br \
--cc=dan@embeddededge.com \
--cc=jdboyer@mediatrix.com \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).