Don't probe I2C addresses 0x40-0x47. We only probed them for the MAX6633,

which is a rare chip, and hard to identify anyway. Given that some I2C chips
have been reported to live at 0x47 and to hang the bus when probed, the
benefit just isn't worth the risk.


git-svn-id: http://lm-sensors.org/svn/lm-sensors/branches/lm-sensors-3.0.0@5235 7894878c-1315-0410-8ee3-d5d059ff63e0
This commit is contained in:
Jean Delvare committed 2008-05-04 16:43:12 +00:00
1 parent d43847b5df
commit a4c078b3df
2 files changed
+4 -1

No files matched your search

+1
View File
@@ -24,6 +24,7 @@ SVN-HEAD
Add National Semiconductor LM64 detection
Add Asus F8000 detection
Add Intel ICH10 (bus) detection
Don't probe I2C addresses 0x40-0x47
3.0.1 (2008-01-28)
documentation: Update the application writing guidelines
+3 -1
View File
@@ -1128,7 +1128,9 @@ use vars qw(@pci_adapters_sis5595 @pci_adapters_sis645 @pci_adapters_sis96x);
{
name => "Maxim MAX6633/MAX6634/MAX6635",
driver => "lm92",
i2c_addrs => [0x40..0x4f],
i2c_addrs => [0x48..0x4f], # The MAX6633 can also use 0x40-0x47 but we
# don't want to probe these addresses, it's
# dangerous.
i2c_detect => sub { lm92_detect(2, @_); },
},
{