Dear kernel and ROM developers.
According to GPL v2 license, under which kernels are released, kernels must be released with source code provided.
To be fully compliant, the thread must contain.
@ kernel devs
More information can be found in the news written by pulser_g2.
Thank you for your attention.
Tom
XDA Senior Moderator
According to GPL v2 license, under which kernels are released, kernels must be released with source code provided.
To be fully compliant, the thread must contain.
@ kernel devs
- Successfully build and produce a valid output file, which is the same format as provided in the binary
- Contain all source code, interface definition files, scripts used to control compilation and installation of the executable (it is not required to include the actual compiler/toolchain, but sufficient information should be made available to obtain the SAME configuration, including compiler flags, as used to build the binary version as released
@ ROM devsKick-ass kernel
- Built with android-toolchain 4.8 4.8-2013.05 (linking isn't a bad idea)
- Branch used to compile (can be a direct link to git)
- Name of the defconfig used in build
- A short instruction about how to build it (not necessary, but useful)
- if ROM uses custom boot.img, the source must be provided. If it uses kernel by someone else, the kernel thread must be linked in the OP
- if the ROM contains stock kernel, source must be linked (official site can be used)
- Using a non GPL compliant kernel makes your ROM non compliant and subject to removal
More information can be found in the news written by pulser_g2.
Thank you for your attention.
Tom
XDA Senior Moderator