[LG Optimus 2x] Stefan Gündhör:
Why are you obviously bashing me for using the word "revolution" when porting a CM7 kernel to stock compatibility, friend?

Did I bash you in this thread? No.

Has this port been made before? No. By a Recognized Dev like you? No.

So what exactly is your point honestly?

Sorry mate, let's face the truth, every single part of changelog of HP kernel is nothing than standard merges from other repos, v10 sources or just playing around with values. Let's take a look at your changelogs from beginning up to now:

OC code? merged

UV code? merged

Voodoo support? merged

Ext4 support? uncomment a line in defconfig

Smoother UI? playing with defconfig and compilation flags

Lower latency? Changing a value from 2000 to 1600 and another value too

Modified battery driver? Changing 3 values from 4150 to 4190

Strong haptic feedback? Using v10E sources

String incoming call vibration? Using v10E sources

JRCU? merged

self compiled toolchain? done in 5 minutes via crossToolNG

disabled f_sync? merged

fixed pseudocolor tables? merged

readahead auto limit? merged

24Bits/48KHz HW accelarated autdio playback? Change 4 integer values

ARM Hard Float VFP support? merged and only single words to change from "soft" to "hard" in most cases

NVMAP enabled to kill processes envoked by GPU? Enable a line in defconfig and if needed merge before

...

Hard work? No! People need to know what we

BOTH

do here is basically nothing more than work of maybe 2 days.

And from release to release we are playing around with the right values and selection of features, this is what takes the most time, but this is

NOT

real developing.

This takes much time but is no hard work. It is NOT MORE than that.

People need to know that what we do

BOTH

here is

NO REAL PROGRAMMING

at all. It's playing around and experimenting.

Real programming is about writing hundreds and thousands lines of code yourself.

I can't stand you always pretending how hard work custom kernel making is. (At least not for both of us though there are of course people out there really DEVELOPING kernels, but spica and I obviously don't belong to them)

Lets just be honest without offending at all: The only thing in your kernel really made by you is the OTF (which in fact is based on another guy's work) --- so is THIS a revolution?

NO, linux kernel has always has many OnTheFly changeable files, you are just enhancing the already existing OTF

Let's take a look at the complete OTF source:

file 1:

#include <linux/guestekrnl.h>
#define PROC_DIR "gueste"

// OTF
unsigned int STRONG_HAPTIC_VIBRATION = 0;
static struct proc_dir_entry *gueste_dir = NULL;

void gueste_init(void) {gueste_dir = proc_mkdir(PROC_DIR, NULL);}

struct proc_dir_entry* gueste_add(const char* name) {
if ( gueste_dir == NULL ) gueste_init();
return create_proc_entry(name, 0777, gueste_dir);
}

void gueste_remove(const char* name) {remove_proc_entry(name, gueste_dir);}

file 2:

#ifndef _GUESTE_H
#define _GUESTE_H
#include <linux/kernel.h>
#include <linux/module.h>
#include <linux/init.h>
#include <linux/proc_fs.h>
#include <asm/uaccess.h>
// OTF
extern unsigned int STRONG_HAPTIC_VIBRATION;
struct proc_dir_entry* gueste_add(const char* name);
void gueste_remove(const char* name);

file 3:

#include	<linux/guestekrnl.h>
#define VIBE_PROCFS_NAME "strong_haptic_vibe"
#define VIBE_PROCFS_SIZE 2
static struct proc_dir_entry *VIBE_Proc_File;

static int vibe_procfile_read(char *buffer, char **buffer_location, off_t offset, int buffer_length, int *eof, void *data) {
int ret;
ret = sprintf(buffer, "%u\n", STRONG_HAPTIC_VIBRATION);
return ret;
}

static int vibe_procfile_write(struct file *file, const char *buffer, unsigned long count, void *data) {

unsigned int tmpval = 0;
unsigned int ret;
ret = sscanf(buffer, "%u", &tmpval);
if (ret != 1)
return -EINVAL;

if ( tmpval < 0 || tmpval > 1 )
return -EINVAL;

STRONG_HAPTIC_VIBRATION = tmpval;
return count;
}

static int __init init_vibe_procsfs(void)
{
VIBE_Proc_File = gueste_add(VIBE_PROCFS_NAME);

if (VIBE_Proc_File == NULL) {
gueste_remove(VIBE_PROCFS_NAME);
return -ENOMEM;
} else {
VIBE_Proc_File->read_proc = vibe_procfile_read;
VIBE_Proc_File->write_proc = vibe_procfile_write;
VIBE_Proc_File->mode = S_IFREG | S_IRUGO;
VIBE_Proc_File->uid = 0;
VIBE_Proc_File->gid = 0;
VIBE_Proc_File->size = 37;
}
return 0;
}
module_init(init_vibe_procsfs);

static void __exit cleanup_vibe_procsfs(void) {
gueste_remove(VIBE_PROCFS_NAME);
}
module_exit(cleanup_vibe_procsfs);

That's it! Whole glorious spica OTF in one posting. Every additional OTF functionality follows the scheme in file 3. There is nothing more to work on OTF or improve like you tell the people.

About 50 lines of code are all you have ever developed NEW for your kernel. (plus Maybe 10-15 lines if that cpu mem leak and second core sync thing really is from you) Everything else is either merged or playing around with values or enabling/disabling features in defconfig.

I have enough of this, you pretending all the time to do such a hard word and so many inventions on your kernel. There is NOT A SINGLE invention in your kernel (unless you call the two bugfixes mentioned above inventions). OnTheFly changeable values have been well known and used in linux before.

I have decided to finally leave XDA, so you can continue working undisturbed and make people believe what great work you do. Yeah this time definitely ;)

I will work on a last stable release of guestekrnL over this night and I bet it will kick your SR4's nuts.

And before you ask what I invented for my kernel... well I'm not moaning all the time about the haaaard work and not always telling how "creative and extraordinary" (your words about your OTF) my work is, so I don't really need to justify here. But just in case I'd like to mention the discovered and first fixed by me bug of second core scaling and the intelligent auto second core limit stuff and maybe the auto backlight intensity stuff no other kernel has yet and of course the hybrid stuff v20Q/v10E, CM7/v20Q/v10E, Linux 3.0.30/v20Q/v10E

Not too much but I'm not bragging all the time too.

Also, remember I started kernel DEVing much later than you, just imagine I have had the time you had.

@Mods: before you take actions against my user account due to this posting, please give me 24 hours to upload my final release of guestekrnL (for XDA) and to update my thread. After this you may delete or lock my account, I don't care.

Ah and maybe you can leave this post for now. This is no bashing, I have justified all of my arguments.

I know people will hate

me

for this because once more it's looking like I'm the bad guy. But it's time to bring spica back to earth, and unfortunately only people working on kernels themselves can see that his work is nothing special at all.

Game over.

My final rock-solid and "best of all"- release of guestekrnL is coming tomorrow, uploaded at the usual places if I should be already banned by then.