From: mds4@verizon.net (Mark Studebaker)
To: lm-sensors@vger.kernel.org
Subject: lm_sensors2/prog/detect sensors-detect
Date: Thu, 19 May 2005 06:24:53 +0000 [thread overview]
Message-ID: <408290DD.60109@verizon.net> (raw)
In-Reply-To: <20021107235845.0037e195.khali@linux-fr.org>
I see.
fixed, sorry.
mds
Jean Delvare wrote:
>>unless I'm missing something, there are no more accesses to the bus
>>at that address in scan_adapter() after the detection function
>>returns, so it isn't necessary.
>
>
> Wrong. There can be more than one possible chip at a given address. For
> example we detect the MAX6900 at 0x50 after the EEPROMs. After your
> change, I suspect that we actually detect it at 0x30 (where it cannot
> be) instead.
>
> Even without that, I think we should never rely on the order of the
> entries in @chips_id, nor on the fact that some addresses are used by a
> limited number of chips. These are thing that can change quickly and
> nobody will remember that part of the detection code depended on a
> condition that isn't true anymore.
>
next prev parent reply other threads:[~2005-05-19 6:24 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 6:23 lm_sensors2/prog/detect sensors-detect Jean Delvare
2005-05-19 6:23 ` Jean Delvare
2005-05-19 6:23 ` Jean Delvare
2005-05-19 6:23 ` Jim Morris
2005-05-19 6:23 ` Jean Delvare
2005-05-19 6:23 ` Jim Morris
2005-05-19 6:23 ` Jean Delvare
2005-05-19 6:23 ` Jean Delvare
2005-05-19 6:23 ` Jean Delvare
2005-05-19 6:24 ` Jim Morris
2005-05-19 6:24 ` Jim Morris
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jim Morris
2005-05-19 6:24 ` Mark D. Studebaker
2005-05-19 6:24 ` Jim Morris
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jim Morris
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jim Morris
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark M. Hoffman
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark M. Hoffman
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark Studebaker [this message]
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` 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=408290DD.60109@verizon.net \
--to=mds4@verizon.net \
--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.