From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Atsushi Nemoto <anemo@mba.ocn.ne.jp>, linux-mips@linux-mips.org
Subject: Re: [MIPS] Probe for usability of cp0 compare interrupt.
Date: Wed, 17 Oct 2007 18:23:45 +0100 [thread overview]
Message-ID: <20071017172345.GA7313@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.64N.0710171756450.28993@blysk.ds.pg.gda.pl>
On Wed, Oct 17, 2007 at 06:03:35PM +0100, Maciej W. Rozycki wrote:
> > The two things are a know lose end. There is a bug in some old MIPS
> > processors where reading one of the compare or count registers in exactly
> > the moment when both have identical values in the interrupt getting lost.
> >
> > Will have to dig up the details on that one again before I can implement
> > a proper workaround ...
>
> This is the erratum #53 of the R4000PC/SC processor and it triggers if
> the Count register is read. Conveniently, in the errata sheet as
> distributed, the text is covered by a figure (Figure 1a on page 13), so
> you can only reach the page with some PostScript magic. I did it a while
> ago and now have a separate document available which provides the text of
> page 13 with the figure removed. I can provide it if there is interest.
Ah. I noticed there was something like white writing on white background
matching when I searched the PDF for keywords. So I guess it would be
nice if somebody could regenerate a PS or PDF file. I also seem to be
missing information on the later R4400 versions.
Ralf
next prev parent reply other threads:[~2007-10-17 17:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S20022491AbXJQLKE/20071017111004Z+82239@ftp.linux-mips.org>
2007-10-17 16:10 ` [MIPS] Probe for usability of cp0 compare interrupt Atsushi Nemoto
2007-10-17 16:46 ` Ralf Baechle
2007-10-17 17:03 ` Maciej W. Rozycki
2007-10-17 17:23 ` Ralf Baechle [this message]
2007-10-17 17:44 ` Maciej W. Rozycki
2007-10-17 18:14 ` Ralf Baechle
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=20071017172345.GA7313@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.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