From a6a12f0fc6cbf093f230cc54ae162527e6c4cb74 Mon Sep 17 00:00:00 2001 From: "Joshua M. Boniface" Date: Sat, 26 Oct 2024 11:15:51 -0400 Subject: [PATCH] Update wording to restore ARM32 deprecation notice --- blog/2024/10-26-jellyfin-release-10.10.0/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/2024/10-26-jellyfin-release-10.10.0/index.mdx b/blog/2024/10-26-jellyfin-release-10.10.0/index.mdx index f87c43f73..324662d11 100644 --- a/blog/2024/10-26-jellyfin-release-10.10.0/index.mdx +++ b/blog/2024/10-26-jellyfin-release-10.10.0/index.mdx @@ -22,7 +22,7 @@ Happy watching! * Most clients should continue to work as-is without any issues or any forced upgrades, though this may change in the future. The sole exception is Jellyfin4Kodi, which currently has issues due to point 5 below, though a fix is hopefully forthcoming shortly. -* We have deprecated Raspberry Pi V4L2 hardware transcoding support, and are looking to deprecate any Raspberry Pi-specific functionality in general for releases past 10.10.0. Raspberry Pi has always been a tricky platform for us, as it's popular but extremely poor in performance, and this has caused a lot of people a lot of headaches. With the RPi5 entirely removing a hardware acceleration engine and the aging of the RPi4, we are taking this action now to ensure it's widely known. If you are running Jellyfin on old RPi hardware, now is the time to start [looking at an upgrade](https://jellyfin.org/docs/general/administration/hardware-selection). See [PR #1148](https://github.com/jellyfin/jellyfin.org/pull/1148). +* We have deprecated Raspberry Pi V4L2 hardware transcoding support, and are looking to deprecate 32-bit ARM support (i.e. `armv7` or `armhf`) in general for releases past 10.10.0. Older, slow ARM systems have always been tricky platforms for us: they're popular but extremely poor in performance, and this has caused a lot of people a lot of headaches. With the RPi5 entirely removing a hardware acceleration engine, and most ARM single-board computers now supporting ARM64, we are taking this action now to ensure it's widely known. If you are running Jellyfin on old ARM hardware, now is the time to start [looking at an upgrade](https://jellyfin.org/docs/general/administration/hardware-selection). See [PR #1148](https://github.com/jellyfin/jellyfin.org/pull/1148). * We now use the system temporary storage engine (e.g. `/tmp` on Linux) for storing short-lived transient temporary files, to allow us to leverage temporary ramdisks and the like and avoid cluttering potentially slow storage. This may cause issues if you specifically depended on the previous behaviour. Note that this does not include transcoding temporary files. See [PR #12226](https://github.com/jellyfin/jellyfin/pull/12226).