All of lore.kernel.org
 help / color / mirror / Atom feed
From: r.marek@sh.cvut.cz (Rudolf Marek)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] w83l785r driver
Date: Tue, 11 Apr 2006 18:02:48 +0000	[thread overview]
Message-ID: <443BEF48.5030709@sh.cvut.cz> (raw)
In-Reply-To: <443BE8D3.6050906@sh.cvut.cz>

Hello Lonni,

Thanks for the quick answer. I'm not the person who seeks the help but users
which do seek help from me. I'm the member of lm-sensors group that
develops and maintains the sensor drivers for the Linux kernel. There is
the unified infrastructure for sensors handling and drivers for monitoring chips.

This unified infastructure means that any application can be used to access the sensors data
which are exported to user programs. Making it closed and locked just to one apps may not fit
the user needs at all. Just imagine the user has some favourite application like gkrellm
and wants to see the GPU temp there.

Opening the drivers for i2c access will enable you to use our hwmon drivers for chips
commonly found on the graphics cards. This would mean it would reduce you the time
to develop the driver to access the chip on your own. Moreover, we are taking care of
that the drivers will work nice in any future linux version.

Some companies like Asus, Tyan  and Winbond are working with us tightly on this sensors
field. If you want to join the cooperation, I'm offering help to nVidia whith opening the drivers
for i2c bus and integrating them to the kernel.

Please forward this email to the responsible manager, or if you need more information
contact me directly, or via the lm-sensors mailing list.

Thank you,

Regards
Rudolf


      parent reply	other threads:[~2006-04-11 18:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-11 17:35 [lm-sensors] w83l785r driver Rudolf Marek
2006-04-11 17:43 ` Lonni J Friedman
2006-04-11 18:02 ` Rudolf Marek [this message]

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=443BEF48.5030709@sh.cvut.cz \
    --to=r.marek@sh.cvut.cz \
    --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.