From: Dave Jones <davej@codemonkey.org.uk>
To: Dominik Brodowski <linux@brodo.de>
Cc: textshell@neutronstar.dyndns.org, linux-kernel@vger.kernel.org,
Henrik Persson <nix@syndicalist.net>
Subject: Re: 2.6.0-test1: CPUFreq not working, can't find sysfs interface
Date: Tue, 22 Jul 2003 15:42:53 +0100 [thread overview]
Message-ID: <20030722144253.GA32119@suse.de> (raw)
In-Reply-To: <20030722142353.GA1301@brodo.de>
On Tue, Jul 22, 2003 at 04:23:53PM +0200, Dominik Brodowski wrote:
> On Tue, Jul 22, 2003 at 04:18:39PM +0200, textshell@neutronstar.dyndns.org wrote:
> > So it seems to me that the BIOS doesn't have the tables for my Athlon
> > model/stepping. I tried to get a new bios from hp, but it didn't change anything
> > relevant (they changed something in the PSTs but did not add a new one for my
> > processor)
> Indeed, that's the BUG().
Can you also mail the output of dmidecode, and the model of the laptop.
This is a 'beat up BIOS vendor' case, which AMD are actively trying to do.
I'll forward the info on to the right people..
> > I think it would be a good thing to display a Message explaining why powernow
> > isn't working to the user in the case that no relevant PST is found.
> Patch appended at the end.
Looks fine. I'll apply it when I get back from KS/OLS.
> > I very much would like to have a way to override (or add to) the bios provided
> > values.
> AFAIK, Dave Jones will add support to override the BIOS-provided tables.
There's been some sysfs discussion with Pat in the last few days
(not specifically cpufreq related, but its going to become easier
to add this aparently..).
Dave
next prev parent reply other threads:[~2003-07-22 14:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-20 15:02 2.6.0-test1: CPUFreq not working, can't find sysfs interface textshell
2003-07-20 17:45 ` Henrik Persson
2003-07-20 21:12 ` textshell
2003-07-22 12:08 ` Dominik Brodowski
2003-07-22 14:18 ` textshell
2003-07-22 14:23 ` Dominik Brodowski
2003-07-22 14:42 ` Dave Jones [this message]
2003-07-22 14:53 ` textshell
2003-07-23 11:13 ` Pavel Machek
2003-07-23 11:28 ` Richard B. Johnson
2003-07-23 12:30 ` Pavel Machek
2003-07-23 16:36 ` Dominik Brodowski
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=20030722144253.GA32119@suse.de \
--to=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@brodo.de \
--cc=nix@syndicalist.net \
--cc=textshell@neutronstar.dyndns.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).