tg-me.com/RequiemKernelX2/581
Last Update:
On 5.10, building standalone kernels is a big mess in and of itself.
To build the qcom kernels on 5.10 and above there's kernel_platform, a sort of split build system where the kernel is built first in a kind of prebuilt kernel format, and then you build the ROM separately.
Well, what about the standalone kernels?
There's 3 ways to mostly do this as far as I know.
First method is a slight hacky way devised by arter97, the lazy initcall
https://github.com/arter97/hdk-kernel/commit/1ad367f0f821a70e5a766e267515aa6be022a44e
The second way is just bypassing those modules by not inlining them in the kernel, as such they are initialised as is from vendor_dlkm.
However here comes the biggest caveat: kmi
https://source.android.com/docs/core/architecture/kernel/stable-kmi
For the kernel to be able to load precompiled kernel modules (ko), the kernel must be compiled with Google clang 12.0.5. This means we cannot compile the kernel with the latest clang.(this is mostly just applicable for stock kernel and if ur gonna target stock rom)
The third way is by unpacking the vendor_dlkm, replacing the module inside, repacking it then shipping the img alongside the kernel Image in ak3.
BY Requiem-Kernel
Warning: Undefined variable $i in /var/www/tg-me/post.php on line 283
Share with your friend now:
tg-me.com/RequiemKernelX2/581