ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: ksummit-discuss@lists.linuxfoundation.org
Cc: Pavel Machek <pavel@ucw.cz>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] FPGAs and how to program them from kernel
Date: Sun, 26 Jul 2015 17:20:21 +0300	[thread overview]
Message-ID: <8128204.353R9quOj0@avalon> (raw)
In-Reply-To: <20150723105711.GB30929@amd>

On Thursday 23 July 2015 12:57:11 Pavel Machek wrote:
> Hi!
> 
> (Please cc me on replies)
> 
> FPGAs are common in embedded systems, where they can provide missing
> hardware interfaces, directly implement functionality, or provide
> custom hardware modules. These days they become available for servers,
> too, where they can act as high-performance co-processors (which are
> tricky to program).
> 
> There are very different requirements for FPGA that implements your
> SATA controller (so you need it for boot), and one where multiple
> userland applications directly access FPGA using it for different
> computations, needing FPGA netlist to be changed based on userspace
> needs. Yet, it would be nice to come up with single interface that can
> handle all the different applications, and is suitable for mainline
> kernel.
> 
> People that might be interested:
> 
> Michal Simek <michal.simek@xilinx.com>
> Dinh Nguyen <dinguyen@opensource.altera.com>
> <atull@opensource.altera.com>
> Steffen Trumtrar <s.trumtrar@pengutronix.de>
> Marek Vasut <marex@denx.de>
> Alan Cox

I've been working on V4L2 drivers for Xilinx FPGAs and I'm interested in this 
topic from that point of view. I see interactions with userspace being one of 
the most complex part, both in terms of triggering the reprogramming 
operations and handling applications that actively use the FPGA resources.

-- 
Regards,

Laurent Pinchart

  parent reply	other threads:[~2015-07-26 14:19 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
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 [this message]
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=8128204.353R9quOj0@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=pavel@ucw.cz \
    /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