Changeset 1073
- Timestamp:
- 04/21/01 21:49:15 (12 years ago)
- Location:
- lm-sensors/trunk
- Files:
-
- 4 modified
-
CHANGES (modified) (2 diffs)
-
doc/chips/MODPARMS (modified) (3 diffs)
-
doc/chips/via686a (modified) (2 diffs)
-
kernel/chips/via686a.c (modified) (4 diffs)
Legend:
- Unmodified
- Added
- Removed
-
lm-sensors/trunk/CHANGES
r1070 r1073 22 22 If your make fails because it can't find <linux/i2c-proc.h>, you 23 23 forgot this step!!! 24 Also, mkpatch is probably broken right now.25 24 File doc/FAQ: Many updates and additions 26 25 File doc/chips/via686a: Claim support for 686b. … … 44 43 Module sensors: Disabled, moved to i2c package as i2c-proc.c 45 44 Module sis5595: Fix temp, add in4 for chip revision 0xc0. 46 Module via686a: Allow force =9191,address(for A7V/K7V boards)45 Module via686a: Allow force_addr=0xaddr (for A7V/K7V boards) 47 46 Module w83781d: Don't reinitialize as99127f chip; this may cause fan/temp 48 47 reading changes -
lm-sensors/trunk/doc/chips/MODPARMS
r412 r1073 1 All chip drivers have a few insmod module parameters in common. These 1 Paramters for modprobe and insmod 2 ================================= 3 4 All chip drivers have a few modprobe module parameters in common. 5 (Insmod can also be used, but we recommend modprobe so that 6 other required modules are automatically loaded.) These 2 7 parameters can be used when a module is inserted, to give some additional 3 8 information about how it should function. In this case, they tell where … … 13 18 14 19 Each adapter has a number of addresses on I2C/SMBus adapters and/or the 15 ISA bus that are always scanned if no insmodparameters are given. The20 ISA bus that are always scanned if no modprobe parameters are given. The 16 21 parameters below override those addresses that are scanned by default. 17 22 18 All insmodparameters described below take lists of positive integers23 All modprobe parameters described below take lists of positive integers 19 24 (unsigned, in the range of 0 to 65535) as their arguments. Integers 20 25 are separated by comma's, and may be given as ordinary decimal numbers, 21 26 as octal numbers (by starting them with a `0') or as hexadecimal numbers 22 27 (by starting them with a `0x'). More information can be found by 23 entering `man insmod'.28 entering `man modprobe' or `man insmod'. 24 29 25 30 `force', `force_*', `ignore' and `probe' parameters take pairs of numbers. … … 58 63 59 64 An example: 60 insmodlm78 force_lm79=9191,0x390 ignore=0,0x2d,1,0x20 probe_range=-1,0,0x7f65 modprobe lm78 force_lm79=9191,0x390 ignore=0,0x2d,1,0x20 probe_range=-1,0,0x7f 61 66 # ISA address 0x390 contains a LM79 62 67 # Scan all I2C addresses (from 0 to 0x7f) for all I2C adapters 63 68 # But skip address 0x2d on adapter 0, and address 0x20 on adapter 1 69 70 `force_addr' is a parameter used for PCI sensor adapters. 71 It is used to program the base address of the sensor registers. 72 This is required if the BIOS does not initialize the base address. -
lm-sensors/trunk/doc/chips/via686a
r1010 r1073 19 19 ----------------- 20 20 21 force =9191,addressSet the I/O base address. Useful for Asus A7V boards21 force_addr=0xaddr Set the I/O base address. Useful for Asus A7V boards 22 22 that don't set the address in the BIOS. Does not do a 23 23 PCI force; the via686a must still be present in lspci. … … 25 25 base address is not set. Otherwise the driver will 26 26 recognize both the old and the forced address. 27 28 force_via686a=9191,address Same as force. 27 Example: 'modprobe via686a force_addr=0x290' 29 28 30 29 -
lm-sensors/trunk/kernel/chips/via686a.c
r1015 r1073 58 58 #define THIS_MODULE NULL 59 59 #endif 60 61 /* If force_addr is set to anything different from 0, we forcibly enable 62 the PIIX4 at the given address. VERY DANGEROUS! */ 63 static int force_addr = 0; 64 MODULE_PARM(force_addr, "i"); 65 MODULE_PARM_DESC(force_addr, 66 "Initialize the Via686a at the given address"); 60 67 61 68 /* Addresses to scan. … … 527 534 return -ENODEV; 528 535 *address = val & ~(VIA686A_EXTENT - 1); 529 if (*address == 0) { 530 printk("via686a.o: base address not set - upgrade BIOS or use force=9191,addr\n"); 531 /* 532 If we do this then the module won't load and force won't work. 533 But unfortunately the above printk is printed even if we are doing a force. 536 if (*address == 0 && force_addr == 0) { 537 printk("via686a.o: base address not set - upgrade BIOS or use force_addr=0xaddr\n"); 534 538 return -ENODEV; 535 */ 536 } 537 /* 538 Moved below. 539 if (PCIBIOS_SUCCESSFUL != 540 pci_read_config_word(s_bridge, VIA686A_ENABLE_REG, &val)) 541 return -ENODEV; 542 if (!(val & 0x01)) { 543 printk("via686a.o: enabling sensors\n"); 544 pci_write_config_word(s_bridge, VIA686A_ENABLE_REG, 545 val | 0x01); 546 } 547 */ 539 } 540 if (force_addr) 541 *address = force_addr; /* so detect will get called */ 542 548 543 return 0; 549 544 } … … 566 561 } 567 562 568 if( kind >= 0) /* force or force_via686a */569 address &=~(VIA686A_EXTENT - 1);563 if(force_addr) 564 address = force_addr & ~(VIA686A_EXTENT - 1); 570 565 if (check_region(address, VIA686A_EXTENT)) { 571 566 printk("via686a.o: region 0x%x already in use!\n", … … 574 569 } 575 570 576 if( kind >= 0) { /* treat force and force_via686a equally */571 if(force_addr) { 577 572 printk("via686a.o: forcing ISA address 0x%04X\n", address); 578 573 if (PCIBIOS_SUCCESSFUL !=
