Skip to content

Request for Unified Build Scripts for OnePlus 11 Kernel (ABI Breakage & Full Module Compilation) #17

@nullptr-t-oss

Description

@nullptr-t-oss

Dear OnePlusOSS Team,

I am writing to you regarding the kernel source code for the OnePlus 11. I am an active developer and maintainer of a custom kernel project for this device.

Link : EmberHeart Kernel

I am currently working on enabling containerization support (LXC/Docker) on the OnePlus 11, which requires enabling specific kernel configurations such as CONFIG_IPC_NS, CONFIG_PID_NS, and CONFIG_USER_NS. As you are aware, enabling these configurations changes the kernel memory layout (specifically task_struct), creating an ABI mismatch with the pre-compiled vendor modules provided in the stock firmware.

To resolve this, I need to recompile all vendor modules against my modified GKI kernel to ensure symbol compatibility. However, the current build scripts and Makefiles provided in the public source release appear to be incomplete or reliant on internal build environments. They do not successfully compile the full suite of out-of-tree modules (such as WLAN, Audio, and Data/Techpack drivers) necessary to boot the device.

I kindly request a unified build script—or detailed instructions—that does not rely on internal Oplus infrastructure, capable of performing the following end-to-end workflow:

  • Compile the Common Kernel (GKI): Build the kernel image and base modules from the common directory using a custom config.

  • Compile GKI Modules: Generate the necessary artifacts to create an updated system_dlkm.img.

  • Compile All Vendor Modules: Compile the full set of msm-kernel modules, crucially including all out-of-tree external modules (WLAN/QCA, Audio, Data, etc.), linked strictly against the artifacts (Module.symvers) from step 1.

  • Packaging: Scripts to correctly pack the resulting modules into vendor_boot.img and vendor_dlkm.img.

Currently, attempting this with the public scripts results in missing symbols or incomplete module sets, leaving the device in a bootloop due to the aforementioned ABI breakage.

Providing a script that covers these steps would greatly benefit the development community and ensure full compliance with the customizability intent of the GPL.

Thank you for your time and assistance.

Best regards,
<nullptr-t-oss>

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions