docs: fix wrong infomation (#282)

* docs: fix wrong infomation

* docs: fix wrong infomation
This commit is contained in:
米凛MiRin
2025-07-17 14:32:20 +08:00
committed by GitHub
parent 86456a4d95
commit dd2b2e995a
2 changed files with 2 additions and 2 deletions

View File

@@ -4,7 +4,7 @@ SukiSU can be integrated into both _GKI_ and _non-GKI_ kernels and has been back
<!-- It should be 3.4, but backslashxx's syscall manual hook cannot use in SukiSU--> <!-- It should be 3.4, but backslashxx's syscall manual hook cannot use in SukiSU-->
This customization could result in as much as 50% of kernel code being out-of-tree code and not from upstream Linux kernels or ACKs. Due to this, the custom nature of _non-GKI_ kernels resulted in significant kernel fragmentation, and we lacked a universal method for building them. Therefore, we cannot provide boot images of _non-GKI_ kernels. Some OEMs' customization could result in as much as 50% of kernel code being out-of-tree code and not from upstream Linux kernels or ACKs. Due to this, the custom nature of _non-GKI_ kernels resulted in significant kernel fragmentation, and we lacked a universal method for building them. Therefore, we cannot provide boot images of _non-GKI_ kernels.
Prerequisites: open source bootable kernel. Prerequisites: open source bootable kernel.

View File

@@ -4,7 +4,7 @@ SukiSU 可以集成到 GKI 和 non-GKI 内核中,并且已反向移植到 4.14
<!-- 应该是 3.4 版本,但 backslashxx 的 syscall manual hook 无法在 SukiSU 中使用--> <!-- 应该是 3.4 版本,但 backslashxx 的 syscall manual hook 无法在 SukiSU 中使用-->
定制可能导致多达 50% 的内核代码超出内核树代码,而非来自上游 Linux 内核或 ACK。因此non-GKI 内核的定制特性导致了严重的内核碎片化,而且我们缺乏构建它们的通用方法。因此,我们无法提供 non-GKI 内核的启动映像。 有些 OEM 定制可能导致多达 50% 的内核代码超出内核树代码,而非来自上游 Linux 内核或 ACK。因此non-GKI 内核的定制特性导致了严重的内核碎片化,而且我们缺乏构建它们的通用方法。因此,我们无法提供 non-GKI 内核的启动映像。
前提条件:开源的、可启动的内核。 前提条件:开源的、可启动的内核。