From: Kashyap Chamarthy <kchamart@redhat.com>
To: linux-riscv@lists.infradead.org, qemu-riscv@nongnu.org,
kvm-riscv@lists.infradead.org
Subject: [CFP] RISC-V Devroom at FOSDEM 2027
Date: Tue, 27 Oct 2026 22:13:13 +0100 [thread overview]
Message-ID: <auET6VbZLtXTUDsQ@kchamart.csb> (raw)
Hello!
We are pleased to announce[1] the Call for Participation (CFP) for the
RISC-V devroom at FOSDEM 2027.
FOSDEM 2027 (https://fosdem.org/2027/) will take place on the 30th and
31st January, 2027 in Brussels, Belgium.
The RISC-V devroom is on January 31st (Sunday afternoon).
Important dates
---------------
- 01 December 2026: Talk submission deadline
- 15 December 2026: Final schedule announcement
- 31 January 2027: RISC-V devroom
About the RISC-V devroom
------------------------
The RISC-V devroom aims to bring software & firmware developers,
toolchain maintainers, and hardware designers to discuss upstreaming
efforts and hard technical problems that can't be solved over email.
This devroom is a collaborative effort, and is organized by folks
actively working in the RISC-V ecosystem.
Suggested topics
----------------
Any RISC-V-related topics that fit the spirit of free and open source
software (FOSS) are welcome. Some topics to consider:
- RISC-V hardware (e.g. cores, SoCs, accelerators)
- Operating system porting, kernels, and hypervisors
- Toolchains: compilers, linkers, and debuggers
- Firmware and boot (e.g. OpenSBI, EDK2, U-Boot)
- Emulation (e.g. QEMU, Spike)
- ISA-level updates relevant to the Linux ecosystem and RVA23
readiness
- Performance and correctness tools (e.g. perf, Valgrind)
- Language runtimes and their RISC-V enablement, maintenance, and
performance (e.g. Go, OpenJDK, Node.js, Rust, Python)
- Package ecosystems and build systems (e.g. riscv64 prebuilt packages
and build support across npm, pip, Cargo, Maven, Go modules)
- Applications and middleware (e.g. riscv64 porting, RVV-optimized
code paths)
We are also interested in experience reports and technical work that
help make complete, production-relevant FOSS workloads available,
usable, and well-supported on RISC-V.
Submit a talk
-------------
Please visit the FOSDEM 2027 Pretalx website:
https://pretalx.fosdem.org/fosdem-2027/cfp. Your submission should
include:
- The title and subtitle of your talk (please be clear and descriptive)
- Select "RISC-V devroom" as the track
- A good abstract of a couple of paragraphs (be thoughtful with AI use)
- A short bio and contact information
- Relevant URLs
We suggest a talk length of 15-20 minutes plus 5 minutes of Q&A, since
the devroom runs for half a day this year. With good planning, one can
pack quite a punch in 15 minutes.
Presentations will be recorded and streamed. Sending your proposal
implies giving permission to have your presentation recorded and
distributed together with your slides under a Creative Commons CC-BY
license.
Regards,
Kashyap Chamarthy
Ludovic Henry
(On behalf of the devroom committee)
* * *
[1] Also on the FOSDEM list:
https://lists.fosdem.org/hyperkitty/list/fosdem@lists.fosdem.org/thread/K63XKEFUWSSZF6UTWFXFOPO5F2GNM3XX/
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
reply other threads:[~2026-10-27 21:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=auET6VbZLtXTUDsQ@kchamart.csb \
--to=kchamart@redhat.com \
--cc=kvm-riscv@lists.infradead.org \
--cc=linux-riscv@lists.infradead.org \
--cc=qemu-riscv@nongnu.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox