From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "B.J. Buchalter" <bj@mhlabs.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Problem with PCIe -> PCI bridge on MPC8377E-RDB
Date: Wed, 12 Aug 2009 19:56:05 +1000 [thread overview]
Message-ID: <1250070965.3587.1.camel@pasglop> (raw)
In-Reply-To: <2D2EDFA8-E51F-4A2D-BEB7-8F9258518DA1@mhlabs.com>
On Tue, 2009-08-11 at 23:25 -0400, B.J. Buchalter wrote:
> I don't know the model of the board off the top of my head.
>
> I do know that it uses the Texas Instruments XIO2000A/XIO2200 PCI
> Express-to-PCI Bridge (rev 03), with the TSB82AA2 OHCI Link behind the
> bridge.
>
> The same board definitely works as expected in a Mac Pro.
I've had problems on embedded 4xx with some of those guys. I think
there's a problem with the TI bridge, either it needs more time to
settle after reset or it doesn't cope with a second reset by the kernel
after the FW reset ,I don't remember... but there's definitely something
fishy with that bridge or something a bit too "tight" on spec we do on
both FSL and 44x that doesn't please that bridge.
Cheers,
Ben.
> In doing some Google searches about this, I have seen the TI part
> listed in the PCI configuration of folks running linux (though
> probably on Intel) and apparently having no problems with the busses
> behind the bridge being enumerated.
>
> I am guessing that the problem is related the the PCIe root complex on
> the 8377, but I am just guessing.
>
> Is PCIe known to work on the MPC837x?
>
> Thanks!
>
> B.J. Buchalter
>
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
prev parent reply other threads:[~2009-08-12 9:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 22:27 Problem with PCIe -> PCI bridge on MPC8377E-RDB B.J. Buchalter
2009-08-12 1:43 ` Kumar Gala
2009-08-12 3:10 ` B.J. Buchalter
2009-08-12 1:43 ` Kumar Gala
2009-08-12 3:25 ` B.J. Buchalter
2009-08-12 5:20 ` Kumar Gala
2009-08-12 6:14 ` B.J. Buchalter
2009-08-12 9:56 ` Benjamin Herrenschmidt
2009-08-12 9:56 ` Benjamin Herrenschmidt [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=1250070965.3587.1.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=bj@mhlabs.com \
--cc=linuxppc-dev@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 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).