From: Peter Ryser <Peter.Ryser@xilinx.com>
To: Mike Wellington <wellington@lucent.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: ppc4xx_find_bridges( ) hangs kernel on Xilinx ML300 (PCI)
Date: Mon, 19 Apr 2004 13:48:02 -0700 [thread overview]
Message-ID: <40843B02.6080907@xilinx.com> (raw)
In-Reply-To: <40842D14.9040708@lucent.com>
The PCI support that is currently included in the Linux kernel tree is
for the V2PDK based OPB -> PCI bridge. It will not work with the EDK
based OPB -> PCI bridge, i.e. you will find exactly what you see.
Please download the EDK reference design for ML300 from
http://www.xilinx.com/ise/embedded/edk_examples.htm (design #6). The
design contains the V2PDK based bridge (including the pcore therefor)
and, thus, the Linux kernel will work fine with that design.
We are currently working on moving to the EDK based bridge and the Linux
kernel tree will be patched once this work is completed.
- Peter
Mike Wellington wrote:
>
> Hi-
> I am trying to port the Xilinx PCI code to
> an embedded linux kernel. The code calls
> ppc4xx_find_bridges( ) during the kernel initialization
> and hangs the kernel.
>
> I built the GPL 2.4 kernel from the Open Source
> archives and it hangs also.
>
> Then I copied ppc405_pci.c from the GPL source
> to my kernel tree and copied head_4xx.S from the
> GPL source to my kernel tree and it still
> hangs.
>
> I'm starting to wonder if there is something
> wrong with the PCI support for the Xilinx OCP PCI
> core.
>
> Does anybody have a working PCI device on a
> Xilinx Virtex-II Pro using the Xilinx-supplied
> PCI core?
>
> -mike wellington
> wellington@lucent.com
> anyplatform@bithead.com
>
>
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-04-19 20:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-01 14:32 PREEMPT problems Colin LEROY
2004-04-02 0:29 ` Benjamin Herrenschmidt
2004-04-02 0:56 ` Benjamin Herrenschmidt
2004-04-02 16:00 ` Michel Dänzer
2004-04-02 16:43 ` Michel Dänzer
2004-04-03 3:06 ` Benjamin Herrenschmidt
2004-04-03 12:56 ` Michel Dänzer
2004-04-04 2:20 ` Benjamin Herrenschmidt
2004-04-06 0:51 ` Benjamin Herrenschmidt
2004-04-06 23:28 ` Michel Dänzer
2004-04-06 23:33 ` Benjamin Herrenschmidt
2004-04-02 9:57 ` Wolfram Quester
2004-04-19 14:26 ` ppc4xx_find_bridges( ) hangs kernel on Xilinx ML300 (PCI) Mike Wellington
2004-04-19 19:48 ` Mike Wellington
2004-04-19 20:48 ` Peter Ryser [this message]
2004-04-19 20:54 ` Mike Wellington
2004-04-19 20:58 ` PCI - i *thought* the edk2 was what I was using! Mike Wellington
2004-04-19 22:05 ` Peter Ryser
2004-04-19 22:13 ` did you give me the right ml300_edk*.zip link? Mike Wellington
-- strict thread matches above, loose matches on Subject: below --
2004-04-19 20:55 ppc4xx_find_bridges( ) hangs kernel on Xilinx ML300 (PCI)] Mike Wellington
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=40843B02.6080907@xilinx.com \
--to=peter.ryser@xilinx.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=wellington@lucent.com \
/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).