From: Pat Erley <pat-lkml@erley.org>
To: "Manuel Argüelles" <manuel.arguelles@gmail.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: powernow-k8: No compatible ACPI _PSS objects found. (Asrock N68-S)
Date: Wed, 28 Apr 2010 01:38:00 -0400 [thread overview]
Message-ID: <4BD7C9B8.3090508@erley.org> (raw)
In-Reply-To: <hr8h5q$qt7$1@dough.gmane.org>
On 04/28/10 01:30, Manuel Argüelles wrote:
> Pat Erley wrote:
>>
>> I recently did something similar: http://pat.erley.org/Other/P4EISTSSDT
>>
>> It wasn't 'too hard', but it was by no means easy... the _PSS values were
>> kinda voodoo for me to come up with, and I'm not sure that I have them
>> correct, just that they work.
>>
>> Pat
>
> Thanks a lot!! I took a look at my ssdt and it doesn't even looks complete:
>
> DefinitionBlock ("SSDT.aml", "SSDT", 1, "A M I ", "POWERNOW", 0x00000001)
> {
>
> No idea how to get the values for my CPU, maybe contacting AMD?
>
> One question, if I do something really really stupid, is it possible to fry
> the CPU? what can be the worst case scenario?
Unfortunately, I don't have answers to any of these questions/problems. In
my case, Intel DSDT/SSDT mods are common in the Mac world, so I was able to
find a lot of resources. I'm guessing the wrong value could damage something,
but can't speak from experience. the PSS values dictate CPU voltages and
Freqencies, which dictate heat generation, so it'd be logical that this
could cause damage. I'd suggest looking up AMD datasheets for the CPU and
chipsets.
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-04-28 5:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 4:35 powernow-k8: No compatible ACPI _PSS objects found. (Asrock N68-S) Manuel Argüelles
2010-04-28 5:00 ` Pat Erley
2010-04-28 5:30 ` Manuel Argüelles
2010-04-28 5:38 ` Pat Erley [this message]
2010-05-14 21:08 ` Thomas Renninger
2010-05-15 4:25 ` Manuel Argüelles
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=4BD7C9B8.3090508@erley.org \
--to=pat-lkml@erley.org \
--cc=linux-acpi@vger.kernel.org \
--cc=manuel.arguelles@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.