From: "Mark A. Greer" <mgreer@mvista.com>
To: Benjamin Davis <bmdavis@arlut.utexas.edu>
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: gt-64260 Question
Date: Tue, 25 Nov 2003 13:24:12 -0700 [thread overview]
Message-ID: <3FC3BA6C.3030201@mvista.com> (raw)
In-Reply-To: <3FC39F16.5040208@arlut.utexas.edu>
Benjamin Davis wrote:
> Errata 9 of
> http://e-www.motorola.com/files/32bit/doc/errata/MPC7455CE.pdf
> talks about some issues with QACK,
Okay.
> I further noticed how in arch/ppc/platform/pmac_feature.c, in
> probe_uninorth:
> if (uninorth_rev < 0x11) {
> actrl = UN_IN(UNI_N_ARB_CTRL) & ~UNI_N_ARB_CTRL_QACK_DELAY_MASK;
> actrl |= ((uninorth_rev < 3) ? UNI_N_ARB_CTRL_QACK_DELAY105 :
> UNI_N_ARB_CTRL_QACK_DELAY) <<
> UNI_N_ARB_CTRL_QACK_DELAY_SHIFT;
> UN_OUT(UNI_N_ARB_CTRL, actrl);
>
> It would appear to me that a QACK delay is being set by communication
> with the uninorth. I will say now though this is my first experiance
> with the kernel.
> I was kinda thinking they might have gotten around the errata by
> extending the delay of the QACK. This QACK is the system saying it is
> time to get out of nap, and snoop.
I don't see any reference in the 64260 manual that lets you control
this. Are you sure that you need to nap/snooze? IOW, are you sure
you're not solving a problem you don't have?
Mark
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-11-25 20:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-25 17:41 gt-64260 Question Benjamin Davis
2003-11-25 18:08 ` Mark A. Greer
2003-11-25 18:27 ` Benjamin Davis
2003-11-25 20:24 ` Mark A. Greer [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-25 20:59 Milliorn Gary-rxcr80
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=3FC3BA6C.3030201@mvista.com \
--to=mgreer@mvista.com \
--cc=bmdavis@arlut.utexas.edu \
--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