All of lore.kernel.org
 help / color / mirror / Atom feed
From: j.w.r.degoede@hhs.nl (Hans de Goede)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] [PATCH] AMD K8 digital sensor
Date: Wed, 26 Jul 2006 14:36:52 +0000	[thread overview]
Message-ID: <44C77E04.6010504@hhs.nl> (raw)
In-Reply-To: <44C69648.9060808@sh.cvut.cz>



Rudolf Marek wrote:
> Hello all,
> 
> And info for users:
> The userspace patch is still in here
> http://assembler.cz/download/amd_digital_temp.tar.gz
> the patch itself is for 2.6.18rc-2 but should work on any post 2.6.15
> kernel. If you need standalone version, use that one in the archive.
> 

I was thinking about doing things differently with regards to userspace.
As I already posted to the list I'm working on a driver for the uGuru2.
The driver is done (waiting for feedback from testers) but I still need
todo userspace. Since the uGuru2 driver is going to be 2.6 only and
since 2.6 has a clear API/ABI between userspace and the kernel for hwmon
chips I was thinking about adding code to libsensors for generic 2.6
support. The idea is to write a piece of code which will come into
action only if libsensors doesn't have a chip definition for a found
chip and libsensors is running on a  2.6 kernel. This piece of code
would then fill a dynamicly allocated structure describing the unknown
chip, using the same structure as for known chips.

Does this sound like a plan? With this in place we no longer need to
write support for every new 2.6 hwmon driver, actually if this goes in I
would like to see explicit support for the uGuru (1) be removed, since
this generic code should do just as good of a job.

Does this sound like  a plan (for 2.6 only drivers) ? Or are you
planning on porting this driver to 2.4?

Regards,

Hans


  reply	other threads:[~2006-07-26 14:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-25 22:08 [lm-sensors] [PATCH] AMD K8 digital sensor Rudolf Marek
2006-07-26 14:36 ` Hans de Goede [this message]
2006-07-26 14:44 ` Rudolf Marek
2006-08-22  8:44 ` Jean Delvare
2006-08-22 18:23 ` Rudolf Marek
2006-08-23  7:10 ` Jean Delvare

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=44C77E04.6010504@hhs.nl \
    --to=j.w.r.degoede@hhs.nl \
    --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.