From: Phil Perry <phil@elrepo.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] EXTERNAL: Re: coretemp driver
Date: Sat, 08 Aug 2015 14:44:35 +0000 [thread overview]
Message-ID: <55C615D3.2010208@elrepo.org> (raw)
In-Reply-To: <830397DA32E1A0479077F4D3642B448B62D86C73@HVXDSP41.us.lmco.com>
On 08/08/15 15:20, Guenter Roeck wrote:
>
>>
>> We are running RedHawk5.4.11, 2.6.31.13, based on RHEL5.4 x86, on an
>> IBM HS23.
>> Executing sensors showed no output at all, no sensors detected.
>> I looked at coretemp.c and saw that the HS23 CPU, 32nm, CPUID= 0X2D,
>> was not supported and in fact coretemp was reporting that in
> /var/log/messages.
>> I added 0x2D to coretemp.c and rebuilt the kernel to see if we could
> even read
>> a sensor. That worked and now there is a temperature reported for each
>> CPU.
Additionally, you don't need to patch and recompile the whole kernel for
just one driver - you can build your patched coretemp driver out of tree.
>> However, with the "workaround" I don't have any confidence in the
> accuracy
>> of the output of course. Is there a patch I can apply to the kernel
> source
>> that will update coretemp.c and related source code?
>
> The upstream driver has been rewritten pretty much completely since then.
> I had a quick look, but back-porting the latest version to 2.6.31
> would be a major effort.
>
> I think the best you can do is to stick with what you did.
>
> Guenter
>
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2015-08-08 14:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 16:40 [lm-sensors] EXTERNAL: Re: coretemp driver Minimi, Phillip A
2015-08-07 17:18 ` Guenter Roeck
2015-08-08 10:59 ` Minimi, Phillip A
2015-08-08 13:34 ` Minimi, Phillip A
2015-08-08 14:20 ` Guenter Roeck
2015-08-08 14:44 ` Phil Perry [this message]
2015-08-08 15:00 ` Minimi, Phillip A
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=55C615D3.2010208@elrepo.org \
--to=phil@elrepo.org \
--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.