wt/lm-sensors
1
0 Fork 0
mirror of https://github.com/lm-sensors/lm-sensors.git synced 2026-11-01 13:20:30 +00:00
Code Issues Packages Projects Releases Wiki Activity

Documented the new insmod parameters

Browse Source 
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@356 7894878c-1315-0410-8ee3-d5d059ff63e0
This commit is contained in:
Frodo Looijaard committed 1999-04-02 22:42:07 +00:00
1 parent 70a35fa068
commit 765c6e0c84
1 file changed
+9 -3
Download Patch File Download Diff File Expand all files Collapse all files
doc/busses/i2c-piix4
+9 -3
View File
@@ -18,11 +18,17 @@ Bus and device numbers may differ, but the function number must be identical
an entry, you have a PIIX4 SMBus controller.
On some computers (most notably, some Dells), the SMBus is disabled by
default. If you compile the i2c-piix4 module with '-DFORCE_PIIX4_ENABLE',
it will try to enable it. THIS IS VERY DANGEROUS! If the BIOS did not
default. If you use the insmod parameter 'force=1', the kernel module
will try to enable it. THIS IS VERY DANGEROUS! If the BIOS did not
set up a correct address for this module, you could get in big trouble
(read: crashes, data corruption, etc.). Try this only as a last resort
(try BIOS updates first, for example), and backup first!
(try BIOS updates first, for example), and backup first! An even more
dangerous option is 'force_addr=<IOPORT>'. This will not only enable the
PIIX4 like 'force' foes, but it will also set a new base I/O port address.
The SMBus parts of the PIIX4 needs a range of 8 of these addresses to
function correctly. If these addresses are already reserved by some other
device, you will get into big trouble! DON'T USE THIS IF YOU ARE NOT VERY
SURE ABOUT WHAT YOU ARE DOING!
The PIIX4E is just an new version of the PIIX4; it is supported as well. The
PIIX/PIIX3 does not implement an SMBus or I2C bus, so you can't use this