From: mds4@verizon.net (Mark Studebaker)
To: lm-sensors@vger.kernel.org
Subject: Problem with eeprom module in 2.9.0
Date: Thu, 19 May 2005 06:25:32 +0000 [thread overview]
Message-ID: <41F2854D.6020503@verizon.net> (raw)
In-Reply-To: <41DDAE4F.9030606@earthlink.net>
good diagnosis khali.
the 6300ESB definitely supports i2c block so there must be a bug in there somewhere.
I just reviewed the code and didn't see anything obvious.
David can you recompile i2c-i801 with the DEBUG=1 uncommented and
send us the dmesg output?
Jean Delvare wrote:
> Hi David,
>
>
>>>What's the PCI ID of this one? Maybe block transfers work OK for the
>>>E7501 but not for the E7520.
>>
>>The SMBus controller on the E7501 is 8086:2483 (rev 02).
>>The SMBus controller on the E7520 is 8086:25a4 (rev 02).
>
>
> OK, mystery explained then. 2483 is an ICH3, for which the I2C block
> transfers are not available at all - so MDS' changes did not affect
> this one. 25a4 is an 6300ESB, which is more recent and supposedly
> supports I2C block transfers, thus is affected by the change.
>
>
>>>(although I still can't get why lm93 doesn't trigger it).
>
>
> As noted by Mark Hoffman, the lm93 driver uses SMBus block transfers, not
> I2C block transfers. Second mystery explained. SMBus block transfers
> were implemented longer ago and seem to work.
>
> So the conclusion is that the (untested as of now) I2C block transfer
> recently added to the i2c-i801 driver by Mark Studebaker doesn't work
> for you, and most presumably doesn't work at all. I will leave it to
> Mark to propose a fix or debug tests to further analyze the problem.
>
> Thanks,
> --
> Jean Delvare
>
>
next prev parent reply other threads:[~2005-05-19 6:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 6:25 Problem with eeprom module in 2.9.0 David Knierim
2005-05-19 6:25 ` Jean Delvare
2005-05-19 6:25 ` Mark M. Hoffman
2005-05-19 6:25 ` Mark M. Hoffman
2005-05-19 6:25 ` Mark Studebaker [this message]
2005-05-19 6:25 ` Mark M. Hoffman
2005-05-19 6:25 ` Mark Studebaker
2005-05-19 6:25 ` Mark M. Hoffman
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=41F2854D.6020503@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.