Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: Staf Verhaegen <staf@fibraservi.eu>
To: libre-riscv-dev@lists.libre-riscv.org
Subject: Re: [libre-riscv-dev] LibreSOC - RISCV and POWER dual architecture feasibility
Date: Sun, 15 Mar 2020 23:04:32 +0100
Message-ID: <d4305c62f6c80a0be1a34019bc36000341689b76.camel@fibraservi.eu> (raw)
In-Reply-To: <8C348DCE-274B-476B-8F61-C1BB5F1C3EC1@gatech.edu>

[-- Attachment #1.1: Type: text/plain, Size: 874 bytes --]

Immanuel, Yehowshua U schreef op zo 15-03-2020 om 19:52 [+0000]:
> > 
> > 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.
> 
> 
> Isn’t x86 kinda big - like a 1000+ instructions? How would this impact our power target…
> 
> But other than that, I’m all for adding x86 support.

If you consider implementing x86 instruction set you also need to
consider the risk of patent lawsuits being filed at you...

Risc-V instruction set is specially designed to only use features which
are not patented or for which the patents have expired. I did not dive
in the open licensing terms but I assume that includes patent licenses.

greets,
Staf.


[-- Attachment #2: Type: text/plain, Size: 177 bytes --]

_______________________________________________
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: 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 [this message]
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
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=d4305c62f6c80a0be1a34019bc36000341689b76.camel@fibraservi.eu \
    --to=staf@fibraservi.eu \
    --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