Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 5 Current »

Date

Disclosures

 RISC-V Disclosure Video

Participants

 Meeting Participants

Name

Affiliation

Agenda

  • Partner Candidacy (RISC-V Labs policy)
  • Q1 Status Report Scheduled
    • 10xEngineers (March 11, 2025)
    • PLCT (February 25, 2025)
    • EPCC (February 11, 2025)
    • OSU/OSL (February 25, 2025)
  • Open Floor Topics
    • 10xEngineers
      • Was able to install Java and use the runner package, leveraging a shell script, and works good for self hosted runners.
      • Gitlab runner binary documentation added to the labs doc (notify Jeff)
      • When having time, will add updates for Teamcity,
      • Can we host a github runner (self managed), tried source code, but what is provided fetches a precompiled binary that cannot run on RISC-V.
    • PLCT
      • The boards in PLCT Lab is running well, and there have been no
        unplanned power outages in the past four weeks; no new developers have
        applied for ssh access; waiting for the delivery of Milk-V Megrez, it
        is estimated that several units will be online in March for CI
        services for the open source community.
      • The RISC-V Lab built by Nanjing Inchi has currently obtained 70 LicheePi 4A, 5 Unmatched, and some K230. It has started to provide some package building services for the Arch Linux community.
      • Hefei University of Technology (HFUT) intends to establish a RISC-V Lab in Anhui Province, China. Currently, some RISC-V equipment has been obtained through the RISC-V development board wandering project (of the Jiachen Project), and more than 50 students have started to learn RISC-V.
      • Known possible issues:
        • January 27 to February 5 is the Chinese New Year. Some office areas
          hosting RISC-V devices may be shut down and will be restored after the
          Spring Festival. We are currently confirming which areas of RISC-V
          boards can continue to serve.
  • EPCC
    • Brought wormhole PCIe accelerator online as part of the testbed with latest software API. All pretty stable and working well. Thinking about Carl's point about Fortran, we have lots of hardware and compilers etc available, and a list of the most popular HPC applications - some of these (and libraries) already on the testbed, this could be a foundation to explore some of the gaps/limits here
    • We have also done some work supporting driving wormhole (and grayskull) from Fortran via OpenMP target offload. Demoed this to Tenstorrent a couple of weeks ago, still lots of work to do but demonstrates the concepts.
  • OSU/OSL
    • No updates
  • RISC-V
    •  
  •  

Presentations

Title

Presenter

File

1

2

Notes & Action Items

  • 2025 Ecosystem Lab Partner Objectives
    • Setup CI environments for RISC-V Targets
      • Working on gitlab, todo github action runners
      • Potential to get buildbot working also look into Jenkins agents
    • Better understand what resources projects need
      • Ssh access, compile farm, etc???
      • On demand remote access containers?
    • Possible target considerations
      • Hack-a-thon resources
      • How to use Labs resources for Risc-v training
    • Modular use of extensible resources
      • Sensors
      • Gpu
      • Usb class compliant devices
      • gpio
    • Places to get people to collaborate and communicate
      • Forum, mailing list, slack, etc…
    • Reference architectures
      • Booting
      • server/automotive/mobile/ai
      • Hpc
    • Get more community knowledge better documented

  •  

Standard_2.png

  • No labels