From: atull <atull@opensource.altera.com>
To: Christoph Lameter <cl@linux.com>
Cc: Pavel Machek <pavel@denx.de>, Alan Tull <atull@altera.com>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] FPGAs and how to program them from kernel
Date: Tue, 28 Jul 2015 12:34:23 -0500 [thread overview]
Message-ID: <alpine.DEB.2.02.1507281233290.7196@linuxheads99> (raw)
In-Reply-To: <alpine.DEB.2.11.1507281055450.16348@east.gentwo.org>
On Tue, 28 Jul 2015, Christoph Lameter wrote:
> On Tue, 28 Jul 2015, Pavel Machek wrote:
>
> > Which tools would be that?
>
> FPGA firmware upload. Up/down. State determinations etc? Administrative
> tasks first. Lets do easy low hanging fruit first.
Exactly what my patchset is intended to do.
Alan Tull
>
> That way one can write scripts / tools to administer FPGAs from different
> manufacturers with the same commands.
>
> _______________________________________________
> Ksummit-discuss mailing list
> Ksummit-discuss@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
>
next prev parent reply other threads:[~2015-07-28 17:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 10:57 Pavel Machek
2015-07-23 11:26 ` Linus Walleij
2015-07-23 12:10 ` Pavel Machek
2015-07-23 13:00 ` Linus Walleij
2015-07-23 20:25 ` Christoph Lameter
2015-07-23 21:20 ` atull
2015-07-24 9:58 ` Michal Simek
2015-07-28 14:23 ` Pavel Machek
2015-07-28 15:58 ` Christoph Lameter
2015-07-28 17:34 ` atull [this message]
2015-08-04 16:03 ` Alan Tull
2015-07-23 22:05 ` Pavel Machek
2015-07-26 23:35 ` Andy Lutomirski
2015-07-24 20:59 ` H. Peter Anvin
2015-07-26 14:20 ` Laurent Pinchart
2015-07-27 0:14 ` Benjamin Herrenschmidt
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.1507281233290.7196@linuxheads99 \
--to=atull@opensource.altera.com \
--cc=atull@altera.com \
--cc=cl@linux.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=pavel@denx.de \
/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