From: Anatolij Gustschin <agust@denx.de>
To: matthew.gerlach@linux.intel.com
Cc: linux-fpga@vger.kernel.org,
Alan Tull <atull@opensource.altera.com>,
Yi Li <yi1.li@linux.intel.com>,
Moritz Fischer <moritz.fischer@ettus.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] fpga manager: Add Altera CvP driver
Date: Thu, 20 Apr 2017 19:47:15 +0200 [thread overview]
Message-ID: <20170420194715.0ff0ccf1@crub> (raw)
In-Reply-To: <alpine.DEB.2.20.1704201021330.8224@mgerlach-VirtualBox>
Hi Matthew,
On Thu, 20 Apr 2017 10:29:34 -0700 (PDT)
matthew.gerlach@linux.intel.com matthew.gerlach@linux.intel.com wrote:
...
>Since you say the driver works with Arria-10, I thought I would give it
>a try with the Altera Arria10 PCIe DevKit I am using. I successfully
>compiled your patch as an out of tree module against a 3.10 kernel. The
>module successfully loaded and created instances for both boards in the
>host.
thanks for testing!
>Now that I have the driver instances running, I'm not sure howto actually
>perform CvP. Do you use a debugfs interface or something else? Do you
>use the sof or an rbf file?
I used the debugfs interface for first testing, now I'm using custom
fpga config interface driver, but it depends on many other drivers
and won't work without additional special hardware.
I use an rbf file. The v2 patch [1] used a module parameter to specify
firmware file name for a given PCIe device, but it is bypassing the
framework and is not acceptable for mainline.
Thanks,
Anatolij
[1] https://patchwork.kernel.org/patch/9582731
next prev parent reply other threads:[~2017-04-20 17:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 14:58 [PATCH v3] fpga manager: Add Altera CvP driver Anatolij Gustschin
2017-04-20 17:29 ` matthew.gerlach
2017-04-20 17:47 ` Anatolij Gustschin [this message]
2017-04-21 21:14 ` Li, Yi
2017-04-25 16:49 ` Yi Li
2017-04-26 16:36 ` Anatolij Gustschin
2017-04-26 17:10 ` Alan Tull
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=20170420194715.0ff0ccf1@crub \
--to=agust@denx.de \
--cc=atull@opensource.altera.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.gerlach@linux.intel.com \
--cc=moritz.fischer@ettus.com \
--cc=yi1.li@linux.intel.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