All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Boelstler <euphoria@arcor.de>
To: linuxppc-embedded@ozlabs.org
Subject: Re: MPC8548 PCIe / PCI support with BSP MPC8548CDS 02/24/2006
Date: Mon, 03 Jul 2006 08:38:04 +0200	[thread overview]
Message-ID: <e8ae0b$35e$1@sea.gmane.org> (raw)
In-Reply-To: <9FCDBA58F226D911B202000BDBAD467306DD12EC@zch01exm40.ap.freescale.net>

Hi,

Zhang Wei-r63237 schrieb:
> Yes, I think so. You can plug a PCIe ethernet card to test it. 

A single device always works.

> :-), Maybe it's need more study. Could you enable the DEBUG and post the kernel verbose message?

We added lots of debug output and made some modifications (mostly delays 
between calls to early_read_config_dword() and 
early_write_config_dword() in pci_auto.c) and came to the conclusion 
that generic bridge devices (PCIe-to-PCI), even in a cascaded setup of 
three bridges, work fine.

However a PCIe switch (PLX8516/8532) doesn't work. The MPC8548 only 
detects a single device (i.e. primary side of the switch).
We are going to analyze the problem more deeply soon. It seems that the 
configuration space of that devices isn't properly set up.

The provided patch doesn't make any difference, besides that it is moved 
to a location where the PPC itself is not detected.

Please keep us informed if there is any progress besides Freescale, as I 
will do.

Cheers,

   Florian

  reply	other threads:[~2006-07-03  6:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-28  5:27 MPC8548 PCIe / PCI support with BSP MPC8548CDS 02/24/2006 Zhang Wei-r63237
2006-07-03  6:38 ` 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-27  9:28 Zhang Wei-r63237
2006-06-27 16:06 ` 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='e8ae0b$35e$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.