Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: Jacob Lifshay <programmerjake@gmail.com>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: [libre-riscv-dev] processor and soc naming
Date: Wed, 11 Mar 2020 14:15:24 -0700
Message-ID: <CAC2bXD7xX+_WEj+DT18aZoQcZDr9wd+y5GhnhODA3Otn9oABBg@mail.gmail.com> (raw)
In-Reply-To: <327623BB-9D89-4666-A984-5B48FC2EC262@gatech.edu>

On Wed, Mar 11, 2020, 13:37 Immanuel, Yehowshua U <yimmanuel3@gatech.edu>
wrote:

> I’ve seen the term shakti passed around a lot now.
> I know it refers to a class of open source hardware, but what exactly is
> shakti in the context of LibreSOC?
>

From what I understand, Shakti is the common name used for the RISC-V cpu's
that are being designed by the RISE group as part of one of India's
universities: https://shakti.org.in/

Luke originally was working with them and so Libre-SOC is derived/inspired
by the Shakti M Class SOC. Libre-SOC has since evolved into its own
independent thing.

We should probably pick names for our processor core and SoC to
differentiate them from the Shakti M Class and from Libre-SOC as our
organization's name:

I suggest the Libre-SOC 1 for the SoC and Libre-CPU 1 for the processor
core. later iterations will be numbered 2, 3, etc. I registered
libre-cpu.org in case we want to use that.

Jacob
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

  reply index

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-11 20:35 [libre-riscv-dev] What is Shakti Immanuel, Yehowshua U
2020-03-11 21:15 ` Jacob Lifshay [this message]
2020-03-11 21:21   ` [libre-riscv-dev] processor and soc naming Jacob Lifshay
2020-03-11 22:17     ` Immanuel, Yehowshua U
2020-03-11 22:58     ` Luke Kenneth Casson Leighton
2020-03-11 23:12       ` Jacob Lifshay
2020-03-11 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=CAC2bXD7xX+_WEj+DT18aZoQcZDr9wd+y5GhnhODA3Otn9oABBg@mail.gmail.com \
    --to=programmerjake@gmail.com \
    --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