From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: sh7785 cache question
Date: Tue, 01 Sep 2009 03:05:01 +0000 [thread overview]
Message-ID: <20090901030501.GB531@linux-sh.org> (raw)
In-Reply-To: <4A7A9C73.1070000@siemens.com>
On Tue, Sep 01, 2009 at 11:19:37AM +0900, yoshii.takashi@renesas.com wrote:
> I think this answer solves your question better than paul's...
> A: You have the question because the manual's description is insufficient.
> # I'm a software engineer, and this is never an official speaking of renesas's semiconductor division.
>
> Actually, you can use 00000000-EFFFFFFF and F4xxxxxxxx for SH4A's cache insns.
> # only F4xxxxxx is valid for SH4. 00000000-EFFFFFFF is SH4A extension.
>
> SH7785 Hardware Manual (rej09b0261) says
> > Do not execute this instruction to invalidate the memory-mapped array areas and control
> > register areas for which Rn[31:24] is not H'F4, and their reserved areas (H'F0 to H'F3, H'F5 to
> > H'FF).
>
> Mmm. Perhaps two sentences has been crashed into one? I guess what they wanted to say was
> Do not use this instructions onto
> the memory-mapped array areas and control register areas for which Rn[31:24] is not H'F4.
> # According to "Figure 7.4 P4 Area" of the manual,
> # memory-mapped array areas is H'F3-H'F7, control register areas is H'FC-H'FF
> # Anyway, this does not care about lower space (H'00-H'EF), that is valid area.
>
> And later part is additional, somewhat duplicated area assignment, as a result this is the answer
> Don't use them onto H'F0 to H'F3 and H'F5 to H'FF.
>
> Only the condition (F0-F3,F5-FF) is clearly described in Software manual for SH4A extensions
> (rjj09b0235 written in Japanese, No English version found).
> Sorry for inconvenient.
>
I think part of the confusion comes from the fact we are still using
associative writes, which we should ultimately move away from given the
fact they can silently turn in to nops under the right conditions on
current hardware. With the transition off of associative accesses, none
of this should be an issue.
prev parent reply other threads:[~2009-09-01 3:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 9:03 sh7785 cache question Valentin R Sitsikov
2009-08-13 3:17 ` Paul Mundt
2009-08-31 7:56 ` Valentin R Sitsikov
2009-09-01 2:19 ` yoshii.takashi
2009-09-01 3:05 ` Paul Mundt [this message]
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=20090901030501.GB531@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox