Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: Cesar Strauss <cestrauss@gmail.com>
To: libre-riscv-dev@lists.libre-riscv.org
Subject: Re: [libre-riscv-dev] daily kan-ban update 22may2020
Date: Sat, 23 May 2020 07:24:15 -0300
Message-ID: <5c96dbc3-3893-717a-6bea-5f2a9f8c3c5c@gmail.com> (raw)
In-Reply-To: <CAPweEDx_YjWZRzNb4qN7m4TundvyWAKTWhzPW1Eff4ph4kYOhw@mail.gmail.com>

On 05/22/2020 23:41, Luke Kenneth Casson Leighton wrote:
> On Saturday, May 23, 2020, Cesar Strauss <cestrauss@gmail.com> wrote:
> 
>>
>> My motivation to participate in Libre-SOC:
>>
>> A libre, supported, fully documented SoC, free of proprietary drivers,
>> firmware and bootloaders, that I can trust to use in my workstation,
>> server and as building blocks of scientific instruments.
> 
> 
> very cool.
> 
> and even in FPGA, one that had good number crunching capability might be
> useful, i assume.
> 

If you mean a libre FPGA, I am all for it.

A libre, supported, fully documented FPGA, with open architecture and
bitstream format.

If some people (hint!) were to start a libre-FPGA project, it would be
absolutely wonderful.

Independent of having a number crunching capability or not.

For synthesis, placing and routing, we do have libre tools. But, to
actually program the Configurable Logic Blocks (CLB), the routing switch
matrices, etc., inside the FPGA, we are forced to either use the
proprietary tools, or use libre tools based on a reverse engineered
bitstream format. It's a complete lock-in.

The community did produce a completely libre flow, from HDL to
bitstream, for Lattice chips. But the bitstream format is still
proprietary, and had to be reverse engineered. It is not assured that we
always will be able to do so, as new families are introduced. It is a
waste of effort, and features will be lacking.

I think there are experimental FPGAs developed in academia, but not
reaching commercial availability.

Cheers,

Cesar

_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

  reply index

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-22 15:02 Luke Kenneth Casson Leighton
2020-05-22 15:19 ` Michael Nolan
2020-05-22 15:39   ` Luke Kenneth Casson Leighton
2020-05-22 19:10 ` Cole Poirier
2020-05-22 19:18   ` Tobias Platen
2020-05-22 19:33     ` Luke Kenneth Casson Leighton
2020-05-23  1:56   ` Cesar Strauss
2020-05-23  2:41     ` Luke Kenneth Casson Leighton
2020-05-23 10:24       ` Cesar Strauss [this message]
2020-05-23 11:03         ` Luke Kenneth Casson Leighton
2020-05-23 11:53       ` Cesar Strauss
2020-05-23 12:08         ` Luke Kenneth Casson Leighton
2020-05-23 18:16     ` Cole Poirier
2020-05-22 19:59 ` Jacob Lifshay
2020-05-22 20:04   ` Luke Kenneth Casson Leighton
2020-05-22 20:12     ` Luke Kenneth Casson Leighton

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=5c96dbc3-3893-717a-6bea-5f2a9f8c3c5c@gmail.com \
    --to=cestrauss@gmail.com \
    --cc=libre-riscv-dev@lists.libre-riscv.org \
    /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

Libre RISC-V Mailing list Archives (accessible via public-inbox)

Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev

Example config snippet for mirrors


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git