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: Thu, 10 Dec 2009 00:21:10 +0200 [thread overview]
Message-ID: <4B2022D6.7040104@embedded-sol.com> (raw)
In-Reply-To: <4B202073.6090200@embedded-sol.com>
Hi, Wolfgang
Felix Radensky wrote:
> Hi, Wolfgang
>
>
>
>> --------------------------------------^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>
>> Did you try running in another configuration, like 800-nor or
>> 1066-nor?
>>
>>
>>
> I did try 600-nor and 800-nor, but that didn't change anything. With
> 1066-nor
> u-boot hangs earlier, the console messages show
>
> U-Boot 2009.11-rc2-00002-g386118a (Dec 09 2009 - 18:48:44)
>
> CPU: AMCC PowerPC 460EX Rev. A at 1066.667 MHz (PLB=266 OPB=88 EBC=88)
> 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, 533 MHz, CL4)
>
> Felix.
>
>
Actually, 1066-nor is not different from other configurations. Switching
to 1066-nor requires power-cycle, it's not enough to simply run "reset"
command.
Anyway, in this configuration u-boot also hangs when PLX board is
plugged in.
Felix.
next prev parent reply other threads:[~2009-12-09 22:21 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 [this message]
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
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=4B2022D6.7040104@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 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.