From: Dan Malek <dan@mvista.com>
To: ajay.kunnath@exgate.tek.com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Local-PCI bridge mapping
Date: Wed, 15 Nov 2000 18:52:39 -0500 [thread overview]
Message-ID: <3A1321C7.CAC069A0@mvista.com> (raw)
In-Reply-To: 21F9768AF088D211BF1C0008C71E5786014EED18@ap-bang-m02.india.tek.com
ajay.kunnath@exgate.tek.com wrote:
> I have a proprietary MPC860 board which has a PLX 9054 Local-PCI
> bridge. I am running the 2.4.0 version of the kernel from
> montavista.
The PLX isn't supported as a PCI bridge in the 8xx kernel......
The 2.4.0 version of the kernel isn't supported in the CDK for
the 8xx either....If anything works you are just lucky.
> My problem is that I am not able to map the configuration registers
> to any other address but 0x80000000.
What do you mean "map"? You use ioremap()? When?
> .... When I map it to 0x80000000, it
> works great, any other address and it just crashes.
Depending upon what you mean by "map", most PCI bridges rely on
well known physical (bus) address or/and chip selects to function
properly, just like other devices attached to the processor.
Tell us how the PLX decodes the configuration space access as a
target, how your system has attached the PLX to the processor,
and we can probably help. You are going to have to minimally write
a set of functions like those found in qspan_pci.c to accomodate
the PLX.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-11-15 23:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-15 11:43 Local-PCI bridge mapping ajay.kunnath
2000-11-15 23:52 ` Dan Malek [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-16 6:24 ajay.kunnath
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=3A1321C7.CAC069A0@mvista.com \
--to=dan@mvista.com \
--cc=ajay.kunnath@exgate.tek.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).