From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: LM83 driver
Date: Thu, 19 May 2005 06:24:06 +0000 [thread overview]
Message-ID: <20030723180958.649e4584.khali@linux-fr.org> (raw)
In-Reply-To: <20030703194558.60bc8955.khali@linux-fr.org>
Hi Zoleg,
Three weeks ago, you requested a driver for the LM83 you say you had on
your motherboard. I wrote the driver and told you about it, but we never
heard about you again. Why that? It's not very polite to you to make me
work for you and ignore me once the job is done...
Nevermind, I would need your help now. First I would like you to try the
driver. It's included in our latest release (2.8.0), or you can use CVS
for a slightly improved version. I'd really like to know if the chip is
detected by our sensors-detect script, and how the driver behaves.
Second, I would like you to unload the lm83 driver (rmmod lm83) and dump
the contents of your LM83 chip. You will need to find at which address
it is located (sensors-detect should tell you) and run the following
command:
i2cdump 0 0x18
(replace 18 with the address given by sensors-detect; if the chip is
located on a second I2C bus, replace 0 with 1).
Thanks.
--
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/
next prev parent reply other threads:[~2005-05-19 6:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 6:24 LM83 driver Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Greg KH
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Greg KH
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark D. Studebaker
2005-05-19 6:24 ` Greg KH
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Philip Pokorny
2005-05-19 6:24 ` Mark D. Studebaker
2005-05-19 6:24 ` Mark D. Studebaker
2005-05-19 6:24 ` Jean Delvare [this message]
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` ZOleg Matrix
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=20030723180958.649e4584.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.