From: Florian Boelstler <euphoria@arcor.de>
To: linuxppc-embedded@ozlabs.org
Subject: Re: MPC8548 PCIe / PCI support with BSP MPC8548CDS 02/24/2006
Date: Tue, 27 Jun 2006 18:06:05 +0200 [thread overview]
Message-ID: <e7rl1v$gul$1@sea.gmane.org> (raw)
In-Reply-To: <9FCDBA58F226D911B202000BDBAD467306D93192@zch01exm40.ap.freescale.net>
Hi,
Zhang Wei-r63237 schrieb:
> It's an add-on PCIe patch. We have tested it on MPC8641, but we have no PCIe-PCI bridge on MPC8548 platform to do more test. So if you verify it, I'll commit it. :)
We did the hardware fix described in the BSP user's manual to make PCIe
work (according to the manual section 2.1, step 3).
I.e.
1) removed R193 and R194 on the carrier card (rev 1.2)
2) removed RN1 on the CPU daughter card
2a) connected pad3 of RN1 to pin3 of U12 (IRQ0)
2b) connected pad2 of RN1 to pin4 of U12 (IRQ1)
Does this fix the interrupt polarity problem (as well)?
We applied the provided kernel patch as well.
IMHO that patch just moves the local PCIe root-complex "out-of-space" so
no detection of that one occurs any more.
This is what actually happens when "lspci" is run.
However we still don't see any devices behind the PCIe switch (e.g. a
transparent PLX8516). It seems that the enumeration process (traversing
through the bus hierarchy) in the kernel is somehow disabled.
Bottom line: Only one device accessible at all on the PCIe port.
Any further ideas?
Thanks,
Florian
next prev parent reply other threads:[~2006-06-27 16:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 9:28 MPC8548 PCIe / PCI support with BSP MPC8548CDS 02/24/2006 Zhang Wei-r63237
2006-06-27 16:06 ` Florian Boelstler [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-11 22:49 Ho Jeffrey-r26191
2006-07-19 16:45 ` Florian Boelstler
2006-08-11 13:48 ` Florian Boelstler
2006-07-03 7:54 Zhang Wei-r63237
2006-06-28 5:27 Zhang Wei-r63237
2006-07-03 6:38 ` Florian Boelstler
2006-06-27 2:44 Zhang Wei-r63237
2006-06-27 8:39 ` Florian Boelstler
2006-06-26 10:48 Florian Boelstler
2006-06-26 13:25 ` Vitaly Bordug
2006-06-26 14:36 ` Florian Boelstler
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='e7rl1v$gul$1@sea.gmane.org' \
--to=euphoria@arcor.de \
--cc=linuxppc-embedded@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.