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 08:53:18 -0300
Message-ID: <6a1e761a-6e41-9431-647d-5e374b4d4134@gmail.com> (raw)
In-Reply-To: <CAPweEDx_YjWZRzNb4qN7m4TundvyWAKTWhzPW1Eff4ph4kYOhw@mail.gmail.com>

Em 22/05/2020 23:41, Luke Kenneth Casson Leighton escreveu:
> 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, programming an FPGA board with a libre-SOC core, it would
have to be seriously optimized for size, not speed. These big FPGAs
boards are very expensive, compared to an equivalent Single Board Computer.

There is no way a relatively simple DSP algorithm, implemented on the
raw resources of an FPGA, could be beaten by a CPU/GPU core executing
this same algorithm, in the same FPGA.

Yes, people put CPU cores in FPGAs, but mainly to interface to the
outside world, providing a convenient interface to the FPGA. The main
data processing is still done in the free resources which remains after
placing the CPU core.

Of course, I could use parts of libre-SOC, like the floating points
pipelines. But, fixed-point algorithms are more common than
floating-point in FPGA applications.

Regards,

Cesar

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

  parent 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
2020-05-23 11:03         ` Luke Kenneth Casson Leighton
2020-05-23 11:53       ` Cesar Strauss [this message]
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=6a1e761a-6e41-9431-647d-5e374b4d4134@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