From: Felix Radensky <felix@embedded-sol.com>
To: linuxppc-dev@ozlabs.org
Subject: Re: FPGA access over PCI-E on MPC8536
Date: Sat, 19 Sep 2009 18:52:49 +0300 [thread overview]
Message-ID: <4AB4FE51.9050607@embedded-sol.com> (raw)
In-Reply-To: <1253176993.8375.345.camel@pasglop>
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 device in u-boot? That would possible tell you if
>> the HW is functioning or not.
>>
>>> Another question is what can cause PCI device memory be marked as
>>> disabled.
>> Good question, no idea how lspci decided to print [disabled]. Take a
>> look at lspci source and see :)
>
> Maybe the memory enable in the PCI command register isn't set ?
>
> If you don't have a kernel driver that sets it (by calling
> pci_enable_device) and u-boot doesn't set it then it's going
> to be off and you'll get hangs or machine checks trying to
> access the device...
>
> Just an idea...
Yes, that was my problem exactly ! Setting this bit via setpci
fixed it.
Thanks a lot for your help.
Felix
next prev parent reply other threads:[~2009-09-19 15:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-17 4:17 FPGA access over PCI-E on MPC8536 Felix Radensky
2009-09-17 6:48 ` Kumar Gala
2009-09-17 8:43 ` Benjamin Herrenschmidt
2009-09-19 15:52 ` Felix Radensky [this message]
2009-09-17 15:43 ` David Hawkins
[not found] ` <fa686aa40909180636jb2f8676k94a50b176319c249@mail.gmail.com>
2009-09-18 13:44 ` Grant Likely
2009-09-19 18:31 ` Leon Woestenberg
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=4AB4FE51.9050607@embedded-sol.com \
--to=felix@embedded-sol.com \
--cc=linuxppc-dev@ozlabs.org \
/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).