From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 15 Feb 2002 20:41:03 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 15 Feb 2002 20:40:53 -0500 Received: from mail2.efi.com ([192.68.228.85]:1035 "HELO fcexgw02.efi.internal") by vger.kernel.org with SMTP id ; Fri, 15 Feb 2002 20:40:44 -0500 Message-ID: <3C6DBA20.28E40161@efi.com> Date: Fri, 15 Feb 2002 17:47:12 -0800 From: Kallol Biswas X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2-2 i686) X-Accept-Language: en MIME-Version: 1.0 To: linux-kernel@vger.kernel.org Subject: eepro100 driver can't read serial eeprom that is beyond a bridge Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org 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 the do_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