From: Jun Sun <jsun@mvista.com>
To: ashish anand <ashish_ibm@rediffmail.com>
Cc: linux-mips@linux-mips.org, jsun@mvista.com
Subject: Re: Problem in pci-bridge or NIC driver..?
Date: Wed, 9 Apr 2003 09:47:37 -0700 [thread overview]
Message-ID: <20030409094737.B31925@mvista.com> (raw)
In-Reply-To: <20030409145228.6142.qmail@webmail16.rediffmail.com>; from ashish_ibm@rediffmail.com on Wed, Apr 09, 2003 at 02:52:28PM -0000
On Wed, Apr 09, 2003 at 02:52:28PM -0000, ashish anand wrote:
> Hello,
>
> I am not able to conclude whether my problem belongs to pci-bridge
> side or towards my NIC drivers.
>
> 1> I am using thee network cards in my BSP process ..Intel 82557 ,
> RealTek 8139 and 3COM
> 3c905b ..all these three card works fine on different machine.
>
> 2>I have great difficulty in having serial eeprom and mdio
> interface both working and responding correctly to pci
> transactions.
>
> 3>in pci io space i can't use 82557 and RTL8139 cards as simply i
> amn't able to read serial eeprom and hence their MAC addresss
> remains undetected while on other machine same two card's serial
> eeprom responds fine in pci io space as well.
> serial eeprom response in pci mem space is fine but other nasty
> problems.
>
> However my 3com card serial eeprom responds perfectly fine on my
> developement system.
>
Is 3com's serial eeprom in IO space or MEM space? If it is in
MEM space, it probably means that your IO space is not setup
right. You need to use substractive decoding to translate
PCI IO address when you memory-map PCI IO space.
Which board/controller chip are you using?
If you use pci_auto to assign PCI resource, you should be able
to see the IO/MEM resources assigned to those cards. They
are very useful for probing the problem.
Jun
prev parent reply other threads:[~2003-04-09 16:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-09 14:52 Problem in pci-bridge or NIC driver..? ashish anand
2003-04-09 16:47 ` Jun Sun [this message]
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=20030409094737.B31925@mvista.com \
--to=jsun@mvista.com \
--cc=ashish_ibm@rediffmail.com \
--cc=linux-mips@linux-mips.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