this post was submitted on 24 Oct 2024
252 points (99.6% liked)

Steam Hardware

20065 readers
263 users here now

A place to discuss and support all Steam Hardware, including Steam Deck, Steam Machine, Steam Frame, and SteamOS in general.

As Lemmy doesn't have flairs yet, you can use these prefixes to indicate what type of post you have made, eg:
[Flair] My post title

The following is a list of suggested flairs:
[Deck] - Steam Deck related.
[Machine] - Steam Machine related.
[Frame] - Steam Frame related.
[Discussion] - General discussion.
[Help] - A request for help or support.
[News] - News about the deck.
[PSA] - Sharing important information.
[Game] - News / info about a game on the deck.
[Update] - An update to a previous post.
[Meta] - Discussion about this community.

If your post is only relevant to one hardware device (Deck/Machine/Frame/etc) please specify which one as part of the title or by using a device flair.

These are not enforced, but they are encouraged.

Rules:

Link to our Matrix Space

founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] woelkchen@lemmy.world 2 points 1 year ago

Always porting not-yet-upstreamed patches to new release kernels is additional work to the upstreaming work towards the latest development tree. The Valve engineers interviewed around the very first Steam Deck announcement said their goal with moving from Debian to Arch was to minimize the patchset maintenance burden. Their approach surely has that goal in mind. There are only two variants of Steam Deck with minor differences between them. If backporting patches from newer kernels is less work than forward porting their patches, they just stay with that version for a while. Updates to drivers for hardware they don't use and filesystems they don't use aren't relevant to them anyway.