HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
raspberrypi
linux
C2012–2026
raspberrypi / linux

linux

Kernel source tree for Raspberry Pi-provided kernel builds. Issues unrelated to the linux kernel should be posted on the community forum at https://forums.raspberrypi.com/

34Distinct people
35Mentions
0Explicit recommenders
13.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Kernel source tree for Raspberry Pi-provided kernel builds. Issues unrelated to the linux kernel should be posted on the community forum at https://forums.raspberrypi.com/

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 6:01:08 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year35 dated mentions

Observed mentions: 2012-10-24 11:57:18 UTC to 2026-04-15 07:10:21 UTC.

02462012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20122013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 7 mentions; 2 submissions, 5 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC101
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC101
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC000
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC202
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC101
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC101
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC404
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC505
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC404
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC202
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC202
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC725
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC303
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC202

From the project README

An excerpt from the repository, fetched Nov 12, 2026.

Read the project’s introduction
Linux kernel There are several guides for kernel developers and users. These guides can be rendered in a number of formats, like HTML and PDF. Please read Documentation/admin-guide/README.rst first. In order to build the documentation, use make htmldocs or make pdfdocs. The formatted documentation can also be read online at: https://www.kernel.org/doc/html/latest/ There are various text files in the Documentation/ subdirectory, several of them using the Restructured Text markup notation. Please read the Documentation/process/changes.rst file, as it contains the requirements for building and running the kernel, and information about the problems which may result by upgrading your kernel. Build status for rpi-6.12.y: Build status for rpi-6.18.y:
Read the full README on GitHub

What Hacker News says

7 sources
I'm really mixing two things and wasn't very clear about it. The pico can kinda deep sleep but it requires an external wakeup trigger. It can't deep sleep from its own clock. Even so its deep sleep is pretty high power compared to most embedded chips. The zero (w) and zero 2 w don't have the equivalent of suspend-to-ram with a low sleep current. I'm not sure if that's a limitation of the SOC or the driver or both, but rpi was fairly clear it wasn't in the cards: https://github.com/raspberrypi/linux/issues/1281
In Extreme Pi Boot Optimization
I see the Raspberry Pi model B+ available right now on Adafruit for $30. It has a single core 700 MHz CPU and 512M RAM. The Raspberry Pi Zero 2 W is available right now for $15 with a 1 GHz 64 bit quad core CPU and 512 MB RAM. So it seems to me that you can get a Raspberry Pi SBC today, that has higher or equal specs in every regard, for a lower cost than the original. Am I missing something? Looking at https://github.com/raspberrypi/linux, I scrolled a few pages of commits and didn't even see one from outside the Raspberry Pi org. I'm picking through their merged PRs and it looks like maybe there are a couple, it's hard to tell. But it looks to me like they just do a great job supporting their own product?
In The Raspberry Pi 5 Is No Match for a Tini-Mini-Micro PC
RPi OS is also using a modified kernel and packages that include the v4l2 codec and FFmpeg (rpi-ffmpeg, which I ever tested). https://github.com/raspberrypi/linux/commit/46f21cab3e888823... https://github.com/jc-kynesim/rpi-ffmpeg These staging drivers do not exist in the Linux mainline. It means that you will not get hardware acceleration support when compiling and installing the kernel from `torvalds/linux` instead of `raspberrypi/linux`. As for the RK3588 SBCs, you are free to choose to use Linux 5.10 LTS (legacy) or 6.1 LTS kernel, both of which are officially supported by Rockchip. Or alternatively, use the bleed edge kernel 6.9. Official 3D acceleration will be available in Mesa 24.1 and Linux 6.10, and the developers have also backported it to 6.1 LTS for ease of use. In addition to Armbian, you can also use `ubuntu-rockchip`, whic
Read the rest
h has full hardware-accelerated desktop/server Ubuntu 22.04/24.04 LTS support. https://github.com/Joshua-Riek/ubuntu-rockchip The VPU used by video decoding has nothing to do with 3D/GPU. With `ffmpeg-rockchip` and `libv4l-rkmpp` you get 4k@60 hw decoding support in Chromium and MPV player, and 8k@60 hw decoding support in Kodi. https://github.com/nyanmisaka/ffmpeg-rockchip/wiki/Rendering Jellyfin also provides complete transcoding pipeline support on the RK3588 based SBCs. https://jellyfin.org/docs/general/administration/hardware-ac...
In Beating Jeff's 3.14 Ghz Raspberry Pi 5

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.