linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Terry Greeniaus <tgree@phys.ualberta.ca>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Chris Studholme <cvs@cs.utoronto.ca>, linuxppc-dev@lists.linuxppc.org
Subject: Re: pismo upgraded to 750fx not detected correctly
Date: Sun, 22 Jun 2003 15:58:49 -0600 (MDT)	[thread overview]
Message-ID: <Pine.LNX.4.10.10306221552510.7619-100000@pneuma.phys.ualberta.ca> (raw)
In-Reply-To: <1056275365.3808.49.camel@gaston>


On 22 Jun 2003, Benjamin Herrenschmidt wrote:

> Note that the kernel doesn't use the device tree to detect the
> CPU type. It rather runs the PVR through a table in
> arch/ppc/kernel/cputable.c. There is currently no hook you could
> use to 'fix' that. Ideally, you should make sure the CPU is properly
> detected before the fixups are done or you may "lose" some 750fx
> specific code.
>
> Terry: do you setup PLL1 ? I assume it's set to a low freq by
> the firmware and switch to it during idle among others...
>
> If PLL1 isn't set, you should probably not set powersave_lowspeed
> in arch/ppc/platforms/pmac_feature.c.

Currently we don't ship any LinuxPPC software with the upgrades.  The
hardware is strapped so that its built-in PLL comes up at the maximum
speed of the upgrade (usually 900 MHz).  This allows software to
determine the range of allowed PLL settings.  The user can attempt to
overclock by running the software in "advanced" mode, but that isn't
documented or supported really.  The software we ship allows the user to
manually configure the CPU speed by switching the PLLs, if that's what
you're asking I can post some code to do that, but I thought LinuxPPC
already had something similar.  We don't downclock the CPU when it is
idle, but that would probably be a nice power saver.

TG


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-06-22 21:58 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200306200459.XAA31217@lists.linuxppc.org>
2003-06-20  5:53 ` pismo upgraded to 750fx not detected correctly Terry Greeniaus
2003-06-21 15:58   ` Chris Studholme
2003-06-22  9:49     ` Benjamin Herrenschmidt
2003-06-22 21:58       ` Terry Greeniaus [this message]
2003-06-23  6:01         ` Benjamin Herrenschmidt
2003-06-23  4:47       ` Chris Studholme
2003-06-23  8:27         ` Gabriel Paubert
2003-06-23 17:16           ` Chris Studholme
2003-06-24  8:18             ` Gabriel Paubert
2003-06-23 17:46           ` Benjamin Herrenschmidt
2003-06-26 17:02       ` how to setup PLL1 on 750FX Chris Studholme
2003-06-26 17:33         ` Terry Greeniaus
2003-06-26 20:47           ` Chris Studholme
2003-06-27 11:37             ` Benjamin Herrenschmidt
2003-06-28  3:05               ` Chris Studholme
2003-06-28  8:23                 ` Benjamin Herrenschmidt
2003-06-30 18:57                   ` Chris Studholme
2003-07-01  9:52                     ` Benjamin Herrenschmidt
     [not found] <200306130459.XAA18908@lists.linuxppc.org>
2003-06-13  5:44 ` pismo upgraded to 750fx not detected correctly Terry Greeniaus
2003-06-19 18:18   ` Chris Studholme
2003-06-12 20:05 Chris Studholme

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=Pine.LNX.4.10.10306221552510.7619-100000@pneuma.phys.ualberta.ca \
    --to=tgree@phys.ualberta.ca \
    --cc=benh@kernel.crashing.org \
    --cc=cvs@cs.utoronto.ca \
    --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).