All of lore.kernel.org
 help / color / mirror / Atom feed
From: medaglia@gmail.com (Cadu)
To: lm-sensors@vger.kernel.org
Subject: Winbound W83627EHF sensor
Date: Thu, 19 May 2005 06:25:58 +0000	[thread overview]
Message-ID: <797de5c3050511075323d34b3d@mail.gmail.com> (raw)
In-Reply-To: <20050510203454.27683f7b.medaglia@gmail.com>

On 5/11/05, Jean Delvare <khali@linux-fr.org> wrote:
> > I'd like to help with code. I've wrote a webcam driver to Linux, so I
> > have some experience. I'd like to know where to start! :)
> 
> Pick the datasheet here:
> http://archives.andrew.net.au/lm-sensors/pdfe5IBpZipZu.pdf

Ok... Thanks!

> Reminder for your future work: do NOT trust that datasheet like holy
> words. I have found errors already, and there may be more.

Oh.. I know. I have experience with bad datasheets too... :)

> Then start from my version of the driver (be sure to start from the
> latest version!) 

Where is the latest version? I have a patch to linux-2.6.12-rc3. I
don't know if it is the latest version.
Are you hacking this driver now? I'm asking that because if the answer
is yes, we can change the same thing at the same time, and maybe it
will not be a good thing.

> and add the missing functions (voltage inputs, VID/VRM,
> PWM outputs). My w83627ehf code is based on the w83627hf driver in the
> first place, so you can probaly find inspiration there. See how this
> other driver handles the missing features, copy to the w83627ehf driver
> and edit to match the datasheet. Then recompile and test your new driver.
> 
> Note that "sensors" won't show anything until libsensors knows about
> the new features. I invite you to first make sure that the driver works
> OK by manually reading and writing values in /sys/bus/i2c/devices/*.
> Once you have tested this, you can edit the code of libsensors and the
> sensors program (both in the lm_sensors package) to handle the new
> features.

I'll do that.

> That's it for the big plan. Now if you have more precise questions, do
> not hesitate. Oh, and please answer to the mailing-list rather than me
> directly, so that others can voice in.

Ok. I will start today!

Thank you!
Cadu

  parent reply	other threads:[~2005-05-19  6:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19  6:25 Winbound W83627EHF sensor Carlos Eduardo Medaglia Dyonisio
2005-05-19  6:25 ` Jean Delvare
2005-05-19  6:25 ` Jean Delvare
2005-05-19  6:25 ` Jean Delvare
2005-05-19  6:25 ` Cadu [this message]
2005-05-19  6:25 ` Jean Delvare
2005-05-19  6:25 ` Cadu

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=797de5c3050511075323d34b3d@mail.gmail.com \
    --to=medaglia@gmail.com \
    --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.