On Wed, 6 Feb 2013, Jean Delvare wrote:
On Wed, 6 Feb 2013 00:26:06 +0100 (CET), Dag Wieers wrote:
I noticed on my second AppleTV device that it has a second address that
replied:
root ~ # i2cdetect 0
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0.
I will probe address range 0x03-0x77.
Continue? [Y/n]
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- 48 -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- 69 -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
The differences between both devices is that this one has the original
wireless device (b43) instead of the crystalhd mini-pci, and it doesn't
have the DVB USB stick inserted.
What could 48 be ?
This address was commonly used for simple temperature sensors (e.g.
LM75) but these are no longer so frequent. This could be virtually
anything. If you are willing to take the risk, you can provide a byte
dump of the chip with:
# i2cdump 0 0x48 b
at which point I can tell you if this is a device I recognize (a.k.a.
human version of sensors-detect.)
What risk am I taking wrt. probability and damage ? :)
And what could be the reason for the difference in behaviour of both
devices ? Could it be BIOS, firmware, ACPI, kernel, or is this pure
hardware-related ?
PS I now added dmidecode to the OpenELEC build system in order to find
other differences between both devices.
--
-- dag wieers, dag@xxxxxxxxxx, http://dag.wieers.com/
-- dagit linux solutions, info@xxxxxxxxx, http://dagit.net/
[Any errors in spelling, tact or fact are transmission errors]
_______________________________________________
lm-sensors mailing list
lm-sensors@xxxxxxxxxxxxxx
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
