From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yw0-f194.google.com (mail-yw0-f194.google.com [209.85.211.194]) by ozlabs.org (Postfix) with ESMTP id 0CDEAB7B73 for ; Fri, 18 Sep 2009 23:44:42 +1000 (EST) Received: by ywh32 with SMTP id 32so1175335ywh.15 for ; Fri, 18 Sep 2009 06:44:40 -0700 (PDT) MIME-Version: 1.0 Sender: glikely@secretlab.ca In-Reply-To: References: <4AB1B84F.8080606@embedded-sol.com> Date: Fri, 18 Sep 2009 07:44:39 -0600 Message-ID: Subject: Re: FPGA access over PCI-E on MPC8536 From: Grant Likely To: Felix Radensky Content-Type: multipart/alternative; boundary=000e0cd5c7c8641eda0473da5502 Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , --000e0cd5c7c8641eda0473da5502 Content-Type: text/plain; charset=ISO-8859-1 Can you access fpga memory from u-boot? Could very well be an fpga problem. Same thing can happen on xilinx parts when accessing an undefined register address via pci bridge --> plb bus --> ipif register block --> bad address. The pci core goes into some kind of retry loop with the plb bus (I'm wasn't the one to look at the pci analyzer, so I don't know the details), and it completely locks up. g. On Sep 16, 2009 11:02 PM, "Felix Radensky" wrote: Hi, On my custom MPC8536 based board running 2.6.31 kernel FPGA is connected via x2 PCI-E lane. FPGA is identified during PCI scan and is visible via lspci. 0000:01:00.0 Class ff00: Altera Corporation Unknown device 0004 (rev 01) Subsystem: Altera Corporation Unknown device 0004 Flags: fast devsel, IRQ 16 Memory at 98000000 (32-bit, non-prefetchable) [disabled] [size=1M] Capabilities: [50] Message Signalled Interrupts: Mask+ 64bit+ Queue=0/5 Enable- Capabilities: [78] Power Management version 3 Capabilities: [80] Express Endpoint IRQ 0 Capabilities: [100] Virtual Channel However when I attempt to access FPGA memory my mmapping it in userspace the read hangs. The same happens in kernel space. Does it happen because FPGA memory is marked as disabled, or because FPGA code is doing something wrong ? Another question is what can cause PCI device memory be marked as disabled. Thanks a lot. Felix. _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev --000e0cd5c7c8641eda0473da5502 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Can you access fpga memory from u-boot?

Could very well be an fpga problem.=A0 Same thing can happen on xilinx p= arts when accessing an undefined register address via pci bridge --> plb= bus --> ipif register block --> bad address.=A0 The pci core goes in= to some kind of retry loop with the plb bus (I'm wasn't the one to = look at the pci analyzer, so I don't know the details), and it complete= ly locks up.

g.

On Sep 16, 2009 11:02 PM, "Felix Radensky= " <felix@embedded-sol.com= > wrote:

Hi,

On my custom MPC8536 based board running 2.6.31 kernel
FPGA is connected via x2 PCI-E lane. FPGA is identified
during PCI scan and is visible via lspci.

0000:01:00.0 Class ff00: Altera Corporation Unknown device 0004 (rev 01) =A0 =A0 =A0 =A0Subsystem: Altera Corporation Unknown device 0004
=A0 =A0 =A0 =A0Flags: fast devsel, IRQ 16
=A0 =A0 =A0 =A0Memory at 98000000 (32-bit, non-prefetchable) [disabled] [s= ize=3D1M]
=A0 =A0 =A0 =A0Capabilities: [50] Message Signalled Interrupts: Mask+ 64bi= t+ Queue=3D0/5 Enable-
=A0 =A0 =A0 =A0Capabilities: [78] Power Management version 3
=A0 =A0 =A0 =A0Capabilities: [80] Express Endpoint IRQ 0
=A0 =A0 =A0 =A0Capabilities: [100] Virtual Channel


However when I attempt to access FPGA memory my mmapping it in userspace th= e read hangs. The same happens in kernel space. Does it happen because FPGA= memory is marked as disabled, or because FPGA code is doing something wron= g ?

Another question is what can cause PCI device memory be marked as
disabled.

Thanks a lot.

Felix.

_______________________________________________
Linuxppc-dev mailing list
Linuxppc= -dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

--000e0cd5c7c8641eda0473da5502--