From: Florian Boelstler <euphoria@arcor.de>
To: linuxppc-embedded@ozlabs.org
Subject: Re: MPC8548 PCIe / PCI support with BSP MPC8548CDS 02/24/2006
Date: Wed, 19 Jul 2006 18:45:03 +0200 [thread overview]
Message-ID: <e9lnie$voo$1@sea.gmane.org> (raw)
In-Reply-To: <3140C9D90FB6D911ABD7000F206DC92603D6E0FC@zhk08exm40.ap.freescale.net>
Hi Jeffrey,
> I have done the PCI config cycle under u-boot. This is very simple
and > able to find the PEX EP attached to the MPC8548.
> In this log, it is reading a pair of MPC8548E connected together
using > PEX.
> Please see the log below:
[ ... ]
thanks for sharing this piece of information.
I will investigate if this matches the way it is done in the kernel.
Thanks,
Florian
Ho Jeffrey-r26191 schrieb:
> Hi Florian,
>
>
> U-Boot 1.1.4 (Apr 12 2006 - 11:40:53)
>
> CPU: 8548_E, Version: 1.1, (0x80390011)
> Core: e500v2, Version: 1.0, (0x80210010)
> Clock Configuration:
> CPU:1333 MHz, CCB: 533 MHz,
> DDR: 266 MHz, LBC: 33 MHz
> L1: D-cache 32 kB enabled
> I-cache 32 kB enabled
>
> Board: MPC85xx Processor Card Rev. A.
> -- Boot Flash is U30
>
> SRIO: X4 2.5Gbps
> PEX : X4 2.5Gbps
> PCI1: 32 bit, async
> PCI2: disabled
> I2C: ready
> DRAM: Initializing
> DDR: 256 MB
> FLASH: 16 MB
> L2 cache 512KB: enabled
> In: serial
> Out: serial
> Err: serial
> Net: eTSEC0: PHY is Marvell 88E1111S (1410cc1)
> eTSEC1: PHY is Realtek RTL821x (1cc912)
> eTSEC2: PHY is Marvell 88E1111S (1410cc1)
> eTSEC3: PHY id ffffffff is not supported!
> eTSEC0, eTSEC1, eTSEC2 [PRIME], eTSEC3
> eTSEC0 & eTSEC1 in Reduce mode
> eTSEC2 & eTSEC3 in Reduce mode
> Hit any key to stop autoboot: 0
> MPC8548E_Rev1.1=> mm e000a000 <-setup command register
> e000a000: 8000f800 ? 80000004 Bus master, SERR, Memory space
> e000a004: 02001000 ? 06011000
> e000a008: 00000000 ? .
> MPC8548E_Rev1.1=> mm e000a000 <-Set secondary bus num = 1
> e000a000: 80000004 ? 80000018 Subordinate bus num = 3
> e000a004: 00000000 ? 00010300
> e000a008: 00000000 ? .
> MPC8548E_Rev1.1=> mm e000a000 <-Check PEX agent ID
> e000a000: 80000018 ? 80010000
> e000a004: 57191200 ? .
> MPC8548E_Rev1.1=> mm e000a000 <-Set PEX agent BAR0 (PEXCSRBAR)
> e000a000: 80010010 ? 80010010 PEXCSRBAR = 0x80000000
> e000a004: 00000000 ? 00000080 This is the PCI address space
> e000a008: 00000000 ? .
> MPC8548E_Rev1.1=> mm e000a000 <-Set PEX agent command register
> e000a000: 80010014 ? 80010004 Bus master, SERR, Memory space
> e000a004: 00001000 ? 06011000
> e000a008: 00000000 ? .
> MPC8548E_Rev1.1=>
> mw e000ac20 00080000; <-Set TAR = 0x80000000 (PCI address space)
> mw e000ac24 0; <-Set 32:64bit TAR = 0x0 (PCI address space)
> mw e000ac28 000a0000; <-Set WBA = 0xa0000000 (ECM, e500 address space)
> mw e000ac30 8004401A <-Set normal R/W, enable Outbound window
> MPC8548E_Rev1.1=>
> MPC8548E_Rev1.1=>
> MPC8548E_Rev1.1=> mm e000a000 <-check PEX agent BAR0 if written
> e000a000: 80010010 ?
> e000a004: 00000080 ? .
> MPC8548E_Rev1.1=> md a0000000 <-read PEX agent CCSRBAR address use 0xa0000000
> a0000000: 000ff700 00000000 00000000 00000000 ................
> a0000010: 00000000 00000000 00000000 00000000 ................
> a0000020: 00000000 00000000 00000000 00000000 ................
> a0000030: 00000000 00000000 00000000 00000000 ................
> a0000040: 00000000 00000000 00000000 00000000 ................
> a0000050: 00000000 00000000 00000000 00000000 ................
> a0000060: 00000000 00000000 00000000 00000000 ................
> a0000070: 00000000 00000000 00000000 00000000 ................
> a0000080: 00000000 00000000 00000000 00000000 ................
> a0000090: 00000000 00000000 00000000 00000000 ................
> a00000a0: 00000000 00000000 00000000 00000000 ................
> a00000b0: 00000000 00000000 00000000 00000000 ................
> a00000c0: 00000000 00000000 00000000 00000000 ................
> a00000d0: 00000000 00000000 00000000 00000000 ................
> a00000e0: 00000000 00000000 00000000 00000000 ................
> a00000f0: 00000000 00000000 00000000 00000000 ................
>
> Regards,
> Jeffrey Ho
> Freescale Semiconductor HK Ltd
> Tel: 852-26668050
>
>
>> -----Original Message-----
>> From:
>> linuxppc-embedded-bounces+r26191=freescale.com@ozlabs.org
>> [mailto:linuxppc-embedded-bounces+r26191=freescale.com@ozlabs.
>> org] On Behalf Of Florian Boelstler
>> Sent: Monday, June 26, 2006 6:48 PM
>> To: linuxppc-embedded@ozlabs.org
>> Subject: MPC8548 PCIe / PCI support with BSP MPC8548CDS 02/24/2006
>>
>> 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
>>
>> _______________________________________________
>> Linuxppc-embedded mailing list
>> Linuxppc-embedded@ozlabs.org
>> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>>
next prev parent reply other threads:[~2006-07-19 16:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-11 22:49 MPC8548 PCIe / PCI support with BSP MPC8548CDS 02/24/2006 Ho Jeffrey-r26191
2006-07-19 16:45 ` Florian Boelstler [this message]
2006-08-11 13:48 ` Florian Boelstler
-- strict thread matches above, loose matches on Subject: below --
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 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='e9lnie$voo$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.