From: Andy Lutomirski <luto@amacapital.net>
To: Linus Walleij <linus.walleij@linaro.org>,
"casper@lists.berkeley.edu" <casper@lists.berkeley.edu>
Cc: Alan Tull <atull@altera.com>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>,
Pavel Machek <pavel@ucw.cz>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] FPGAs and how to program them from kernel
Date: Sun, 26 Jul 2015 16:35:20 -0700 [thread overview]
Message-ID: <CALCETrW07yfLW3Gv3Z0W6SoiSnsUVYf1=RnEHBvimO0c9ovVDg@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdYeud0s6ZyvW8n+0oPQ+S7uP1CTv22wQhvtwfD7iHKL2A@mail.gmail.com>
[cc: CASPER]
On Thu, Jul 23, 2015 at 4:26 AM, Linus Walleij <linus.walleij@linaro.org> wrote:
> On Thu, Jul 23, 2015 at 12:57 PM, Pavel Machek <pavel@ucw.cz> wrote:
>
>
>> 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).
>>
>> People that might be interested:
>
> Alan Tull <atull@altera.com>
> Is sending patchsets for this, and would be the primary person to
> invite for this topic:
> http://marc.info/?l=linux-kernel&m=143714949226387&w=2
I'm adding the CASPER list to see if anyone is interested. CASPER is
a big Berkeley-based project that, among other things, designs
powerful programmable boards with PowerPC CPUs running Linux and giant
FPGAs for signal processing and I/O.
https://casper.berkeley.edu/wiki/ROACH2
I haven't used ROACH2, but I've used ROACH a bunch, and it would be
really nice if there was a standard Linux API for dealing with FPGAs.
--Andy
next prev parent reply other threads:[~2015-07-26 23:35 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 [this message]
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='CALCETrW07yfLW3Gv3Z0W6SoiSnsUVYf1=RnEHBvimO0c9ovVDg@mail.gmail.com' \
--to=luto@amacapital.net \
--cc=atull@altera.com \
--cc=casper@lists.berkeley.edu \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linus.walleij@linaro.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