From: Ducrot Bruno <ducrot@poupinou.org>
To: Luigi Belli <lbelli@crema.unimi.it>
Cc: cpufreq@www.linux.org.uk
Subject: Re: Acer Aspire 1300 buggy BIOS - hardcoded patch
Date: Mon, 30 Jun 2003 17:14:01 +0200 [thread overview]
Message-ID: <20030630151401.GE7796@poupinou.org> (raw)
In-Reply-To: <200306301436.29188.lbelli@crema.unimi.it>
On Mon, Jun 30, 2003 at 02:36:29PM +0200, Luigi Belli wrote:
> I'm one of the owners of an Acer Aspire 1300 series with a buggy BIOS, so I
> decided to hardcode a patch with the correct PST table for my mobile Athlon
> XP 1800+.
> I know very little of kernel internals, I only opened powernow-k7.c and tried
> to guess what had to be changed...
> For me it works and I decided to post it here for those in my conditions
> waiting for a new bios or a newer cpufreq release.
> It's a patch against kernel 2.4.21-ac4.
I am wondering if the _PCT table (from ACPI) are correct or not.
Could you send me a DSDT table, please? For this, you have to
retrieve pmtools from intel site (this should be the latest link):
http://developer.intel.com/technology/iapc/acpi/downloads.htm
then go to pmtools-20010730/acpidmp/
make
./acpidmp DSDT > dsdt
gzip dsdt
then send me *privately* the dsdt.gz file.
I will then look if, at least, ACER guy give correct _PCT table.
Cheers,
--
Ducrot Bruno
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
next prev parent reply other threads:[~2003-06-30 15:14 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 [this message]
2003-07-01 10:51 ` Ducrot Bruno
2003-07-04 17:04 ` Ducrot Bruno
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=20030630151401.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