eepro100 driver can't read serial eeprom that is beyond a bridge
Hi,
We have a system running 2.4.17 with the following configuration.
------North Bridge---------PCI-PCI-BRIDGE----82559ER
|
82559ER
# lspci
......
00:12.0 Ethernet controller: Intel Corp. 82559ER (rev 09)
.......
00:0f.0 PCI bridge: Digital Equipment Corporation DECchip 21152 (rev 03).........
02:01.0 Ethernet controller: Intel Corp. 82559ER (rev 09)
#insmod eepro100
.........
eth0: Intel Corp. 82559ER, l00:eC0:s85:/30:292:.9F, 4IRQ 12.
............
eth1: OEM i82557/i82558 10/100 Ethernet, FF:FF:FF:FF:FF:FF, IRQ 10.
........
It seems eepro100 driver can't read the eeprom from the 2nd card. I have
printed the data bits in thedo_eeprom_cmd routine, all were 1. Adjusting the delay did not help.
The eepro100 driver on 2.2 kernel works fine and even intel's e100 driver on
2.4.17 also works fine.
I guess there may be some timing issues involved.
Are the devices beyond a bridge imapped to I/O space properly in 2.4 kernel? Intel's driver reads the EEPROM
control register using memory cycles.
Kallol
The problem has been fixed changing the access to the eeprom comtrol register from I/O to memory.
The lines that have been changed:
do_eeprom_cmd() {
change io_outw to outw
and out_inw to inw
}speedo_found1() {
/*
iobase = pci_resource_start(pdev, 1);
*/
iobase = ioaddr;
}Quoted 46 lines · Kallol Biswas
Hi,
We have a system running 2.4.17 with the following configuration. ------North Bridge---------PCI-PCI-BRIDGE----82559ER | 82559ER # lspci ...... 00:12.0 Ethernet controller: Intel Corp. 82559ER (rev 09) ....... 00:0f.0 PCI bridge: Digital Equipment Corporation DECchip 21152 (rev 03).........
02:01.0 Ethernet controller: Intel Corp. 82559ER (rev 09)#insmod eepro100
.........
eth0: Intel Corp. 82559ER, l00:eC0:s85:/30:292:.9F, 4IRQ 12.
............eth1: OEM i82557/i82558 10/100 Ethernet, FF:FF:FF:FF:FF:FF, IRQ 10.
........It seems eepro100 driver can't read the eeprom from the 2nd card. I have
printed the data bits in thedo_eeprom_cmdroutine, all were 1. Adjusting the delay did not help.The eepro100 driver on 2.2 kernel works fine and even intel's e100 driver on
2.4.17 also works fine.I guess there may be some timing issues involved.
Are the devices beyond a bridge imapped to I/O space properly in 2.4 kernel? Intel's driver reads the EEPROM
control register using memory cycles.Kallol
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/