Clash Meta for Android Update
2025-08-27
#Clash #ClashMeta #Android

Release tag:
v2.11.16

Assets:
cmfa-2.11.16-meta-arm64-v8a-release.apk (24.3 MB)
cmfa-2.11.16-meta-armeabi-v7a-release.apk (24.6 MB)
cmfa-2.11.16-meta-universal-release.apk (59.2 MB)
cmfa-2.11.16-meta-x86-release.apk (25.5 MB)
cmfa-2.11.16-meta-x86_64-release.apk (25.2 MB)
output-metadata.json (2.5 KB)

Xiaomi.eu Multilang HyperOS ROM stable Update
2025-08-28
#Marble #XiaomiEU #HyperOS #Stable

Build date:
Wed, 27 Aug 2025 15:14:43 UT

MD5:
3b404efbe6d85fcb3125a1b01e958ba7

Download:
xiaomi.eu_MARBLE_OS2.0.205.0.VMRCNXM_15.zip

Size:
5.7 GB

Raspberry Pi4 bootloader EEPROM Stable Update
2025-08-28
#RaspberryPi #eeprom

Build date:
20250827

Changelog:
https://github.com/raspberrypi/rpi-eeprom/blob/master/firmware-2711/release-notes.md

Download:
pieeprom-2025-08-27.bin

Size:
512.0 KB

Linux Patches To Unconditionally Enable Architecture-Optimized BLAKE2s Support
28 August 2025 - Arch-Optimized BLAKE2s

While Linus Torvalds doesn't too often like new kernel options being enabled by default, one area where it has proven beneficial and otherwise an oversight by those configuring their own kernel builds is the architecture-optimized crypto algorithm implementations. Some will enable support for different kernel crypto algorithms only to forget or be unaware that there are CPU architecture specific implementations that can also typically be enabled for much better performance over the common code. Google engineer Eric Biggers has been cleaning this up and BLAKE2s is the latest receiving treatment.

Comments

#Phoronix #LinuxKernel

Linux Kernel stable v5.10.241 update
#Linux #Kernel

Commits

SHA1: 10FC7B75ECAAD80B8E86BEDBE54EB4C1ADF70C29

Glow Kernel v4.1 for marble/marblein
By Asshole

Download
Source code

Changelog:
- Same as Melt-marble-v4.1

Q1. Why does Glow Kernel only support the original KernelSU and MKSU?
A1: I can't satisfy everyone, I don't even use KernelSU at all, I still use Magisk. But since Glow Kernel is a standard GKI, you can still install any other unofficial version of KernelSU you like through LKM. If you are asked to select the KMI version during installation, select android12-5.10.

Q2. Why did you abandon support for MIUI14 in Glow Kernel v4.0 and later versions?
A2: The latest Glow Kernel has replaced almost all kernel modules with those compiled from source code, but you know we still need to use some precompiled kernel modules from Xiaomi. In HyperOS, making open source kernel modules compatible with Xiaomi's precompiled kernel modules is enough to give me a headache, and if it is the older MIUI14, it will only give me more headaches. There are very few users who are still using MIUI14. Even if I have a marble dedicated to testing, I don't want to risk losing the baseband by downgrading the ROM and firmware to test the compatibility of Glow Kernel on MIUI14.

Q3. Why are the dtb and dtbo included in Glow Kernel not open source?
A3: The dtb and dtbo included in Glow Kernel are extracted from the latest official HyperOS rom and slightly modified. If you want to know what modifications I made, please read: https://github.com/Pzqqt/AnyKernel3/blob/Marble-Melt/modify_dtb_and_dtboimg.sh
As for why it is not open source, there are several reasons:
1. Qualcomm itself has not open sourced waipio's devicetree at clo, and from the "leaked" waipio devicetree source code of some manufacturers, these devicetree source codes are not subject to the GPL 2.0 of Linux Kernel (there is no relevant statement in the file header). Therefore, first of all, Glow Kernel's behavior of not open dtb and dtbo does not violate GPL 2.0; secondly, rather than condemning me, we should condemn Qualcomm, right?
2. Decompiling and recompiling dtb and dtbo files is as simple as 1+1=2, and the decompiled source code files are completely readable and editable. If you have doubts about the security of Glow Kernel's dtb and dtbo, you are welcome to review and give me feedback.

Q4. Why does Glow Kernel still include some of Xiaomi's precompiled kernel modules?
A4: I had to do this to be compatible with HyperOS rom.

Q5. Glow Kernel includes Xiaomi precompiled kernel modules that are not open source. This behavior violates the GPL and I want to condemn you.
A5: Please go to Asshole, not me.

Google Clang Prebuilt Update
#clang

Commit

Download tar.gz:
clang 21.0.0 (based on r574158) from build 13996053

给电脑更新BIOS结果翻车了，查资料鼓捣了几个小时仍然没解决问题。🤔

Clash Verge Rev Update
2025-08-31
#Clash #ClashMeta

Release tag:
Clash Verge Rev v2.4.1

Assets:
There are too many, see here

Linux 6.17-rc4 Released With Bcachefs Now "Externally Maintained", Some New Hardware
31 August 2025 - Linux 6.17-rc4

Linus Torvalds just released Linux 6.17-rc4 as the newest weekly test release of Linux 6.17 in working toward the stable release in late September.

Comments

#Phoronix #LinuxKernel

Linux's Current & Future Rust Graphics Drivers Getting Their Own Development Tree
2 September 2025 - drm/rust/kernel.git

To help in accelerating the development of kernel graphics drivers and any other NPU/accelerator drivers written in the Rust programming language, the Direct Rendering Manager (DRM) subsystem is creating its own DRM-Rust development tree for drivers and associated Rust infrastructure.

Comments

#Phoronix #LinuxKernel

Linux Scheduler Adapted For A Latency Win & Avoiding An RT Deadlock
3 September 2025 - Defer Throttle

A patch series for the Linux kernel scheduler code is queued up for expected introduction in Linux 6.18 to defer throttle when tasks exit to user-space. These changes to switch the scheduler to a task-based throttle model and task-based throttle time accounting can provide a latency win and also address a possible deadlock situation for real-time "RT" kernels.

Comments

#Phoronix #LinuxKernel

Final version, fixes performance issue caused by code obfuscation

Linux Kernel stable v5.10.242 update
#Linux #Kernel

Commits

后续：
大战售后失败，准备拿回来寄给维修厮修，弄不好还能上电视。