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:56:30 +0000
Message-ID: <CAPweEDwN6Asy9rfq5+gE4a8+NJp8nqLyTNJYKPY_B_wohWdYRg@mail.gmail.com> (raw)
In-Reply-To: <CAC2bXD7fz6_KfymY5kMTFojHQsrmTGC2XZ958F1ju7s6tg-91A@mail.gmail.com>
On Sun, Mar 15, 2020 at 7:44 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> On Sun, Mar 15, 2020, 12:33 Immanuel, Yehowshua U <yimmanuel3@gatech.edu>
> wrote:
>
> > 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.
>
>
> In my opinion, dual ISAs is a significant advantage that basically no one
> else has, since it allows us to run both Power and RISC-V software at full
> speed, it's also useful for on a test server where people need to test both
> Power and RISC-V software (where QEMU isn't good enough).
from a commercial perspective, given that there doesn't exist any
mass-volume products that use RISC-V (just a lot of noise and a lot of
talk), it's not as attractive as it seems.
if however we assume that RISC-V *will* take off in mass-volume,
*then* it might become attractive.
however given that the RISC-V Foundation's reputation is now shot to
shit, and people know - loud and clear - that they are "Fake Open
Source", i highly doubt whether mass-commercial
*end-user-programmable* RISC-V systems will actually take off any time
in the next 8 to 12 years.
> Later (for Libre-SOC v2 or v3), it might be a good idea to add support for
> x86 and x86_64 user-mode since the patents for the base ISA will have
> expired by then. This would help give us an advantage since it would allow
> us to run legacy software.
now that *would* be good.
as we saw with the China ICT "Loongson G" architecture, even just the
base ISA having *partial* x86 hardware ISA support would give a
massive speed-boost of an emulated application.
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 [this message]
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
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=CAPweEDwN6Asy9rfq5+gE4a8+NJp8nqLyTNJYKPY_B_wohWdYRg@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