From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: John Steele Scott <toojays@toojays.net>
Cc: linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>,
Christiaan Welvaart <cjw@daneel.dyndns.org>
Subject: Re: nearly-working support for cpufreq on 2004 iBook G4 with 7447A cpu
Date: Mon, 31 May 2004 13:49:51 +1000 [thread overview]
Message-ID: <1085975390.1930.31.camel@gaston> (raw)
In-Reply-To: <200405311003.21439.toojays@toojays.net>
On Mon, 2004-05-31 at 10:32, John Steele Scott wrote:
>
> On Mon, 31 May 2004 08:13 am, Benjamin Herrenschmidt wrote:
> > OF is probably not reporting wrong frrequency, check your bogomips. I
> > suspect your clock chip isn't configured properly at boot, like with
> > other newer models. I need to hack the proper bits in. I'll have a look
> > at this asap.
Ok, that's weird, I don't see the same kind of clock chip on i2c as
the previous model had... Can you check the exact dividers programmed
on the CPU and redo the calculation based on the bus frequency ?
There is a do-clock-spreading property attached to the U2 ASIC, I don't
know if it may be related, I'll have a look.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-05-31 3:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-30 14:01 nearly-working support for cpufreq on 2004 iBook G4 with 7447A cpu John Steele Scott
2004-05-30 22:43 ` Benjamin Herrenschmidt
2004-05-30 22:43 ` Benjamin Herrenschmidt
2004-05-31 0:32 ` John Steele Scott
2004-05-31 0:29 ` Benjamin Herrenschmidt
2004-05-31 3:49 ` Benjamin Herrenschmidt [this message]
2004-05-31 8:37 ` John Steele Scott
2004-05-31 23:41 ` Benjamin Herrenschmidt
2004-05-31 23:47 ` Benjamin Herrenschmidt
2004-06-01 2:05 ` nearly-working support for cpufreq on 2004 iBook G4 with 7447Acpu John Steele Scott
2004-06-01 2:53 ` Benjamin Herrenschmidt
2004-06-02 11:08 ` nearly-working support for cpufreq on 2004 iBook G4 with 7447A cpu John Steele Scott
2004-06-03 22:26 ` Benjamin Herrenschmidt
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=1085975390.1930.31.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=cjw@daneel.dyndns.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=toojays@toojays.net \
/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).