From: Jeff Studer <jstuder@aquilagroup.com>
To: "linuxppc-embedded@lists.linuxppc.org"
<linuxppc-embedded@lists.linuxppc.org>
Subject: PCI QSPAN2 resource conflicts
Date: Tue, 18 Dec 2001 12:09:06 -0700 [thread overview]
Message-ID: <3C1F9452.AB979826@aquilagroup.com> (raw)
Hello list,
I am working with a linux 2.4.2 kernel in an MPC860 custom board using a
Tundra QSPAN2 PCI controller. I have set up configuration space and can
successfully probe for PCI cards. When I load PCI drivers, I get into
trouble.
When I insmod the 3c59x.o module, I can access I/O space, but my MAC
address is read as 00:00:00:00:00:00. I can't find manuals for this
card to verify what is going wrong, but I can see data in the I/O space
when I use our ADS board and the mpc8bug program.
When I load another driver specific to this project, therefore the need
for PCI at all, I get resource conflicts. The 3c59x.o driver actually
uses the value I set bus->resource->start to, whereas the other PCI
driver uses 0.
I've tried various setups for the resource. I have set
bus->resource->start to the address in the QSPAN2's Slave0 address
setting. And I also tried do this and using the arch/ppc/mbxboot/pci.c's
functions: probe_addresses and map_pci_addrs.
I really wish there was a detailed HOWTO for all this, but in the
meantime, does anyone have any idea what are the proper steps to
complete this PCI support and/or what I may be doing wrong?
Thank you,
Jeff Studer
Software Engineer
Aquila Technologies Group
jstuder@aquilagroup.com
ph: 505-828-9100
fax: 505-828-9115
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-12-18 19:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-18 19:09 Jeff Studer [this message]
[not found] ` <3C1F8DE8.9FA7CECE@chinook.com>
2001-12-18 21:53 ` PCI QSPAN2 resource conflicts Jeff Studer
2001-12-19 15:44 ` Peter Desnoyers
2001-12-19 16:05 ` Peter Desnoyers
2001-12-19 17:27 ` Jeff Studer
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=3C1F9452.AB979826@aquilagroup.com \
--to=jstuder@aquilagroup.com \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).