lkml.org 
[lkml]   [2017]   [May]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 00/16] Intel FPGA Device Drivers
On Tue, Apr 25, 2017 at 09:02:25PM +0100, One Thousand Gnomes wrote:
> > That is where we disagree. I do not see bitstream as firmware. For instance
> > now you can run OpenCL on some FPGA, so this is exactly like GPU we should
> > request open source stack from OpenCL down to bitstream.
>
> It's an accelerator with a bunch of firmwares where you load the right
> one. We've got lots of those in Linux already. Your GPU probably needs
> firmware as well in just the same way.

I stress again OpenCL on FPGA ie at runtime you load a program source
that is compiled at runtime and then lower to a bitstream which get
loaded on the FGPA at runtime. You can go look at how OpenCL works it
is not like fix firmware. OpenCL was done for GPU and everything needed
to support OpenCL is open source when it comes to GPU. On contrary with
FPGA the bitstream part is close source.

Sure GPU have firmware, those firmware run on realtime micro-controller
to dispatch job, handle GPU power management and other janitorial stuff.
For some GPU we even have open source firmware.

So FPGA with thing like OpenCL are more like GPU than like a fix hardware
that is program once and use like a device for which we need a firmware.
That is where we disagree on the characterization of things.


> > For me this is not enough (tool to load bitstream).
>
> Unfortunately that isn't likely to change for any major FPGA device in
> the near future. If you could load arbitrary bit patterns into an FPGA
> then in most cases that also means you could physically destroy the
> hardware.

I am just questioning the different standard in the kernel.

Jérôme

\
 
 \ /
  Last update: 2017-05-01 18:42    [W:0.121 / U:4.300 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site