The firmware will be branched to avoid de-stabilising its functionality as it continues to support future hardware. This means that a driver compiled against 5.10 may not work when compiled against 5.12 it is therefore important to choose a long-term stable Linux kernel such as 5.10 and only take upstream changes. With new versions of the kernel, the interfaces between different layers changes. The Linux kernel APIs are also important. For this reason we think using the upstream software-accelerated version by default will be better, although we will still keep the hardware-accelerated v92 browser. At the same time, it is important that Chromium is supplied with the most recent version available in Debian, since it has many security patches applied to it. Hardware acceleration of Chromium takes a significant amount of support time for every release we have to re-port our hardware interfaces. Raspberry Pi firmware branched and only taking security and hardware support patches for existing products.Linux kernel branched at 5.10.y and only taking security patches from the Linux kernel.Hardware-accelerated Chromium removed and replaced with the upstream software browser.The previous release of the Raspberry Pi OS based on Buster.Raspberry Pi OS (Legacy)įor this reason, we’ve decided to create a legacy version of the Raspberry Pi OS based on the Debian Buster release (or, to be more specific, the Debian oldstable release). Some of you have asked for an option to roll back certain parts of the OS to restore some functionality that you have been relying on. Others are industrial users, who’ve developed software to use particular library versions or who value a stable unchanging operating system. For example, some of you are educational users who would like to follow instructions and tutorials online. Of course, we understand this isn’t always the right decision for particular users. Some of those come from the upstream and some from our own desire to move to open-source interfaces. Old software and interfaces become unsupported, and the way to do specific things changes. With the new branches come new versions of libraries and new interfaces. This can cause significant problems when we move to a new upstream branch (for example when we moved from Jessie to Stretch or from Stretch to Buster, or the recent move from Buster to Bullseye). Over the past nine years, Raspberry Pi has only ever supported a single release of the Raspberry Pi OS (formerly known as Raspbian).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |