Hi,
I am trying to modify a kernel for Samsung Galaxy 3. I have successfully compiled stock kernel from Samsung Sources.
I am new to kernel development and want to add new features to it like overclocking etc.
Can any one please suggest me links or give info regarding how to go about it.
For example, how to modify the frequencies supported by kernel or bus speed in the source code?
Thanks,
Abhijeet
Check github for modifications to the base. I don't know about Samsung kernels, but a quick search of github shows plenty, like this:
https://github.com/kangsterizer/android_kernel_samsung
click on the comments to see only files affected by OC/UV mods like this from the above example:
https://github.com/kangsterizer/and...mmit/1817cd02de8165a4f96746d4dddec3ef4347cb2d
See if you can move those changes into your own kernel.
Related
Hi,
Could you generalize a download from OmniRom without kernel ?
A lot of OmniRom users a poweruser and used another kernel
bbk said:
Hi,
Could you generalize a download from OmniRom without kernel ?
A lot of OmniRom users a poweruser and used another kernel
Click to expand...
Click to collapse
No. The included kernel is the only supported configuration, and it will always be this way.
Why? Anything else results in a testing nightmare. It's bad enough when we change out blobs that require a matching kernel change and a maintainer's thread gets flooded with "it's not working with X kernel any more".
Anyone can submit changes to Omni's kernels for review in gerrit, so that leads to the question:
1) Why is the maintainer of an alternate kernel not upstreaming to gerrit? What are they hiding?
2) If a change was submitted to gerrit, why was it rejected? In many cases, some of the "features" of alternate kernels are highly dangerous (such as disabling per-file fsync and allowing devices to pull more than 500 mA from a standard USB host port)
I have omni sources cloned and setup to build the kernel for my Xperia V.
The kernel sources are cloned from the dev of the rom I am using NeoWave 1.2.2 for xperia V
I can build a fully working kernel fine, but when adding new cpu governors, they just don't show up...
everything is included in all the relevant files, Kconfig, Makefile,cpufreq.h, cpufreq_xxx, and ....defconfig..
strange thing is if I run a standard make ARCH=arm CROSS_COMPILE=....../arm-eabi- on the same source, they show up and work fine, the only problem being that my build doesn't use the vendor/blobs for my device..
Does anyone know something simple I'm missing, or alternatively a way I can add the vendor blobs directly to my source and just do a standard make?
I'm fairly new to all this...
To answer my own question, it seems that the governors also need to be specified in the cm_xxxx_defconfig file.. That confused me as i have added a module to <device>_defconfig file and it built fine!!
Does this sound feasible for me to get a kernel going for 901F
Compile a stock samsung kernel and test it works on device. (will test with my S2, if I can find samsung sources.)
If cannot find samsung sources compile someone else's sources and test.
Once I confirm I can compile a kernel properly then grab 900F sources, and compare to a custom kernel source to see whats changed.
Try to apply same changes to 901F
done?
I am trying to build a custom kernel for my redmi 2 running on Nexus Experience. I found there kernel source at their github page in nx_kernel_xiaomi_msm8916 . It's the only kernel referring to XIAOMI so I think it is the right one.
I am really new to kernel building. I read some tutorials on the web and tried building one for the stock miui rom but it didn't work out.
So before I start re-building the kernel for Nexus Experience I had some questions. I wanted to add the support for external wifi adapters based on RTL8188CUS. I found the option to enable it. My question is that , By just enabling that feature will my phone just start supporting the adapter out of the box or do I have to add some Modules to it.
And the last question, After I compile the kernel I get this zImage file. I put this file in the anyKernel.zip but I found that I also have to add the wlan.ko file and I couldn't find it....
I really need some help here.
Hi all,
I like to try tweaking and hacking my phone. I've tried some ROMs on my kugo for some time, but I figured I wanted to make my own personalized build. Right now, I'd like to use the 'Night Light' app from F-Droid, which requires KCAL support. In order to enable KCAL I'd need to edit the stock kernel (I know this can be done, it was the case for Genesis Kernel on Nougat).
Hence I'd want to learn to compile a kernel, but I can't get to the end of Sony's tutorial. I've downloaded the kernel source but I am totally lost with defconfig files. How should I configure the kernel ? There is no obvious choice for a defconfig, and I can't get past point #6 in the tutorial..
Given that I've just discovered kernel compilation today, would someone be kind and take some time to maybe point me to useful doc, give me a clue as to what my next step could be, or teach me how they compile kernels for their device ?
Many thanks for any help,
Cheers
TLDR. How to compile a kernel? I have Sony's source for kugo, but don't understand how to configure the kernel compilation.