From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] Pitch Speech
Date: Sat, 11 Apr 2020 23:28:01 +0100
Message-ID: <CAPweEDwVDoqZ5oKDxzrTgX3-CSCHo186WChiDjxbx_SCjxdXRA@mail.gmail.com> (raw)
In-Reply-To: <914BA2FD-9C48-4DB5-97DE-92EC56F6E6E1@gatech.edu>
On Saturday, April 11, 2020, Immanuel, Yehowshua U <yimmanuel3@gatech.edu>
wrote:
> > lower power, lower software development costs, lower hardware costs
> > due to no licensing royalties.
>
> Yep yep. But the thing I’ve found really catches on is the GPU aspect.
>
> Basically - the question was - what else does LIbreSOC offer besides being
> an open ARM chip,
> and the answer that caught people’s attention was, we have a non-trash GPU
> solution.
yes.
here is those benefits i mentioned.
lower power because it is integrated (a hybrid) single CPUGPUVPU.
lower software development cost because not only is the source code
entirely libre, the drastically simpler driver model combined with the full
source means that single-stepping into the ACTUAL 3D ENGINE is possible.
that is flat out impossible on a proprietary GPU, not because you can't
single step across a kernel level PCIe bus to a completely different
processor, but how the hell do you synchronise debugging when the remote
instruction set is utterly different from the main core??
lower hardware costs due to no licensing is pretty obvious.
--
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next prev parent reply index
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-11 18:42 Immanuel, Yehowshua U
2020-04-11 19:56 ` Luke Kenneth Casson Leighton
2020-04-11 20:01 ` Immanuel, Yehowshua U
2020-04-11 22:28 ` Luke Kenneth Casson Leighton [this message]
2020-04-11 20:02 ` Immanuel, Yehowshua U
2020-04-11 22:29 ` 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=CAPweEDwVDoqZ5oKDxzrTgX3-CSCHo186WChiDjxbx_SCjxdXRA@mail.gmail.com \
--to=lkcl@lkcl.net \
--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