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] W83792D & Overtemperature LED on Supermicro
Date: Thu, 07 Jul 2005 21:26:44 +0000	[thread overview]
Message-ID: <20050707212627.565d683a.khali@linux-fr.org> (raw)
In-Reply-To: <1120167411.32695.31.camel@wiz.dev.aspsys.com>

Hi again Eric,

> Yes, that was it, except I had to make a few minor adjustments to the
> driver file to get it to compile against the 2.6.5 kernel.  (Before
> you ask, yes, we *have* to use that kernel version; the customer wants
> SuSE Enterprise 9, and that's the most recent kernel version we have
> from SuSE with all their patches and whatnot.)  In addition, I made a
> teeny patch to the driver to change the dev_info() message that is
> logged every time the driver polls the chip to a dev_dbg() message,
> since our production engineer was concerned about the excessive log
> messages.  I am attaching the patch as I modified it for 2.6.5, and
> the second patch for the log messages (that works against either the
> 2.6.5 or 2.6.12 patches).

Another thing here, see these lines in the patch:

+	/* Start monitoring */
+	w83792d_write_value(client, W83792D_REG_CONFIG,
+			    (w83792d_read_value(client,
+						W83792D_REG_CONFIG) & 0xf7)
+			    | 0x01);

I believe that the mask should be 0x7e, rather than 0xf7. Could you
please change that and see if it helps?

Thanks,
-- 
Jean Delvare

  parent reply	other threads:[~2005-07-07 21:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-30 23:37 [lm-sensors] W83792D & Overtemperature LED on Supermicro Eric J. Bowersox
2005-06-30 23:51 ` Eric J. Bowersox
2005-07-01  2:33 ` Mark Studebaker
2005-07-01 17:44 ` Eric J. Bowersox
2005-07-02 18:37 ` Rudolf Marek
2005-07-06 17:41 ` Eric J. Bowersox
2005-07-07 21:19 ` Jean Delvare
2005-07-07 21:26 ` Jean Delvare [this message]
2005-07-07 22:11 ` Rudolf Marek
2005-07-08  0:22 ` Eric J. Bowersox
2005-07-08  9:42 ` Rudolf Marek
2005-07-08 12:28 ` Rudolf Marek
2005-07-08 18:19 ` Eric J. Bowersox

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=20050707212627.565d683a.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.