cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ducrot Bruno <ducrot@poupinou.org>
To: cpufreq@www.linux.org.uk
Cc: Luigi Belli <lbelli@crema.unimi.it>
Subject: Re: Acer Aspire 1300 buggy BIOS - hardcoded patch
Date: Fri, 4 Jul 2003 19:04:56 +0200	[thread overview]
Message-ID: <20030704170456.GE7796@poupinou.org> (raw)
In-Reply-To: <20030701105154.GK7796@poupinou.org>

> Interresting.  From ACPI point-of-view, you have those states (I reproduce
> only the different frequencies)
> 
> 950 MHz
> 750 MHz
> 700 MHz
> 600 MHz
> 500 MHz
> 
> Ahem,  seems that not only your PST table is somehow wrong, but it seems
> there is nothing to do with ACPI either, sorry.
> 

Ok.  Looking a little bit more, I think I can in fact retrieve
the exact same configuration (at least FID/VID), minus fsb and
settling time (which is 125us instead of 100us) than your override.

I am therefore wondering if that is OK to fallback to retrieve at
least those FID/VID via ACPI, but (ahem) still the fsb issue though.


The 5 states retrieved via _PSS look like this:

+---------+-------------------+---------------+------------+--------+
|  Freq.  | Power compsuption | settling time |   control  | verif. |
|---------+-------------------+---------------+------------+--------|
| 950 MHz |     24000 mW      |     125 us    | 0x009C418D | 0x018D |
| 750 MHz |     16337 mW      |     125 us    | 0x009C41C9 | 0x01C9 |
| 700 MHz |     15248 mW      |     125 us    | 0x009C41C8 | 0x01C8 |
| 600 MHz |     12084 mW      |     125 us    | 0x009C4226 | 0x0226 |
| 500 MHz |      9280 mW      |     125 us    | 0x009C4264 | 0x0264 |
+---------+-------------------+---------------+------------+--------+

Therefore, the 'control' stuff look like:
bits 0-4: FID
bits 5-9: VID
other bits: ?

rem: I must admit I don't know for what is the other bit-fields.
     Perhaps some may give real fsb and settling time?

which then permit to get those pairs (FID/VID):

state 0:  FID:0x0d (1263.5 MHz -- 950.0 MHz) / VID:0x0c (1.400)
state 1:  FID:0x09 (997.5 MHz -- 750.0 MHz) / VID:0x0e (1.300)
state 2:  FID:0x08 (931.0 MHz -- 700.0 MHz) / VID:0x0e (1.300)
state 3:  FID:0x06 (798.0 MHz -- 600.0 MHz) / VID:0x11 (1.250)
state 4:  FID:0x04 (665.0 MHz -- 500.0 MHz) / VID:0x13 (1.200)

rem: For the FID, I compute also the theorical freq. if fsb = 133 at
     first, then if fsb = 100.
and well, that look a little better than nothing.

Cheers,

-- 
Ducrot Bruno

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.

  reply	other threads:[~2003-07-04 17:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-30 12:36 Acer Aspire 1300 buggy BIOS - hardcoded patch Luigi Belli
2003-06-30 15:14 ` Ducrot Bruno
2003-07-01 10:51   ` Ducrot Bruno
2003-07-04 17:04     ` Ducrot Bruno [this message]
2003-06-30 19:14 ` Stefan Gehn
2003-06-30 22:59 ` Francesco Poli
2003-06-30 23:20   ` Luigi Belli
2003-07-01 21:43     ` Francesco Poli
2003-07-01 10:12   ` Morrowind
  -- strict thread matches above, loose matches on Subject: below --
2003-07-01  0:44 Alex Young
2003-07-01  5:34 ` Adachi, Kenichi
2003-07-01 12:24 davidendless
2003-07-01 13:34 ` Luigi Belli
2003-07-01 14:20   ` Stefan Hoppe

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=20030704170456.GE7796@poupinou.org \
    --to=ducrot@poupinou.org \
    --cc=cpufreq@www.linux.org.uk \
    --cc=lbelli@crema.unimi.it \
    /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