ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: atull <atull@opensource.altera.com>
To: Christoph Lameter <cl@linux.com>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>,
	Pavel Machek <pavel@denx.de>,
	Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
	Alan Tull <atull@altera.com>,
	yvanderv@altera.com
Subject: Re: [Ksummit-discuss] [TECH TOPIC] FPGAs and how to program them from kernel
Date: Thu, 23 Jul 2015 16:20:10 -0500	[thread overview]
Message-ID: <alpine.DEB.2.02.1507231552020.7582@linuxheads99> (raw)
In-Reply-To: <alpine.DEB.2.11.1507231524530.364@east.gentwo.org>

On Thu, 23 Jul 2015, Christoph Lameter wrote:

> On Thu, 23 Jul 2015, Linus Walleij wrote:
> 
> > >> > People that might be interested:
> 
> I would be very very interested in the subject matter. Anything that helps
> creating some abstraction layer that allows the open source development of
> tools on top.
> 
> _______________________________________________
> Ksummit-discuss mailing list
> Ksummit-discuss@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
> 

Jason is another person who may be interested in this topic:
Jason Gunthorpe = jgunthorpe at obsidianresearch.com

My work has been to get a uniform API for FPGA programming into the
kernel along with an interface for controlling reprogramming.  My
current patchset separates the two so that if the interface I am
proposing doesn't meet somebody's use needs, another interface
can be written to use the API functions.

http://marc.info/?l=linux-kernel&m=143714949226387&w=2

Topics that have been discussed in the mailing list could be included 
here:

 * At least two different basic use models:
   * FPGA as hardware (containing harware devices that need drivers)
   * FPGA as accelerator.  If FPGA is an accelerator, it could be
     allocated in a malloc-like thing - Alan Cox's proposal.
 * Device Tree Overlays as an interface in the "FPGA as Hardware" use,
   where loading an overlay will cause FPGA reconfiguration, bridges
   getting enabled, and devices being created, drivers probed.  The
   code for accomplishing all this is actually quite small.
 * Some use cases are complicated systems that need a lot of userspace
   to bring things up in a sequenced way (may need another interface
   with lots of userspace control and FPGA status available to
   userspace).
 * Security issues that arise if FPGA programming can be controlled
   from userspace.
 * How to control the bridges. Some hardware needs the bridges disabled
   during FPGA programming.  How to conceptualize this in the device tree.
 * It is likely that these different use cases will best be suited by
   different interfaces.

Alan Tull

atull at opensource.altera.com is a good email for me for mailing
list purposes (to avoid Outlook).

  reply	other threads:[~2015-07-23 21:58 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 [this message]
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
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.1507231552020.7582@linuxheads99 \
    --to=atull@opensource.altera.com \
    --cc=atull@altera.com \
    --cc=cl@linux.com \
    --cc=jgunthorpe@obsidianresearch.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=pavel@denx.de \
    --cc=yvanderv@altera.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