About Linux (CPU Software)

this page explains the structure of the linux (cpu software) sub project, provides links to all the repositories, and explains how they are used to build flipper one's official linux operating system about linux (cpu software) flipper one has two processors the high performance cpu (rockchip rk3576) runs linux and handles user applications, networking, high speed peripherals (usb3, pcie), ai acceleration (npu), and graphics output (hdmi, displayport) the low power mcu manages power, the display, button and touchpad input, and power bank mode the cpu software sub project consists of ✅ task tracker https //github com/orgs/flipperdevices/projects/11 🏭 os images build server https //linux images flipp dev/ 📁 github repositories linux build scripts https //github com/flipperdevices/flipperone linux build scriptsrkbin https //github com/flipperdevices/rkbinu boot https //github com/flipperdevices/u bootlinux kernel https //github com/flipperdevices/flipper linux kernelrkloader https //github com/flipperdevices/rkloader & gofastboot https //github com/flipperdevices/gofastboot we'd love your feedback — look for tasks tagged help wanted in the task tracker, or contribute directly to the github repositories via pull requests cpu software subproject structure ✅ task tracker all linux (cpu software) team tasks are tracked in the github project flipper one — linux (cpu software) https //github com/orgs/flipperdevices/projects/11/ there, you can see what the engineering team is working on and follow progress and discussions linux (cpu software) task tracker some tasks are open to the community and marked with a help wanted label you’re welcome to join the discussion on these tasks or submit your code suggestions — just make sure to read the contribution guide docid\ bdmplcyr sy0560cbhil first 🏭 os images build server our official os image build server automatically builds a new os image whenever changes are made to any of the github repositories included in the build process you can monitor the build status in the server’s web interface https //linux images flipp dev/ os buildbot once the build succeeds, full disk images for all supported rk3576 based boards listed under supported boards docid 5zr6i3iehbjbwmr3n9bd are published on the web server https //dl linux images flipp dev/full img/ , where they can be downloaded os build list see also build system docid\ isvwirz7zz0je7grahigs — build system architecture and image build flow how to build a linux image docid\ tem3oaprttfsdvuinbejc — building the os image locally how to install a linux image docid\ okmny6rizqvmrbxhb6k4h — installing a full disk os image on a supported board 📁 github repositories the linux (cpu software) sub project includes several public github repositories containing linux os components and flashing tools linux build scripts https //github com/flipperdevices/flipperone linux build scripts — linux os image build scripts for supported rk3576 based boards these scripts can be used to build the os image locally and are also used by the official os image build server to produce release images rkbin https //github com/flipperdevices/rkbin — rockchip rk3576 binaries, including ddr trainer and internal storage access binaries in maskrom mode u boot https //github com/flipperdevices/u boot — mirror of the official u boot bootloader sources with rk3576 specific patches not in mainline yet linux kernel https //github com/flipperdevices/flipper linux kernel — our fork of the latest mainline linux kernel release with patches not in mainline yet rkloader https //github com/flipperdevices/rkloader & gofastboot https //github com/flipperdevices/gofastboot — go tools for flashing images to rockchip devices via fastboot protocol how to contribute the linux (cpu software) sub project accepts contributions in two forms comments on open tasks for ideas, suggestions, improvements, and pull requests for code changes to os components such as the bootloader, kernels, build scripts, or flashing tools ‎ comment on an open task ⚠️ contributions only — no flooding to keep collaboration productive, please keep comments on topic open tasks are for contribution related discussion only if you have an idea or concern, first turn it into a concrete contribution and share it as a comment on a task for general questions or discussions, you're always welcome to join the conversation on social media https //x com/flipper rnd or discord https //discord com/invite/flipper ! contribute a comment on an open task open tasks that need the community's help are labeled help wanted if you have ideas on how to improve os components, you can contribute by commenting on the task and attaching screenshots, videos, code snippets, or links pick a task in the linux (cpu software) github project https //github com/orgs/flipperdevices/projects/11 , browse the open tasks and click the one labeled help wanted that you want to contribute to write your suggestion in the comments section, clearly describe your suggestion and, if helpful, attach a screenshot, video, code snippet, or link to a draft pull request good vs bad comment on a cpu software task attachment size limit images 10 mb videos 100 mb click comment to submit we review all comments carefully! we may ask additional questions about your idea in the task thread, so please watch for github notifications in your email ‎ contribute to linux os via a pull request contribute via a pull request contributing via pull requests allows anyone to propose changes to the components of our linux os you don't need a flipper one to test — any supported rk3576 based development board docid 5zr6i3iehbjbwmr3n9bd works once a pr is merged, your changes become part of the official os builds fork and clone the linux build scripts https //github com/flipperdevices/flipperone linux build scripts repository set up your own copies of os components during the build, the scripts pull public github repositories for components such as the kernel and u boot learn more build system docid\ isvwirz7zz0je7grahigs to modify these components without touching the originals fork each component repo on github, then clone your fork locally edit the build scripts to point at your forks make your changes in the cloned repositories build the os image locally learn more on the how to build a linux image docid\ tem3oaprttfsdvuinbejc page test your changes flash the os image to a supported board and check your changes learn how to install a linux image docid\ okmny6rizqvmrbxhb6k4h open pull requests to all repositories you modified we review all pull requests carefully! we may ask additional questions in the pr thread, so please watch for github notifications in your email