From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Chris Friesen <cfriesen@nortel.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
linuxppc64-dev <linuxppc64-dev@ozlabs.org>
Subject: Re: looking for help with scomc/scomd registers on 970
Date: Fri, 25 Feb 2005 15:33:38 +1100 [thread overview]
Message-ID: <1109306018.14992.52.camel@gaston> (raw)
In-Reply-To: <421E06B9.2000504@nortel.com>
On Thu, 2005-02-24 at 10:54 -0600, Chris Friesen wrote:
> Not strictly linux related, but I thought someone might know the answer.
>
> I've got a request from someone that wants to be able to flush the L2 on
> the 970.
>
> The user manual has a procedure to do this, but it involves first
> flipping the cache to direct-mapped mode by setting SCOM register
> 0x43000 bit 0x8000. The only thing is, I can't find any linux code that
> ever touches the SCOM stuff, and the manual has no examples of *reading*
> from the SCOM area, just writing to it, so I'm not entirely sure how to
> do that.
>
> A google search found the following snippet of darwin code:
>
>
> lis r8,cFIR ; Get the Core FIR register address
> ori r8,r8,0x8000 ; Set to read data
> sync
> mtspr scomc,r8 ; Request the Core FIR
> mfspr r25,scomd ; Get the source
> mfspr r8,scomc ; Get back the status (we just ignore it)
> sync
> isync
>
>
>
> This implies that bit 0x8000 needs to be set to specify a read command,
> and that we need to read the status after the read. Does anyone know if
> this is in fact the case?
I think so. Also, there are some erratas with early 970's where the
stuff is shifted one bit. The Darwin source is a good reference for
that.
> Also, in that code they make reference to early chip revisions that
> returned scom reads shifted by one bit. Does anyone know which versions
> are affected?
I think all non-FX.
Ben.
prev parent reply other threads:[~2005-02-25 4:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 16:54 looking for help with scomc/scomd registers on 970 Chris Friesen
2005-02-25 4:33 ` Benjamin Herrenschmidt [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=1109306018.14992.52.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=cfriesen@nortel.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.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.