From: steve@hassard.net (Stephen Hassard)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] report: ATI IXP use via i2c-piix4
Date: Mon, 19 Dec 2005 19:19:30 +0000 [thread overview]
Message-ID: <43A707C2.30900@hassard.net> (raw)
In-Reply-To: <43A700F5.4020606@hassard.net>
Rudolf Marek wrote:
> Hmm I dont like this.
>
> Will the sensors command produce correct result?
>
> Can you please provide dumps in this order:
>
> i2cdump 0 0x51
> i2cdump 0 0x51 c
> i2cdump 0 0x51
Hi Rudolf,
Here's the requested output:
---
i2cdump 0 0x51
No size specified (using byte-data access)
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0, address 0x51, mode byte
Continue? [Y/n]
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: 80 08 07 0d 0a 02 40 00 04 50 70 00 82 08 00 01 ??????@.?Pp.??.?
10: 0e 04 04 01 02 20 c0 00 00 00 00 3c 28 3c 23 40 ????? ?....<(<#@
20: 60 60 40 40 00 00 00 00 00 37 46 28 28 32 00 00 ``@@.....7F((2..
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 73 ..............?s
40: 7f 7f 7f 7f b0 00 00 00 00 4f 43 5a 34 30 30 31 ?????....OCZ4001
50: 30 32 34 45 4c 44 43 47 45 43 32 00 00 00 00 00 024ELDCGEC2.....
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
80: 05 09 02 00 00 00 00 00 00 00 00 00 00 00 00 00 ???.............
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
i2cdump 0 0x51 c
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0, address 0x51, mode byte consecutive read
Continue? [Y/n]
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: 80 08 07 0d 0a 02 40 00 04 50 70 00 82 08 00 01 ??????@.?Pp.??.?
10: 0e 04 04 01 02 20 c0 00 00 00 00 3c 28 3c 23 40 ????? ?....<(<#@
20: 60 60 40 40 00 00 00 00 00 37 46 28 28 32 00 00 ``@@.....7F((2..
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 73 ..............?s
40: 7f 7f 7f 7f b0 00 00 00 00 4f 43 5a 34 30 30 31 ?????....OCZ4001
50: 30 32 34 45 4c 44 43 47 45 43 32 00 00 00 00 00 024ELDCGEC2.....
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
80: 05 09 02 00 00 00 00 00 00 00 00 00 00 00 00 00 ???.............
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
i2cdump 0 0x51
No size specified (using byte-data access)
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0, address 0x51, mode byte
Continue? [Y/n]
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: 80 08 07 0d 0a 02 40 00 04 50 70 00 82 08 00 01 ??????@.?Pp.??.?
10: 0e 04 04 01 02 20 c0 00 00 00 00 3c 28 3c 23 40 ????? ?....<(<#@
20: 60 60 40 40 00 00 00 00 00 37 46 28 28 32 00 00 ``@@.....7F((2..
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 73 ..............?s
40: 7f 7f 7f 7f b0 00 00 00 00 4f 43 5a 34 30 30 31 ?????....OCZ4001
50: 30 32 34 45 4c 44 43 47 45 43 32 00 00 00 00 00 024ELDCGEC2.....
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
80: 05 09 02 00 00 00 00 00 00 00 00 00 00 00 00 00 ???.............
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
---
Thanks,
Steve Hassard
next prev parent reply other threads:[~2005-12-19 19:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-19 18:50 [lm-sensors] report: ATI IXP use via i2c-piix4 Stephen Hassard
2005-12-19 19:15 ` Rudolf Marek
2005-12-19 19:19 ` Stephen Hassard [this message]
2005-12-19 19:22 ` Stephen Hassard
2005-12-19 19:26 ` Rudolf Marek
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=43A707C2.30900@hassard.net \
--to=steve@hassard.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.