linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Florian Boelstler <euphoria@arcor.de>
To: linuxppc-embedded@ozlabs.org
Subject: MPC8548 PCIe / PCI support with BSP MPC8548CDS 02/24/2006
Date: Mon, 26 Jun 2006 12:48:27 +0200	[thread overview]
Message-ID: <e7oe1r$k2o$1@sea.gmane.org> (raw)

Hi,

I am currently working on a MPC8548-based development system.
Linux kernel version is 2.6.11 with patches delivered from Freescale 
(BSP MPC8548CDS 02/24/2006).

Kernel configuration contains a warning message for CONFIG_PEX:
"This requires hardware modification to work correctly if your CPU 
version < 2.0 and will break the PCI bus. [...]"

I was wondering whether enabling PCIe makes PCI bus functionality 
unusable at all (including kernel functionality for detecting devices 
behind a transparent PCI-to-PCI bridge).

Our setup connects a transparent PLX8516 PCI-to-PCI bridge to the PCIe 
port of the MPC8548 daughter board. Behind that bridge is another PCIe 
capable device.
MPC8548 is configured to run as PCIe host mode.

When trying to lookup the PCIe devices using lspci I can only see the 
PPC itself and the bridge.
However I cannot see the device(s) behind the bridge.

Is there another method for detecting PCI(e) devices?
Is "BSP MPC8548CDS 02/24/2006" the latest version corresponding to that 
hardware?

Thanks in advance,

   Florian

             reply	other threads:[~2006-06-26 12:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-26 10:48 Florian Boelstler [this message]
2006-06-26 13:25 ` MPC8548 PCIe / PCI support with BSP MPC8548CDS 02/24/2006 Vitaly Bordug
2006-06-26 14:36   ` Florian Boelstler
  -- strict thread matches above, loose matches on Subject: below --
2006-06-27  2:44 Zhang Wei-r63237
2006-06-27  8:39 ` Florian Boelstler
2006-06-27  9:28 Zhang Wei-r63237
2006-06-27 16:06 ` Florian Boelstler
2006-06-28  5:27 Zhang Wei-r63237
2006-07-03  6:38 ` Florian Boelstler
2006-07-03  7:54 Zhang Wei-r63237
2006-07-11 22:49 Ho Jeffrey-r26191
2006-07-19 16:45 ` Florian Boelstler
2006-08-11 13:48 ` 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='e7oe1r$k2o$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 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).