Re: Packaging FPGA bitstreams

2016-07-29 Thread DJ Delorie
Nico Kadel-Garcia writes: > It's certainly a direct violation of the intent of the GPL licensed > tools that form so much of the base of Fedora's build environment. The GPL3 no longer requires us to provide tools used to compile such objects, as long as such tools are general-purpose and used unm

Fedora on RISC-V (was: Re: Packaging FPGA bitstreams)

2016-07-29 Thread Richard W.M. Jones
I wrote a rough initial plan, attached. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-builder quickly builds VMs from scratch http://libguestfs.org/virt-builder.1.html A plan for

Re: Packaging FPGA bitstreams

2016-07-29 Thread Solomon Peachy
On Fri, Jul 29, 2016 at 09:34:38AM +0100, Richard W.M. Jones wrote: > In many ways its no different from trusting your hardware. Did you > inspect the EDA tooling that was used to convert your CPU HDL down to > the photomask? Did you even get to see the source HDL for your CPU > (clue: unless you

Re: Packaging FPGA bitstreams

2016-07-29 Thread Peter Robinson
On Fri, Jul 29, 2016 at 12:07 PM, Josh Boyer wrote: > On Fri, Jul 29, 2016 at 4:34 AM, Richard W.M. Jones wrote: >> I have an idea to add RISC-V on FPGA as a Fedora "tertiary >> architecture" (I made up that term), if anyone is interested in that. > > Small sidebar. > > I've used the same term in

Re: Packaging FPGA bitstreams

2016-07-29 Thread Josh Boyer
On Fri, Jul 29, 2016 at 4:34 AM, Richard W.M. Jones wrote: > I have an idea to add RISC-V on FPGA as a Fedora "tertiary > architecture" (I made up that term), if anyone is interested in that. Small sidebar. I've used the same term in the past, and after thinking about it quite a bit recently I d

Re: Packaging FPGA bitstreams

2016-07-29 Thread Daniel P. Berrange
On Fri, Jul 29, 2016 at 02:19:49AM -0400, Nico Kadel-Garcia wrote: > On Thu, Jul 28, 2016 at 10:54 PM, Solomon Peachy wrote: > > On Thu, Jul 28, 2016 at 10:19:07PM -0400, Nico Kadel-Garcia wrote: > >> Still not reasonable for Fedora, I think. Red Hat, and RHEL, can > >> manage registered licensing

Re: Packaging FPGA bitstreams

2016-07-29 Thread Richard W.M. Jones
On Thu, Jul 28, 2016 at 10:54:16PM -0400, Solomon Peachy wrote: > On Thu, Jul 28, 2016 at 10:19:07PM -0400, Nico Kadel-Garcia wrote: > > Still not reasonable for Fedora, I think. Red Hat, and RHEL, can > > manage registered licensing to build this binary blob. But binary > > blobs with no tool chai

Re: Packaging FPGA bitstreams

2016-07-28 Thread Nico Kadel-Garcia
On Thu, Jul 28, 2016 at 10:54 PM, Solomon Peachy wrote: > On Thu, Jul 28, 2016 at 10:19:07PM -0400, Nico Kadel-Garcia wrote: >> Still not reasonable for Fedora, I think. Red Hat, and RHEL, can >> manage registered licensing to build this binary blob. But binary >> blobs with no tool chain to build

Re: Packaging FPGA bitstreams

2016-07-28 Thread Solomon Peachy
On Thu, Jul 28, 2016 at 10:19:07PM -0400, Nico Kadel-Garcia wrote: > Still not reasonable for Fedora, I think. Red Hat, and RHEL, can > manage registered licensing to build this binary blob. But binary > blobs with no tool chain to build htem? So it's okay to ship opaque-but-redistributable binar

Re: Packaging FPGA bitstreams

2016-07-28 Thread Nico Kadel-Garcia
On Thu, Jul 28, 2016 at 4:18 AM, Richard W.M. Jones wrote: > On Wed, Jul 27, 2016 at 10:28:38PM +0200, Kevin Kofler wrote: >> Richard W.M. Jones wrote: >> > Unfortunately to compile the source code to a bitstream, things get >> > very proprietary. For Xilinx, you have to install their proprietary

Re: Packaging FPGA bitstreams

2016-07-28 Thread Richard W.M. Jones
On Wed, Jul 27, 2016 at 10:28:38PM +0200, Kevin Kofler wrote: > Richard W.M. Jones wrote: > > Unfortunately to compile the source code to a bitstream, things get > > very proprietary. For Xilinx, you have to install their proprietary > > compiler, Vivado. It's not just proprietary but it has node

Re: Packaging FPGA bitstreams

2016-07-27 Thread Kevin Kofler
Richard W.M. Jones wrote: > Unfortunately to compile the source code to a bitstream, things get > very proprietary. For Xilinx, you have to install their proprietary > compiler, Vivado. It's not just proprietary but it has node-locked > licensing so it's user-hostile too. So this is a binary blo

Re: Packaging FPGA bitstreams

2016-07-26 Thread Richard W.M. Jones
On Tue, Jul 26, 2016 at 12:05:23PM -0400, Przemek Klosowski wrote: > Why are the proprietary bits in this case problematic, if we have > proprietary bits in the context of module (e.g. wireless) firmware > and CPU microcode patches? Right, in fact the proprietary bits have a firmware-like license

Re: Packaging FPGA bitstreams

2016-07-26 Thread Przemek Klosowski
On 07/26/2016 10:36 AM, Richard W.M. Jones wrote: RISC-V is an open source instruction set architecture (ISA). I was broadly looking at what it would take to support RISC-V in Fedora, Yay! great idea, and I hope RISC-V will gain broad acceptance, e.g. in the IOT field. ARM is great and ubiquito

Re: Packaging FPGA bitstreams

2016-07-26 Thread Josh Boyer
On Tue, Jul 26, 2016 at 10:36 AM, Richard W.M. Jones wrote: > In summary: > > - Compiling the Verilog source code to a bitstream requires highly >proprietary tools and will never be possible in Fedora. > > - Writing the bitstream to the FPGA is possible with GPL tools. > > - There are curre