= Welcome to RISC-V BoF =

- Presentation of attendees
Some people interested in architecture, HW vendors, derivative distributions,
d-i team member

- Debian RISC-V documentation
  + https://wiki.debian.org/RISC-V

- Debian Toolchain status
  + Upstream LLVM now regards RISC-V as non-experimental https://github.com/llvm/llvm-project/commit/4e8d07fd7db2bd9d0c4384cb6b87e6bad1b4e120#diff-b7c61103e5b04a057783630466888503
    + Two issues with the llvm-toolchain-snapshot package being worked on (aurel32):
      + Doesn't know about multiarch
      + Target rv64g by default (no floating point)

GNU toolchain is fine
We're waiting for LLVM to apply patches sent to them
Debian Unstable - we can run GNOME \o/


- Debian installer status
  + https://lists.debian.org/debian-riscv/2019/06/msg00000.html

Karsten Merken is working on debian-installer
Missing possibility to boot with uboot from d-i?
WIP, details unknown

Coreboot support/status unknown (on some boards?)
   - https://github.com/coreboot/coreboot/tree/master/src/arch/riscv
   
uboot will most likely remain default boot way
(on sci-fi boards)
Not enough HW to know for sure what will be in future

Would be good to avoid having different solutions for different boards

- Debian Bootloader/Kernel support
  + seccomp support, seems to be used by more and more packages
     (to ask the naive question, is this a good or a bad thing?)

uboot; support is preliminary, one branch
pushed to upstream, but not integrated yet
We should be able to boot in 1-2 months
patches on uboot ML, but merge conflicts

Kernel - also not integrated yet (booting kernel from uboot)
BBL jumping to kernel directly
But need to be done same way as ARM does it
Open SBI needed on 5.2
Many different ways kernel can work with uboot

coreboot. Work stopped, previous developer moved on to other things


- RISC-V hardware availability
  + Unleashed SiFive board
  + Softcores that run on FPGA, Rocket, a 64-bit RISC-V in-order core
    - https://github.com/chipsalliance/rocket-chip

We don't have hardware, use mostly emulators
SiFive boards
Rocket64

- Build infrastructure status
  + Currently using QEmu based build daemons and 3 HFU developer boards.

qemu, used till April
Since then we have 3 SiFive boards
Qemu used only when long build queue, to fix it

- Package status
  + https://buildd.debian.org/stats/?arch=riscv64
  + https://buildd.debian.org/status/architecture.php?suite=unstable&a=riscv64&priority=
  + 28 packages currently in unreleased

88% of packages are built for Risc-V

- Plan for bullseye
there should be more hardware, many vendors are interested
But still HW canbe main blocker for bullseye
SiFive don't have local storage, crash from time to time

Microchip board, with SATA connectors, but costly
Need for more general solution

No support of Risc-V by DSA. They require server-class HW to be official
Not enough boards for now
But we need something that can be put into data center, and manage remotely
(so stability)