All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugme-daemon@bugzilla.kernel.org
To: cpufreq@www.linux.org.uk
Subject: [Bug 8720] still problems with k7 mobile frequency is lower than real
Date: Sat,  1 Sep 2007 08:21:43 -0700 (PDT)	[thread overview]
Message-ID: <20070901152143.5BAC0108010@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-8720-3570@http.bugzilla.kernel.org/>

http://bugzilla.kernel.org/show_bug.cgi?id=8720


dsd@gentoo.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |davej@codemonkey.org.uk




------- Comment #19 from dsd@gentoo.org  2007-09-01 08:21 -------
Looking at dmesg in comment #15 and corresponding DSDT in comment #16:

powernow tables in this system are unusable so it falls back on ACPI. The
powernow_acpi_control_t values in the control field of the _PSS entries always
result in FID=0 VID=0 which looks wrong.

As there is _PCT, acpi-cpufreq may be a better cpufreq driver choice for this
system. However the ACPI-supplied cpu frequencies in _PSS are wrong.

The DSL code for _PSS reads FID and VID values from system memory (region FSEG
defined at 0x000FDF00 in system memory), and uses them as indexes into a local
PS13 array which presumably contains a series of frequencies. However, again
the FID values are always 0 so it always ends up looking at the first element,
0x5b7 (1463).

I'm not 100% sure if 0x000FDF00 is controlled by Linux or otherwise, however I
am fairly sure the answer here is that your BIOS is double-broken. Dave, any
comments?


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

  parent reply	other threads:[~2007-09-01 15:21 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-06 17:18 [Bug 8720] New: still problems with k7 mobile frequency is lower than real bugme-daemon
2007-07-06 17:19 ` [Bug 8720] " bugme-daemon
2007-07-06 23:57 ` bugme-daemon
2007-07-09 17:50 ` bugme-daemon
2007-07-23  0:08 ` bugme-daemon
2007-07-23  0:09 ` bugme-daemon
2007-07-28 14:40 ` bugme-daemon
2007-07-28 14:42 ` bugme-daemon
2007-07-28 14:43 ` bugme-daemon
2007-07-30  2:50 ` bugme-daemon
2007-07-30 18:21 ` bugme-daemon
2007-07-30 18:53 ` bugme-daemon
2007-07-30 22:46 ` bugme-daemon
2007-08-01 19:48 ` bugme-daemon
2007-08-01 19:50 ` bugme-daemon
2007-09-01 12:41 ` bugme-daemon
2007-09-01 12:41 ` bugme-daemon
2007-09-01 12:43 ` bugme-daemon
2007-09-01 12:46 ` bugme-daemon
2007-09-01 14:34 ` bugme-daemon
2007-09-01 15:21 ` bugme-daemon [this message]
2007-09-06 14:33 ` bugme-daemon
2007-09-06 14:46 ` bugme-daemon
2007-09-23  9:35 ` bugme-daemon
2007-09-23 11:19 ` bugme-daemon
2007-09-30 15:07 ` bugme-daemon

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=20070901152143.5BAC0108010@picon.linux-foundation.org \
    --to=bugme-daemon@bugzilla.kernel.org \
    --cc=cpufreq@www.linux.org.uk \
    /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.