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:
Date: Fri, 06 Jan 2006 19:08:48 +0000 [thread overview]
Message-ID: <20060106200848.08ed4ad2.khali@linux-fr.org> (raw)
In-Reply-To: <43BDFEEE.4070408@rogers.com>
Hi Yuan,
> Sorry I have not read the w83687thf spec before, It seems a similar chip
> to w83627thf, so I would like to give a patch to try make the driver
> work first. I'm not sure if it can work but I'm sure there should be a
> better solution.
So you do have a datasheet for this chip? I asked Chunhao Huang about
it when he was working with us, but back then he didn't have the
datasheet:
http://lists.lm-sensors.org/pipermail/lm-sensors/2005-June/012754.html
The main reason why we do not support this chip at the moment is simply
the lack of datasheet. If you can publish it on Winbond's site and/or
send it to me, we should be able to start working on proper support. I
made the same assumption you did about the W83687THF chip: that it was
probably similar to the W83627THF, given the similar names and release
dates. If this is true, adding support to the w83627hf driver should be
straightforward. The experimental patch I wrote several months ago may
even be almost sufficient, at least to start with.
> Quoting Jim:
> > BTW - youd do well to drop the *misfortunate* posture.
> I will try to tell my HW colleagues your dissatisfaction...
> Thank you Jim ;)
It really has nothing to do with the hardware itself. It's simply a
matter of getting documentation about the chip. I can easily understand
Steven's original position, it's always a bit worrying when you realize
that your precious hardware lacks support, and he couldn't know how
helpful Winbond is. Now that he knows, I'm sure he'll see the life in
a much more positive way :)
--
Jean Delvare
next prev parent reply other threads:[~2006-01-06 19:08 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 ` [lm-sensors] seeking a W83687THF patch for 2.6.15 (re: ticket Jean Delvare
2006-01-06 19:08 ` Jean Delvare [this message]
2006-01-06 19:16 ` 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=20060106200848.08ed4ad2.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.