---
title: About Linux (CPU Software)
slug: one/cpu-software/about
docTags: 
createdAt: 2026-06-10T18:09:43.572Z
---

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)](https://api.archbee.com/api/optimize/3StCFqarJkJQZV-7N79yY/eP94c40Lvgj_rkw75zDCF_about-cpu-main-image.png)

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-scripts)
  - [Rkbin](https://github.com/flipperdevices/rkbin)
  - [U-Boot](https://github.com/flipperdevices/u-boot)
  - [Falcon mode boot menu](https://github.com/flipperdevices/flipperos-boot-menu)
  - [Linux kernel](https://github.com/flipperdevices/flipper-linux-kernel)

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](https://api.archbee.com/api/optimize/3StCFqarJkJQZV-7N79yY/fmKVS7L3n9GCQEvOfYQD6_cpu-software-subproject-structure.jpg)

***

## ✅ 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](https://api.archbee.com/api/optimize/3StCFqarJkJQZV-7N79yY/3FGWKO8Lb0ICVhVdP7yC6_cpu-task-tracker.png "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\:rtTV7n0wnSuBvEb-Ov45y) 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](https://api.archbee.com/api/optimize/3StCFqarJkJQZV-7N79yY/G4i8tERYoXynIWLiSpWnW_os-buildbot.png "BuildBot web interface")

Once the build succeeds, full-disk images for all supported RK3576-based boards listed under [supported boards](docId:2qAVA-eHxy9yiQ7l-3w22) are published on the [web server](https://dl-linux-images.flipp.dev/full-img/), where they can be downloaded.

![OS build list](https://api.archbee.com/api/optimize/3StCFqarJkJQZV-7N79yY/a7iqZgI-Hfc2rY21h1ZYZ_os-build-list.png "Web server interface with build list")

:::hint{type="info"}
**See also:**

- [Build system](docId\:Za0yz2EoiekXoJiQD_rZf) — build system architecture and image build flow.
- [How to build a Linux image](docId\:Gjv9E-r2gBe20VjYUG0MG) — building the OS image locally.
- [How to install a Linux image](docId\:rWO9zLxTQmdVjBPxExkXD) — 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.

***

## 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

:::hint{type="info"}
**⚠️ 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](https://api.archbee.com/api/optimize/3StCFqarJkJQZV-7N79yY/mGixx9NyTNUXJZaGb-pS9_cpu-contribute-a-comment.jpg)

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:

::::WorkflowBlock
:::WorkflowBlockItem
**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.
:::

:::WorkflowBlockItem
**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](https://api.archbee.com/api/optimize/3StCFqarJkJQZV-7N79yY/7P5f3QhR3h-dqFuE-uJ1g_docs-good-vs-bad-comment.png)

**Attachment size limit:**

- Images: 10 MB
- Videos: 100 MB
:::

:::WorkflowBlockItem
**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](https://api.archbee.com/api/optimize/3StCFqarJkJQZV-7N79yY/-hkjRu_L86nNxsTKJguNG_cpu-contribute-via-pr.jpg)

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:2qAVA-eHxy9yiQ7l-3w22) works. Once a PR is merged, your changes become part of the official OS builds.

::::WorkflowBlock
:::WorkflowBlockItem
**Fork and clone the** [Linux build scripts](https://github.com/flipperdevices/flipperone-linux-build-scripts) **repository.**
:::

:::WorkflowBlockItem
**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\:Za0yz2EoiekXoJiQD_rZf).

To modify these components without touching the originals:

1. Fork each component repo on GitHub, then clone your fork locally.
2. Edit the build scripts to point at your forks.
:::

:::WorkflowBlockItem
**Make your changes** in the cloned repositories.
:::

:::WorkflowBlockItem
**Build the OS image locally.** Learn more on the [How to build a Linux image](docId\:Gjv9E-r2gBe20VjYUG0MG) page.
:::

:::WorkflowBlockItem
**Test your changes.** Flash the OS image to a supported board and check your changes. Learn [how to install a Linux image](docId\:rWO9zLxTQmdVjBPxExkXD).
:::

:::WorkflowBlockItem
**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.