Hello Felix,
On Thu, Sep 17, 2009 at 6:17 AM, Felix Radensky wrote:
> 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.
>
I committed a PCI Express device driver for an Altera FPGA (chainin
Hi, Benjamin
Benjamin Herrenschmidt wrote:
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 ?
Can you access the
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
Hi Felix,
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.
:01:00.0 Class ff00: Altera Corporation Unknown device 0004 (rev 01)
Subsystem: Altera Corporation Unknown device 0004
> > 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 ?
>
> Can you access the device in u-boot? That
On Sep 16, 2009, at 11:17 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.
:01:00.0 Class ff00: Altera Corporation Unknown device 0004 (rev
01)
S
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.
:01:00.0 Class ff00: Altera Corporation Unknown device 0004 (rev 01)
Subsystem: Altera Corporation Unknown device 0004
