From: atull <atull@opensource.altera.com>
To: Joel Holdsworth <joel@airwebreathe.org.uk>
Cc: <ijc+devicetree@hellion.org.uk>, <galak@codeaurora.org>,
<mark.rutland@arm.com>, <moritz.fischer@ettus.com>,
<pawel.moll@arm.com>, <robh+dt@kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [v2 2/2] fpga: Add support for Lattice iCE40 FPGAs
Date: Tue, 25 Oct 2016 09:47:49 -0500 [thread overview]
Message-ID: <alpine.DEB.2.02.1610250913530.14525@linuxheads99> (raw)
In-Reply-To: <c971d8f4-dbb4-8d6e-f8eb-028a0a95e6fb@airwebreathe.org.uk>
On Tue, 25 Oct 2016, Joel Holdsworth wrote:
>
> > Hi Joel,
> >
> > Thanks for submitting your driver!
> >
> > I didn't see any huge problems, just minor things below...
> >
> > Alan
> >
>
> Hi Alan, Thanks for your feedback. I've implemented all your suggestions and
> I'll resubmit.
>
> I had a question about the status of the fpga-manager framework. Is there
> active work going on? I was wondering if there were any patches for specifying
> a firmware file from device-tree?
Yes! I have submitted patches for doing exactly that. About to
submit v21. Here's patch 1 of v20:
https://patchwork.kernel.org/patch/9379859/
> and/or if there were any patches for loading
> firmware from userspace - something like this: "cat firmware.bin >
> /dev/fpga0"?
We discussed doing a char driver interface. That's where all this
started. It met with lots of resistance.
>
> Only being able to load firmware from kernel C-code is rather a limitation -
> though I suppose the framework is quite early in development.
>
> Thanks
> Joel
>
next prev parent reply other threads:[~2016-10-25 14:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 4:39 [v2 1/2] of: Add vendor prefix for Lattice Semiconductor Joel Holdsworth
2016-10-24 4:39 ` [v2 2/2] fpga: Add support for Lattice iCE40 FPGAs Joel Holdsworth
2016-10-24 21:55 ` atull
2016-10-24 22:28 ` Moritz Fischer
2016-10-25 4:51 ` Joel Holdsworth
2016-10-25 16:48 ` Moritz Fischer
2016-10-29 21:38 ` Joel Holdsworth
2016-10-25 5:05 ` Joel Holdsworth
2016-10-25 14:47 ` atull [this message]
2016-10-25 16:31 ` Joel Holdsworth
2016-10-25 16:34 ` 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=alpine.DEB.2.02.1610250913530.14525@linuxheads99 \
--to=atull@opensource.altera.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=joel@airwebreathe.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=moritz.fischer@ettus.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@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
Powered by JetHome