No I didn't meant to compile and replace the kernel, that wouldn't work,obviously.. I meant, why isn't it possible to use the environment provided by those kernels headers and config to compile the required modules and tools? Or would any other problems arise from doing so?
Modifying source and header files sounds like compiling modules and tools against the wrong kernel version and ssources.
The new compil will have news kallsyms adresses, and modules won't load in memory.
So, Sony kernel or DooMLoRD kernel is the same way for me, except this, i only one kernel to maintain for now. It's a easy way.
The only way to have a loading module in a kernel, is the kernel is compil with option witch grant external module.
It's the same issu that stock kernel won't grant, and won't kexec, because stock kernel don't have any option to be open to community (on locked bootloader of course)
Sony gives sources for unlocked only...
"kexec_load.ko" is loaded in memory now. Now i try to converse with.
Edit : "procfs_rw.ko" work
I have a "/proc/atags" now