From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] seeking a W83687THF patch for 2.6.15 (re: ticket
Date: Fri, 06 Jan 2006 18:53:32 +0000 [thread overview]
Message-ID: <20060106195332.45aed75e.khali@linux-fr.org> (raw)
In-Reply-To: <43BDFEEE.4070408@rogers.com>
Hi Steven,
> I have the misfortune of having the Windbond W83687THF Super I/O IC on
> my Soltek motherboard (SL-B9D-FGR).
Nothing to worry about. Sure we don't support this chip right now, but
given the good relationship that exists between the lm_sensors group
and Winbond, I am certain we should be able to come up with a solution
fast.
> I tried manually patching the w83627hf.c file contained in the 2.6.15
> sources with the changes outlined in the experimental patch for
> 2.6.13-rc3 found on the lm_sensors drivers page. There were a few
> differences in line numbers but thats about it (i.e. it was pretty
> straightforward what to change). Unfortunately, it didn't work for me
> (sensors-detect didn't detect...didn't even probe for this chip). This
> was probably predictable, as I'm not at all familiar with what was
> required and what all else would have needed to have been changed (i.e.
> I was just taking a stab in the dark in hopes that I might get it right).
Which version of lm_sensors (user-space) are you using? The W83687THF
detection was added in version 2.9.2, so you need at least this
version. Please note also that the detection code was written without
the benefit of a datasheet, so it might simply be incomplete.
You could provide the output of "isadump -k 0x87,0x87 0x2e 0x2f 0x0b"
so that I compare the ID of your chip with what is believed to the the
W83687THF chip ID. Note that you need isadump from lm_sensors 2.9.2 for
it to work.
> Which brings me to my question: how do I go about applying the
> experimental code/patch in order to gain support for my board' w83687thf ?
I just updated the patch for Linux 2.6.15:
http://jdelvare.net2.nerim.net/sensors/linux-2.6.15-hwmon-w83687thf.diff
But this shouldn't be fundamentally different from what you had
starting from the 2.6.13-rc3 patch, if you fixed it properly.
Please also keep in mind that for user-space support you need to apply
the following patch to the lm_sensors sources:
http://jdelvare.net2.nerim.net/sensors/CVS-w83687thf.diff
I checked it and it still applies to CVS with some offset.
--
Jean Delvare
next prev parent reply other threads:[~2006-01-06 18:53 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-06 5:23 [lm-sensors] seeking a W83687THF patch for 2.6.15 (re: ticket 1944) Steven Karatnyk
2006-01-06 7:01 ` [lm-sensors] seeking a W83687THF patch for 2.6.15 (re: ticket Jim Cromie
2006-01-06 9:06 ` [lm-sensors] seeking a W83687THF patch for 2.6.15 (re: Ymu
2006-01-06 18:53 ` Jean Delvare [this message]
2006-01-06 19:08 ` Jean Delvare
2006-01-06 19:16 ` [lm-sensors] seeking a W83687THF patch for 2.6.15 (re: ticket Steven Karatnyk
2006-01-06 19:34 ` [lm-sensors] seeking a W83687THF patch for 2.6.15 (re: Steven Karatnyk
2006-01-06 19:41 ` Steven Karatnyk
2006-01-06 20:06 ` [lm-sensors] seeking a W83687THF patch for 2.6.15 (re: ticket Jim Cromie
2006-01-08 1:30 ` Steven Karatnyk
2006-01-10 21:33 ` Steven Karatnyk
2006-01-11 6:56 ` CityK
2006-01-11 7:01 ` [lm-sensors] seeking a W83687THF patch for 2.6.15 (re: ticket 1944) Steven Karatnyk
2006-01-11 22:20 ` [lm-sensors] seeking a W83687THF patch for 2.6.15 (re: ticket Jean Delvare
2006-01-12 22:37 ` Jean Delvare
2006-01-13 4:59 ` Steven Karatnyk
2006-01-14 23:54 ` Steven Karatnyk
2006-01-15 17:54 ` Jean Delvare
2006-01-15 18:00 ` Jean Delvare
2006-01-16 19:41 ` Steven Karatnyk
2006-01-16 20:11 ` Steven Karatnyk
2006-01-16 22:20 ` Jean Delvare
2006-01-16 22:27 ` Jean Delvare
2006-01-19 4:41 ` Mark M. Hoffman
2006-01-19 5:07 ` Steven Karatnyk
2006-01-19 5:20 ` Steven Karatnyk
2006-01-19 5:27 ` Steven Karatnyk
2006-01-20 7:42 ` Jean Delvare
2006-01-24 5:51 ` Steven Karatnyk
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=20060106195332.45aed75e.khali@linux-fr.org \
--to=khali@linux-fr.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.