From: "Kyle Nesbit" <kyle.nesbit@asu.edu>
To: linuxppc-dev@lists.linuxppc.org
Subject: L2CR
Date: Mon, 08 Feb 1999 19:34:56 -0700 [thread overview]
Message-ID: <199902090234.TAA26936@mx0-smtp.goodnet.com> (raw)
I am currently looking for some more info on how to get my L2 backside cache
running. I am using a powerlogix card.
I have used the powerlogix/Ben patch posted in the mailing list during Dec.
The kernel compiled without and error. When I try to pass the l2cr kernel
argument I get nothing. my /proc/sys/kernel/l2cr is 00000000: disabled,
etc...
Another thing that is strange is in /proc/cpuinfo the clock rate of my chip
is off by over 100 MHZ.
I would greatly appreciate if someone could point me to more info on the
subject.
Thanx,
Kyle
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next reply other threads:[~1999-02-09 2:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-09 2:34 Kyle Nesbit [this message]
1999-02-09 11:02 ` L2CR BenH
1999-02-09 13:11 ` L2CR BenH
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=199902090234.TAA26936@mx0-smtp.goodnet.com \
--to=kyle.nesbit@asu.edu \
--cc=linuxppc-dev@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).