[Libre-soc-bugs] [Bug 394] New: Reach out to developers of 'BlackParrot' RV64GC Multicore SoC

bugzilla-daemon at libre-soc.org bugzilla-daemon at libre-soc.org
Sat Jun 20 01:40:41 BST 2020


            Bug ID: 394
           Summary: Reach out to developers of 'BlackParrot' RV64GC
                    Multicore SoC
           Product: Libre-SOC's first SoC
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: CONFIRMED
          Severity: enhancement
          Priority: ---
         Component: Source Code
          Assignee: lkcl at lkcl.net
          Reporter: colepoirier at gmail.com
                CC: libre-soc-bugs at lists.libre-soc.org
   NLnet milestone: ---

*will insert mailing list archive link here once it catches up...*

Going to create some bug reports related to what we can learn from a
multicore RV64GC SOC, "BlackParrot: A Linux-Capable Accelerator Host Multicore"

Especially their branch predictor and cache-coherency code, and their
14nm tapeout experience from july 2019.

Collection of info I found with a very quick search, to be followed up on

BlackParrot aims to be the default Linux-capable, cache-coherent, RV64GC
multicore used by the world.

Project Status

The next release of BlackParrot, v 1.0, is coming in January 2020, and will
contain support for 1 to 24-way cache coherent multicore, and include baseline
user and privilege mode functionality and run Linux.

A 14-nm BlackParrot multicore chip was taped out in July 2019.




"BlackParrot: An Agile Open Source RISC-V Multicore for Accelerator SoCs"


Published in: IEEE Micro ( Early Access )
Page(s): 1 - 1
Date of Publication: 20 May 2020
ISSN Information:
DOI: 10.1109/MM.2020.2996145
Publisher: IEEE

Open access of same:

Subtasks which may need their own bug report in the future:

* look at their branch predictor implementation
* look at their cache coherency implementation
* contact BlackParrot devs about their July 2019 14nm tapeout to see if they
are willing to talk about it, see if we can gain any useful insights from them

You are receiving this mail because:
You are on the CC list for the bug.

More information about the libre-soc-bugs mailing list