android/SukiSU-Ultra
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

misc grammar and typo fixes (#699)

Browse Source
This commit is contained in:
SirRGB
2023-06-30 17:54:15 +02:00
committed by GitHub
parent e6fea652de
commit b308a368d3
1 changed files with 11 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
website/docs/guide/how-to-integrate-for-non-gki.md
View File

@@ -1,19 +1,19 @@
# How to integrate KernelSU for non GKI kernel?
# How to integrate KernelSU for non GKI kernels?
KernelSU can be integrate to non GKI kernel, and it is backported to 4.14 now, it is also possible to run on kernel below 4.14.
KernelSU can be integrated into non GKI kernels, and was backported to 4.14 and below.
Since the fragmentization of non GKI kernels, we don't have a uniform way to build it, so we can not provide non GKI boot images. But you can build the kernel yourself with KernelSU integrated.
Due to the fragmentization of non GKI kernels, we do not have a uniform way to build it, so we can not provide non GKI boot images. But you can build the kernel yourself with KernelSU integrated.
First, you should be able to build a bootable kernel from kernel source code, if the kernel is not open sourced, then it is difficult to run KernelSU for your device.
First, you should be able to build a bootable kernel from kernel source code. If the kernel is not open source, then it is difficult to run KernelSU for your device.
If you can build a bootable kernel, there are two ways to integrate KernelSU to the kernel source code:
1. Automatically with `kprobe`
2. Manully
2. Manually
## Integrate with kprobe
KernelSU use kprobe to do kernel hooks, if the *kprobe* runs well in your kernel, it is recommended to use this way.
KernelSU uses kprobe to do kernel hooks, if the *kprobe* runs well in your kernel, it is recommended to use this way.
First, add KernelSU to your kernel source tree:
@@ -40,9 +40,9 @@ But if you encounter a boot loop when integrated KernelSU, it is maybe *kprobe i
comment out `ksu_enable_sucompat()` and `ksu_enable_ksud()` in `KernelSU/kernel/ksu.c`, if the device boots normally, then kprobe may be broken.
:::
## Manully modify the kernel source
## Manually modify the kernel source
If kprobe can not work in your kernel (maybe a upstream bug or kernel below 4.8), then you can try this way:
If kprobe does not work in your kernel (may be an upstream or kernel bug below 4.8), then you can try this way:
First, add KernelSU to your kernel source tree:
@@ -157,7 +157,7 @@ index 376543199b5a..82adcef03ecc 100644
return -EINVAL;
```
You should found the four functions in kernel source:
You should find the four functions in kernel source:
1. do_faccessat, usually in `fs/open.c`
2. do_execveat_common, usually in `fs/exec.c`
@@ -221,7 +221,7 @@ index 2ff887661237..e758d7db7663 100644
To enable KernelSU's builtin SafeMode, You should also modify `input_handle_event` in `drivers/input/input.c`:
:::tip
It is strongly recommended to enable this feature, it is very helpful for recusing from bootloop!
It is strongly recommended to enable this feature, it is very helpful to prevent bootloops!
:::
```diff
@@ -248,4 +248,4 @@ index 45306f9ef247..815091ebfca4 100755
add_input_randomness(type, code, value);
```
Finally, build your kernel again, KernelSU should works well.
Finally, build your kernel again, KernelSU should work well.