All of lore.kernel.org
 help / color / mirror / Atom feed
From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] vt1211 questions
Date: Sun, 29 Jan 2006 21:56:01 +0000	[thread overview]
Message-ID: <20060129225601.696e685c.khali@linux-fr.org> (raw)
In-Reply-To: <191fb4ca0512131244y460b368do91d586d73f21c258@mail.gmail.com>

Hi Juerg,

> At this point, I leave the mapping as it is (in 2.4) and make sure
> that the 2.6 version of the driver will have the same mapping. Maybe I
> will fix it in both 2.4 and 2.6 at a later time. It's not a high
> priority, just cosmetics.

We will most certainly need to do the same changes in 2.4 we had to do
for the vt8231 driver. But obviously not just before the freshly
announced 2.10.0 release. And you're right, the 2.4 and 2.6 drivers will
have to be in sync. This means not only the input numbers, but also, in
part, the values. Magnitude differences are OK, libsensors can deal
with them, but that's about it.

> I can certainly generate a patch and make it available for people to
> test it. Speaking of making kernel patches: I'm not too familiar with
> that. Am I supposed to generate a patch against the latest (devel)
> kernel or is 2.6.14 good enough?

I can only accept patches against a recent tree. Ideally, the latest
-mm tree. At the very least, Linus' latest (-git).

> I'll try to do that over the next couple of days. I also need to
> supply some basic information on how to use the PWM feature and it
> also requires a new sensors.conf since the 2.6 driver doesn't do weird
> scaling of temperature and voltage numbers anymore. It just returns
> the true register values and any scaling is performed via the compute
> lines in sensors.conf.

This might not be acceptable with regards to the standard interface as
defined in Documentation/hwmon/sysfs-interface. As much as possible,
the values you pass through sysfs must make some physical sense, even
if they are not direct readings. See how we did for the VT8231, it has
many common points with the VT1211 so you should be able to do the same.

> Is it possible to host the patch on the lm-sensors webpage and maybe
> issue a call to VT1211 users? Just like you did it with the VT8231.

We can't really host temporary files on the lm-sensors webpage, but we
can make annoucements and point to any external URI you'd have set up.
If you can't host the patch yourself, just send it to me and I'll make
it available on my server (if so, I'll also update it after that as
needed.)

Thanks,
-- 
Jean Delvare


  parent reply	other threads:[~2006-01-29 21:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-13 20:44 [lm-sensors] vt1211 questions Juerg Haefliger
2006-01-27 20:57 ` Rudolf Marek
2006-01-29 21:32 ` Juerg Haefliger
2006-01-29 21:44 ` Rudolf Marek
2006-01-29 21:56 ` Jean Delvare [this message]
2006-01-30  2:28 ` Juerg Haefliger

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=20060129225601.696e685c.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.