From: Jos Huisken <jos.huisken@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v14 0/7] fpga area and fpga bridge framework
Date: Mon, 11 Jan 2016 10:54:06 +0100 [thread overview]
Message-ID: <56937BBE.6090904@gmail.com> (raw)
In-Reply-To: 1449790629-5517-1-git-send-email-atull () opensource ! altera ! com
On Thu, Dec 10, 2015 at 05:37:04PM -0600, atull@xxxxxxxxxxxxxxxxxxxxx wrote:
>
> For v14 I'm dropping the concept of "simple-fpga-bus" for "fpga-area"
> with reworked bindings.
Works great (using 4.4rc5)!!
With:
- Pantelis' overlay patches and dtc,
- Walter Goossens' sopcinfo with minor overlay patch
- additional board_info.xml
- and some python scripting using pyfdt
Its -almost- possible to automatically generate a bitfile with
appropriate overlay devicetree blob.
I only have an issue left w.r.t. phandles, I guess.
Using it now on de0-nano and veek kit.
next reply other threads:[~2016-01-11 9:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 9:54 Jos Huisken [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-12-10 23:37 [PATCH v14 0/7] fpga area and fpga bridge framework atull
2015-12-14 17:16 ` Moritz Fischer
2015-12-15 1:56 ` Alan Tull
2015-12-15 18:15 ` Moritz Fischer
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=56937BBE.6090904@gmail.com \
--to=jos.huisken@gmail.com \
--cc=linux-kernel@vger.kernel.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).