From: Philip Balister <philip@balister.org>
To: "H. Peter Anvin" <hpa@zytor.com>,
Alan Tull <delicious.quinoa@gmail.com>,
Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
Joel Becker <jlbec@evilplan.org>, Pavel Machek <pavel@denx.de>,
Alan Tull <atull@altera.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Michal Simek <monstr@monstr.eu>,
Michal Simek <michal.simek@xilinx.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mark Brown <broonie@kernel.org>,
Alessandro Rubini <rubini@gnudd.com>,
Steffen Trumtrar <s.trumtrar@pengutronix.de>,
Jason Cooper <jason@lakedaemon.net>,
Kyle Teske <kyle.teske@ni.com>,
Josh Cartwright <joshc@eso.teric.us>,
Nicolas Pitre <nico@linaro.org>, Felipe Balbi <balbi@ti.com>,
Mauro Carvalho Chehab <m.chehab@samsung.com>,
David Brown <davidb@codeaurora.org>,
Rob Landley <rob@landley.net>,
"David S. Miller" <davem@davemloft.net>,
Joe Perches <joe@perches.com>,
Cesar Eduardo Barros <cesarb@cesarb.net>,
Samuel Ortiz <sameo@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Dinh Nguyen <dinguyen@altera.com>,
Yves Vandervennet <rocket.yvanderv@gmail.com>
Subject: Re: [RFC PATCH v1] fpga manager framework with configfs interface
Date: Wed, 25 Jun 2014 11:54:17 -0700 [thread overview]
Message-ID: <53AB1AD9.7050108@balister.org> (raw)
In-Reply-To: <53AB1842.5020703@zytor.com>
On 06/25/2014 11:43 AM, H. Peter Anvin wrote:
> On 06/25/2014 11:37 AM, Alan Tull wrote:
>>
>> Yes, that's why I've recently felt more love for the firmware
>> interface. Since I need resume, it gives me a straightforward path to
>> be able to reprogram the FPGA without holding ram for the bitfile.
>> Also it is scalable.
>>
>
> The firmware interface is definitely pretty much ideal for the
> "production driver" use case... after all, the fact that the firmware
> happens to be an FPGA is to some degree an implementation detail (well,
> modulo fun things like showing up on the bus with one device ID and then
> disconnecting and reconnecting with another device ID after firmware load.)
>
> There are *so* many use cases for FPGA bitstreams...
Agreed!
Philip
>
> -hpa
>
>
>
prev parent reply other threads:[~2014-06-25 19:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1399411381-10902-1-git-send-email-atull@altera.com>
[not found] ` <1399411381-10902-2-git-send-email-atull@altera.com>
[not found] ` <20140513192330.GA6561@amd.pavel.ucw.cz>
[not found] ` <4190CF2D-6114-4652-90BA-899B5003ACCC@konsulko.com>
[not found] ` <20140513205641.GA4114@amd.pavel.ucw.cz>
2014-05-13 22:52 ` [RFC PATCH v1] fpga manager framework with configfs interface H. Peter Anvin
[not found] ` <20140625125449.GV30852@ZenIV.linux.org.uk>
[not found] ` <DF9393AB-E2A0-494A-A007-CB4A19A64E2A@konsulko.com>
[not found] ` <1cacd7d5-826b-40e0-8b5c-f3463fe7a809@email.android.com>
[not found] ` <D4CC4816-F293-427B-8D52-1D4F93635E2D@konsulko.com>
[not found] ` <CANk1AXQcqzu16OaT3LziWaroeyyuUoXU1CQy4e6BoGKLOk6fSg@mail.gmail.com>
[not found] ` <20140625175440.GC13460@obsidianresearch.com>
[not found] ` <CANk1AXS+JZCv7CMJW956PvnJ_YvebyyLVm_TkCPZr5TX1Wb4Yw@mail.gmail.com>
[not found] ` <53AB1842.5020703@zytor.com>
2014-06-25 18:54 ` Philip Balister [this message]
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=53AB1AD9.7050108@balister.org \
--to=philip@balister.org \
--cc=akpm@linux-foundation.org \
--cc=atull@altera.com \
--cc=balbi@ti.com \
--cc=broonie@kernel.org \
--cc=cesarb@cesarb.net \
--cc=davem@davemloft.net \
--cc=davidb@codeaurora.org \
--cc=delicious.quinoa@gmail.com \
--cc=dinguyen@altera.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=jason@lakedaemon.net \
--cc=jgunthorpe@obsidianresearch.com \
--cc=jlbec@evilplan.org \
--cc=joe@perches.com \
--cc=joshc@eso.teric.us \
--cc=kyle.teske@ni.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=nico@linaro.org \
--cc=pantelis.antoniou@konsulko.com \
--cc=pavel@denx.de \
--cc=rob@landley.net \
--cc=rocket.yvanderv@gmail.com \
--cc=rubini@gnudd.com \
--cc=s.trumtrar@pengutronix.de \
--cc=sameo@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