From: Achim Gottinger <achim@ag-web.biz>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] AMD Phenom temperature driver
Date: Wed, 23 Jul 2008 11:38:20 +0000 [thread overview]
Message-ID: <4887182C.3030100@ag-web.biz> (raw)
In-Reply-To: <4881063D.60906@assembler.cz>
Rudolf Marek schrieb:
> Hello all,
>
> I think I put all parties up in CC. Thanks to Andreas, I have received
> missing information about the TControlMax temperature. It means we can
> get further to a new driver.
>
> I did some experimental driver which works fine (attached as k8temp.c)
> Kryzstof Went even further and made changes to original k8temp driver.
>
> I will go for vacation soonish (middle of next week) and I'm very
> busy, but at least we can start. I will write a short list of things
> which needs to be discussed in the meanwhile:
>
> 1) driver name
>
> AMD proposes the change to amdtemp (from k8temp) I think we can merge
> the drivers together, it should be still simple.
>
> Jean, please do you remember how autoloading/driver name change is
> handled in the kernel? I have some feeling that it should be simple to
> handle. Please confirm.
>
> The name change can be done if we know that old name will work, so we
> dont break too much things around.
>
> 2) Maximum temperature.
>
> The new Phenom temperature is non-physical it means we must know the
> limit so we know when we cross it.
>
> Therefore our new driver must export either temp1_max or temp1_crit.
> The TcontrolMax is for all fam 10h CPUs 70 degrees.
>
> The Intel driver has temp1_max as maximum temperature from which all
> fans must start cooling. The temp1_crit is when the CPU will fail.
>
> I think the thremtrip_l is asserted for much higher temperatures, I
> think we can go for temp1_max.
>
> We can put the TcontrolMax into a variable, because for future
> revisions we may need cpuid to put there right value.
>
> 3) Errata #319
>
> I think all CPU revisions still may have problem with the temp sensor
> inside the CPU (not the diode interface which is analog and works fine).
>
> Please can someone test mine k8temp.c attached, and report back the
> values you got? If we detect a CPU with the errata we should print a
> warning to syslog.
Hi Rudolf,
I tried your attached code with an 9950BE and the temps reported look
equal to those everest reports under winxp 32bit with similar load
conditions. I have a few other phenoms here and will report if i find
one whos affected by the errata.
achim~
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
prev parent reply other threads:[~2008-07-23 11:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 21:08 [lm-sensors] AMD Phenom temperature driver Rudolf Marek
2008-07-23 11:38 ` Achim Gottinger [this message]
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=4887182C.3030100@ag-web.biz \
--to=achim@ag-web.biz \
--cc=lm-sensors@vger.kernel.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 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.