From: Kallol Biswas <kallol@efi.com>
To: linux-kernel@vger.kernel.org
Subject: eepro100 driver can't read serial eeprom that is beyond a bridge
Date: Fri, 15 Feb 2002 17:47:12 -0800 [thread overview]
Message-ID: <3C6DBA20.28E40161@efi.com> (raw)
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
next reply other threads:[~2002-02-16 1:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-16 1:47 Kallol Biswas [this message]
2002-02-23 0:40 ` eepro100 driver can't read serial eeprom that is beyond a bridge Kallol Biswas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C6DBA20.28E40161@efi.com \
--to=kallol@efi.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox