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] Myson MTP008 driver ported to 2.6 kernel
Date: Wed, 05 Oct 2005 20:46:14 +0000	[thread overview]
Message-ID: <20051005204529.3e233cf9.khali@linux-fr.org> (raw)
In-Reply-To: <20051004125511.GI7154@kira.glasswings.com.au>

Hi Andrew,

> > > /* Addresses to scan */
> > > static unsigned short normal_i2c[] = {0x2c, 0x2e, I2C_CLIENT_END};
> > 
> > 0x2d is missing.
> 
> Is the chip ever actually implemented at that address?

Why not? The datasheet says it can. It even says that the 24-pin
version of the chip always has this address.

> It may be that all known implementations use 0x2c for a single chip
> motherboard and 0x2c + 0x2e for a dual chip motherboard.

Why would we assume this? Adding 0x2d doesn't cost us much. The
original driver did support it (it supported 0x2c - 0x2e as a *range*,
not individual values!) and sensors-detect as well.

Thanks,
-- 
Jean Delvare

  parent reply	other threads:[~2005-10-05 20:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-04 14:56 [lm-sensors] Myson MTP008 driver ported to 2.6 kernel Andrew Pam
2005-10-04 21:37 ` Jean Delvare
2005-10-05 12:04 ` Andrew Pam
2005-10-05 13:32 ` Helge Bahmann
2005-10-05 15:25 ` Andrew Pam
2005-10-05 17:22 ` Jean Delvare
2005-10-05 18:41 ` Andrew Pam
2005-10-05 18:48 ` Andrew Pam
2005-10-05 18:51 ` Andrew Pam
2005-10-05 19:25 ` Tonu Samuel
2005-10-05 20:46 ` Jean Delvare [this message]
2005-10-05 21:46 ` Jean Delvare
2005-10-06 11:09 ` Andrew Pam
2005-10-06 11:13 ` Andrew Pam
2005-10-06 11:57 ` Jean Delvare
2005-10-06 12:20 ` Jean Delvare
2005-10-06 16:02 ` Andrew Pam
2005-10-09 20:03 ` Andrew Pam
2006-05-24  7:20 ` Andrew Pam
2006-05-24  8:39 ` Helge Bahmann
2006-05-24 12:57 ` Andrew Pam

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=20051005204529.3e233cf9.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.