cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Bruno Ducrot <ducrot@poupinou.org>
Cc: cpufreq <Cpufreq@www.linux.org.uk>
Subject: Re: ACPI / cpufreq on Presario R3120
Date: Thu, 03 Jun 2004 21:34:05 +0100	[thread overview]
Message-ID: <1086294845.2970.1.camel@delerium.codemonkey.org.uk> (raw)
In-Reply-To: <20040603182047.GH13782@poupinou.org>

On Thu, 2004-06-03 at 19:20, Bruno Ducrot wrote:

> 
>         Package (0x06)
>         {
>             0x00000320, 
>             0x000032C8, 
>             0x00000064, 
>             0x00000006, 
>             0xE0202E00, 
>             0x00000600
>         }, 
> 
>         Package (0x06)
>         {
>             0x00000320, 
>             0x000032C8, 
>             0x00000064, 
>             0x00000006, 
>             0xE0202E00, 
>             0x00000600
>         }
>     })
> 
> 
> The last two states are *exactly* the same.  Then powernow-k8 complains that
> there is 2 low states (which is not supported, as Paul will tell us).
> Then the driver fail.

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

  reply	other threads:[~2004-06-03 20:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-03 14:32 ACPI / cpufreq on Presario R3120 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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-06-03 17:39 paul.devriendt
2004-06-03 21:42 paul.devriendt
2004-06-03 21:58 ` Ken Hughes
2004-06-04  9:59 ` Bruno Ducrot
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-04 18:01 paul.devriendt
2004-06-05 13:52 ` 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=1086294845.2970.1.camel@delerium.codemonkey.org.uk \
    --to=davej@redhat.com \
    --cc=Cpufreq@www.linux.org.uk \
    --cc=ducrot@poupinou.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