From: Bruno Ducrot <ducrot@poupinou.org>
To: paul.devriendt@amd.com
Cc: davej@redhat.com, Cpufreq@www.linux.org.uk
Subject: Re: ACPI / cpufreq on Presario R3120
Date: Fri, 4 Jun 2004 11:59:45 +0200 [thread overview]
Message-ID: <20040604095945.GI13782@poupinou.org> (raw)
In-Reply-To: <99F2150714F93F448942F9A9F112634C1431B6EA@txexmtae.amd.com>
On Thu, Jun 03, 2004 at 04:42:22PM -0500, paul.devriendt@amd.com wrote:
>
> > We could kludge around this by doing a compare of the tables before we
> > abort, and if they are the same, just ignore one of them.
> > If it differs, we do what we do now.
> >
> > Ideally, this should be fixed in a BIOS update though, or
> > alternatively
> > an ACPI fallback.
> >
> > Paul ?
> >
> > Dave
>
> I'm willing to put it in the driver. It is easy to ignore certain
> table entries (thanks Dominik!), and I already have to do so for
> the case where BIOSs are filling out unused entries with -1 instead
> of accurately reporting how many entries actually exist.
What about doing this kludge in drivers/acpi/processor.c in
acpi_processor_get_performance_states() so that all
drivers will benefit for this?
Dominik?
--
Bruno Ducrot
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
next prev parent reply other threads:[~2004-06-04 9:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 21:42 ACPI / cpufreq on Presario R3120 paul.devriendt
2004-06-03 21:58 ` Ken Hughes
2004-06-04 9:59 ` Bruno Ducrot [this message]
2004-06-04 15:25 ` Dominik Brodowski
2004-06-04 16:07 ` Bruno Ducrot
2004-06-05 13:46 ` Dominik Brodowski
2004-06-04 16:55 ` Ken Hughes
2004-06-05 13:47 ` [PATCH] " Dominik Brodowski
-- strict thread matches above, loose matches on Subject: below --
2004-06-04 18:01 paul.devriendt
2004-06-05 13:52 ` Dominik Brodowski
2004-06-03 17:39 paul.devriendt
2004-06-03 14:32 Ken Hughes
2004-06-03 17:25 ` Bruno Ducrot
2004-06-03 18:02 ` Ken Hughes
2004-06-03 18:20 ` Bruno Ducrot
2004-06-03 20:34 ` Dave Jones
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=20040604095945.GI13782@poupinou.org \
--to=ducrot@poupinou.org \
--cc=Cpufreq@www.linux.org.uk \
--cc=davej@redhat.com \
--cc=paul.devriendt@amd.com \
/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