public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Felix Radensky <felix@embedded-sol.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Problem with transparent PCI-PCI bridge on Canyonlands
Date: Fri, 11 Dec 2009 00:01:01 +0200	[thread overview]
Message-ID: <4B216F9D.3050009@embedded-sol.com> (raw)
In-Reply-To: <2B3B2AA816369A4E87D7BE63EC9D2F2608922150@SDCEXCHANGE01.ad.amcc.com>

Hi,

Feng Kan wrote:
> Can you turn on the additional debug information. That will give a
> better
> Clue as to what part is hanging.
>   

I've enabled debugging in drivers/pci/pci.c. I'm seeing an infinite flow 
of messages

PCI:   Bus Dev VenId DevId Class Int
PCI Scan: Found Bus 0, Device 6, Function 0
PCI Scan: Found Bus 1, Device 6, Function 0
...
PCI Scan: Found Bus 255, Device 6, Function 0
PCI Scan: Found Bus 0, Device 6, Function 0
PCI Scan: Found Bus 1, Device 6, Function 0
...

Felix.
> Feng Kan
> AMCC Software
>
> -----Original Message-----
> From: u-boot-bounces at lists.denx.de [mailto:u-boot-bounces at lists.denx.de]
> On Behalf Of Felix Radensky
> Sent: Wednesday, December 09, 2009 10:02 AM
> To: u-boot at lists.denx.de; Stefan Roese
> Subject: [U-Boot] Problem with transparent PCI-PCI bridge on Canyonlands
>
> Hi,
>
> I'm running latest u-boot on 1GHz Canyonlands board and have trouble
> using 64-bit transparent PCI-PCI PLX 6254 bridge. With PLX evaluation
> board plugged into Canyonlands PCI slot u-boot hangs. With PCI support
> disabled u-boot works fine. The PLX board is OK, it was recognized by
> both u-boot and kernel on Freescale MPC8536DS board. On Canyonlands
> linux-2.6.32 silently resets the board when PLX is plugged in. Any ideas
> what could be wrong in u-boot ? I'll post a separate question to 
> linuxppc-dev.
>
> U-Boot 2009.11-rc2-00002-g386118a (Dec 09 2009 - 18:48:44)
>
> CPU:   AMCC PowerPC 460EX Rev. A at 1000 MHz (PLB=200 OPB=100 EBC=100)
>        Security/Kasumi support
>        Bootstrap Option H - Boot ROM Location I2C (Addr 0x52)
>        Internal PCI arbiter enabled
>        32 kB I-Cache 32 kB D-Cache
> Board: Canyonlands - AMCC PPC460EX Evaluation Board, 2*PCIe, Rev. 14
> I2C:   ready
> DRAM:  512 MB (ECC not enabled, 400 MHz, CL3)
> FLASH: 64 MB
> NAND:  256 MiB
> PCI:   Bus Dev VenId DevId Class Int
>
>
> Thanks a lot.
>
> Felix.
>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>   

  reply	other threads:[~2009-12-10 22:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-09 18:02 [U-Boot] Problem with transparent PCI-PCI bridge on Canyonlands Felix Radensky
2009-12-09 20:49 ` Wolfgang Denk
2009-12-09 22:10   ` Felix Radensky
2009-12-09 22:21     ` Felix Radensky
2009-12-09 23:01       ` Wolfgang Denk
2009-12-09 23:15         ` Felix Radensky
2009-12-09 23:16 ` Feng Kan
2009-12-10 22:01   ` Felix Radensky [this message]
2009-12-15  7:30     ` Felix Radensky
2009-12-15  9:10       ` Stefan Roese
2009-12-15 12:42         ` Felix Radensky
  -- strict thread matches above, loose matches on Subject: below --
2009-12-24 12:08 java33 at inwind.it
2009-12-24 14:34 ` Felix Radensky
2010-01-13 11:12   ` Felix Radensky

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=4B216F9D.3050009@embedded-sol.com \
    --to=felix@embedded-sol.com \
    --cc=u-boot@lists.denx.de \
    /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