You might build a kernel that is usable with a hacked version of Harmattan where in addition of the normal aegis-neutering you need to remove quite a lot of stuff from the OS that uses the aegis interfaces in kernel (or you could port back those as dummy interfaces to the 3.x.x kernel... I have not tried that.)
There are precompiled binaries but none of the abovenmentioned stuff of course exists in those so you need to roll your own.
Building the kernel is pretty straighthtforward, on a debian based linux you need to install ARM cross-compilation tools (but no scratchbox et al is needed), for example "apt-get install gcc-arm-linux-gnueabi"
4.) "ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- make modules_install"
5.) copy modules to device, do not forget to "depmod -a <mod_dir>"
6.) flash the beast to your device
1, ARCH=arm make rm696_nemo_defconfig" Can't find default configuration "arch/arm/configs/rm696_nemo_defconfig", missing some procedure?
2, can this kernel loaded by ubiboot?
1, ARCH=arm make rm696_nemo_defconfig" Can't find default configuration "arch/arm/configs/rm696_nemo_defconfig", missing some procedure?
2, can this kernel loaded by ubiboot?
1.) if you take a standard source tree you need to create a matching configuration. Take a look in the Nokia Harmattan PR1.3 kernel tree in directory arch/arm/config for clues.
2.) yes, ubiboot can load any kind of kernel. However, it depends on the kernel itself if it will start up correctly.
It's a shame that this project doesn't have the same momentum as the N900 one. As far as I can tell, this project only aims to provide a 3.5 kernel (which is now nearly 2.5 years old) and there seems to be little effort to upstream these patches. I'd love to do a DebiaN950/DebiaN9 to complement my DebiaN900 project but with such an outdated kernel, the incentive's just not there.
The kernel now works fine on N9, but, as you said, there is not enough motivation in upstreaming it. IIRC, it seems that many bits depend on closed source user space, and so are probably unsuitable for upstreaming (probably will not be accepted upstream)?
Also, probably the first step to upstream more code is to replace most of N9 board file with device tree equivalant.
My second N9 failed also (it powers off after inserting SIM and entering pin) - but both work, just not with 3G. Since 3G is know to be working in 3.5.3 for some time now (https://github.com/filippz/kernel-ad...1c54b344ffc9fd) I'm guessing that these broken devices won't be a problem.
