OpenWrt meeting November 2024

OpenWrt One Status Update

For APK-related pull requests, please refer to: APK Pull Requests.
For APK-related issues, please visit: APK Issues.
Proposal to implement a “Message of the Day”:
- Inform users about the transition to APK, emphasizing the new command “apk add” instead of “opkg install.”
- Paul will provide further details.
Addressing issues related to ABI version changes: ABI Version Changes.
A wiki transition page will be created:
- Reference Eric’s contributions in the forum: Forum Discussion.
Acknowledgment of feedback regarding the communication of the APK transition:
- We apologize for any confusion caused.

Discussion on making APK the default package manager:
- Decision to continue using opkg for the 24.10 release.
Plan to conduct a release candidate (RC) testing phase in the coming days, led by Hauke.
Proposal to eliminate the USE_APK configuration option to reduce user confusion.

Focus on APK integration.
Exploration of Rust support within the core.
Consideration of LLVM integration in the core.
Development of a notification system: Notification System PR.
Discussion on the potential removal of usign and ucert in favor of a unified PKI solution, possibly utilizing “px5g” as proposed by Felix.
Increased use of ucode instead of Bash scripts.
Initiation of a forum thread to gather user feedback, to be managed by Paul.

Reference to the potential OpenWrt Summit in Central Europe in March/April: Summit Discussion.
- Current status indicates that this event may not proceed (Hauke).
- No response received regarding the status inquiry made on November 7 in Matrix.

Information on Battlemesh V17: Battlemesh Details.
Location: Sundhausen, Thuringia, Germany. Map Location.
Event Dates: June 10-17, 2025.
Proposal for collaboration with OpenWrt or co-locating an OpenWrt conference.
Advantages:
- Opportunity for in-person meetings.
- Minimal organizational effort required.
Disadvantages:
- Remote location with limited nearby accommodations.
- Potential shuttle service availability.
- Tent camping options available.
Support for endorsing Battlemesh.
Agreement to support travel for OpenWrt developers.
Paul will initiate a forum thread to discuss the use of donated funds for travel stipends.
Battlemesh intends to incorporate OpenWrt branding in their marketing, and we are supportive of this initiative.

The kernel is beginning to incorporate components relevant to our needs, particularly in drivers/net/phy.
This integration would facilitate better compatibility with projects not utilizing Cargo, specifically in include/meson.mk.
Daniel will engage with the Rust community within OpenWrt to encourage contributions to the core.

Discussion on including a full host and target build of LLVM and Clang to enhance support for Rust packages that depend on rust-bindgen.
This would enable the development of projects utilizing LLVM for JIT compilation on the target, such as Mesa LLVMPipe, Vulkan drivers, and OpenCL support (intel_clc).
Ansuel and Paul will investigate a centralized ccache solution to improve build efficiency. If issues arise with ccache, alternative solutions will be explored.

We propose the introduction of a weekly or monthly build of the video feed to provide precompiled binaries. Recent developments include support for local displays, with successful implementations of Wayland, Mesa (including Vulkan), GTK+4, WPEWebKit, and two ports of Doom. These have been tested on x86/64 architectures with Intel and AMD GPUs, as well as on ARM using Lima and Panfrost. Additionally, support has been established for SPI-connected MIPI-DBI displays on devices lacking dedicated GPU or video interfaces. WPEWebKit can facilitate local displays for applications such as Grafana, LuCI, or WiFi credentials via QR codes. Given the extensive scope of LLVM, Mesa, and WebKit, which significantly exceed the lines of code of the rest of OpenWrt combined, it is advisable not to include these in standard buildbot runs unless we implement CCACHE instances in each data center.
Ansuel and Paul will further investigate this proposal.

Daniel will explore the implementation of seccomp support for the RISC-V architecture.

Currently, LoongArch64 is unsupported due to a lack of available hardware for testing.
- We welcome any hardware donations to facilitate this effort.