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] next tasks
Date: Sat, 14 Mar 2020 18:28:29 +0000
Message-ID: <CAPweEDxzSvs49X5axA=Qii8sj-U3AzHz1mPzEBOWw44+u3iWrg@mail.gmail.com> (raw)
In-Reply-To: <07af6b25b38d1a9c7f0b973e1ebe0279@f-cpu.org>
On Sat, Mar 14, 2020 at 6:23 PM <whygee@f-cpu.org> wrote:
> I think the very existence of this project proves you can never
> reassure a paranoid ;-)
actually, although we can leverage the privacy aspect to attract
motivated developers, the main benefit to end-users is: dramatically
reduced costs due to no royalties and no massive NREs on hard macros
that need to be amortised across the cost of the chip.
the fact that the chip is privacy-respecting is a "side-benefit" for
the majority of people. the reduced cost is what will hook them.
l.
_______________________________________________
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: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPweEDyGztErPRa=9KLM9J02R1fLQ9Y23VY7UNAkfJ5yt-03PQ@mail.gmail.com>
[not found] ` <20200220093921.635c47f72ea2faf85dd352b7@gmx.com>
2020-03-12 14:32 ` Hendrik Boom
2020-03-12 14:43 ` Luke Kenneth Casson Leighton
2020-03-12 17:40 ` Jacob Lifshay
2020-03-13 6:44 ` Lauri Kasanen
2020-03-13 7:38 ` Jacob Lifshay
2020-03-13 8:04 ` Lauri Kasanen
2020-03-13 8:25 ` Jacob Lifshay
2020-03-13 10:13 ` Luke Kenneth Casson Leighton
2020-03-13 18:10 ` [libre-riscv-dev] Rustup security Jacob Lifshay
2020-03-14 18:13 ` [libre-riscv-dev] next tasks Hendrik Boom
2020-03-14 18:23 ` whygee
2020-03-14 18:28 ` Luke Kenneth Casson Leighton [this message]
2020-03-14 18:49 ` whygee
2020-03-15 2:47 ` [libre-riscv-dev] benefits of rust Jacob Lifshay
2020-03-15 5:18 ` Hendrik Boom
2020-03-15 5:42 ` Jacob Lifshay
2020-03-15 5:47 ` [libre-riscv-dev] [OT] Minecraft garbage collection Hendrik Boom
2020-03-15 6:41 ` Jacob Lifshay
2020-03-15 12:11 ` Luke Kenneth Casson Leighton
2020-03-16 13:22 ` Luke Kenneth Casson Leighton
2020-03-16 16:22 ` Jacob Lifshay
2020-03-16 16:24 ` Luke Kenneth Casson Leighton
2020-03-17 18:23 ` [libre-riscv-dev] next tasks Jacob Lifshay
2020-03-17 18:56 ` Luke Kenneth Casson Leighton
2020-03-16 18:30 ` Immanuel, Yehowshua U
2020-03-16 18:51 ` Jacob Lifshay
2020-03-16 22:53 ` Luke Kenneth Casson Leighton
2020-03-16 22:53 ` Luke Kenneth Casson Leighton
2020-03-16 23:12 ` Immanuel, Yehowshua U
2020-03-16 23:16 ` Immanuel, Yehowshua U
2020-03-16 23:42 ` 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='CAPweEDxzSvs49X5axA=Qii8sj-U3AzHz1mPzEBOWw44+u3iWrg@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