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] LibreSOC - RISCV and POWER dual architecture feasibility
Date: Sun, 15 Mar 2020 19:51:59 +0000
Message-ID: <CAPweEDz6KGOyQfcFV29WsC24esLHGFzWnqPL-3Dyp0-vX9r56Q@mail.gmail.com> (raw)
In-Reply-To: <884F8FEE-60FF-4580-A2E7-8AAA40A6DB6B@gatech.edu>
On Sun, Mar 15, 2020 at 7:33 PM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:
>
> OK.
>
> So to sum up - we have limited funding currently, and we want to have
> something to show hopefully by October -
we're *going* to meet the tapeout deadline in October. exactly what
with will be cut - in a draconian and clinical fashion - to *make*
that goal achievable.
> progress on RISCV is already well underway.
was.
*was* underway, until the RISC-V Foundation fucked us over, yes.
> Lets make this prominent on the website - that we’re currently doing Dual ISAs.
>
> Once we do get a lot of more funding, I would eventually like to move to only supporting one architecture which seems to be POWER right now. I say this because I believe supporting DUAL ISA down the road will cause more headaches than its worth.
well, once it's done it's done.
> Not that it isn’t possible, but its notably non-trivial and adds little value to most customers.
honestly i think you're right. if we were doing ARM or x86 Dual ISA,
i'd say it had "real value".
> We can explain this to our backers - people can be flexible - especially over a cup of tea.
>
> However for right now, the risk minimizing move (if I understand everything correctly) is to maintain the position of supporting both ISA with incremental additions of POWER.
basically, so as not to be critically dependent on investment.
one of the biggest mistakes that any entrepreneurial team can make is
to make plans that ASSUME - as a critical dependency - the "existence
of VC funding".
> Who knows, I could be wrong. Maybe people really would find a use for dual ISAs - but up front, to investor for example, and to me, it looks unnecessary.
if an investor drop USD $10m onto the project, tomorrow, RISC-V goes.
if they *don't*, then we carry on with the plan that we have, and that
*most likely* means an incremental bootstrap process by way of RV32
(Minerva), RV64, RV64GC *and then* POWER *and then* SimpleV
why?
each of those is a *SMALL* incremental step.
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: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6AC4EFD4-AA30-42C7-855A-CE68A62F107F@gatech.edu>
2020-03-15 3:17 ` Jacob Lifshay
2020-03-15 4:00 ` Luke Kenneth Casson Leighton
2020-03-15 7:59 ` Jacob Lifshay
2020-03-15 11:22 ` Luke Kenneth Casson Leighton
2020-03-15 12:09 ` [libre-riscv-dev] pearpc simulator running Luke Kenneth Casson Leighton
2020-03-15 5:10 ` [libre-riscv-dev] LibreSOC - RISCV and POWER dual architecture feasibility Hendrik Boom
2020-03-15 6:13 ` Jacob Lifshay
2020-03-15 7:18 ` Immanuel, Yehowshua U
2020-03-15 11:20 ` Luke Kenneth Casson Leighton
2020-03-15 18:19 ` Immanuel, Yehowshua U
2020-03-15 18:21 ` Immanuel, Yehowshua U
2020-03-15 18:26 ` Immanuel, Yehowshua U
2020-03-15 19:11 ` Luke Kenneth Casson Leighton
2020-03-15 19:16 ` Immanuel, Yehowshua U
2020-03-15 19:20 ` Immanuel, Yehowshua U
2020-03-15 19:24 ` Luke Kenneth Casson Leighton
2020-03-15 19:25 ` Luke Kenneth Casson Leighton
2020-03-15 19:23 ` Luke Kenneth Casson Leighton
2020-03-15 19:32 ` Immanuel, Yehowshua U
2020-03-15 19:43 ` Jacob Lifshay
2020-03-15 19:52 ` Immanuel, Yehowshua U
2020-03-15 19:57 ` Luke Kenneth Casson Leighton
2020-03-15 20:00 ` Immanuel, Yehowshua U
2020-03-15 20:05 ` Luke Kenneth Casson Leighton
2020-03-15 22:04 ` Staf Verhaegen
2020-03-15 22:10 ` Jacob Lifshay
2020-03-15 22:23 ` Adam Van Ymeren
2020-03-15 22:32 ` Luke Kenneth Casson Leighton
2020-03-16 0:25 ` Immanuel, Yehowshua U
2020-03-15 19:56 ` Luke Kenneth Casson Leighton
2020-03-16 7:14 ` Lauri Kasanen
2020-03-16 7:28 ` Jacob Lifshay
2020-03-16 8:53 ` Staf Verhaegen
2020-03-16 9:27 ` Lauri Kasanen
2020-03-16 10:34 ` Luke Kenneth Casson Leighton
2020-03-16 11:00 ` Staf Verhaegen
2020-03-15 19:51 ` Luke Kenneth Casson Leighton [this message]
2020-03-15 19:37 ` Immanuel, Yehowshua U
2020-03-15 19:07 ` Luke Kenneth Casson Leighton
2020-03-15 16:57 ` Hendrik Boom
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=CAPweEDz6KGOyQfcFV29WsC24esLHGFzWnqPL-3Dyp0-vX9r56Q@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