I have uploaded a new version with disabled boot logo as it seems to have caused the crashes during
shutdown (and sometimes during boot).

alrighty then, I'm about to format my 8 GB microSD car with your nilfs package, but just to point out, I re-installed the latest flash version from nokia, and then reinstalled your kernel, and now my phone won't charge, I got it back to the stock kernal, but just a heads up.

edit: well, format worked, and so did mount on stock(nokia) kernel. gonna do some simple tests, and whats a good tool to test performance thats already ported?

interesting. I have upgraded to the latest firmware, installed my kernel and everything works fine for me, including charging.
For benchmarks there are bonnie++, iozone and postmark in extras-devel.
For bonnie++ results see http://talk.maemo.org/showpost.php?p...2&postcount=76

test results for nilfs2 on sd card vs ext3 on internal emmc using bonnie++

nilfs2 8gb sd ------Sequential Output------ --Sequential Input- --Random-
-Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP
berylium 472M 4815 13 3727 6 14286 16 725.7 13

ext3 eMMC ------Sequential Output------ --Sequential Input- --Random-
-Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP
berylium 472M 9880 16 4550 6 17953 20 90.0 1

edit: your kernel works again, anyone wanna throw a gander at how to re-create this bug??

so nilfs2 on SD is muchhslower than ext3 on eMMC.
What class is the SD? could you please also performing the benchmark with ext3 on SD for comparison?

give me a second process the data, but it looks like performance is around similar with both file systems I just got done reformating the sd card and doing a test on it as you specified, give me a moment to process the data.

I'm using a 8 gb microSD card I had from a previous phone. Other than that, I don't know what class it'd fall under.

edit:
this results kinda mixed

nilfs2 8gb sd ------Sequential Output------ --Sequential Input- --Random-
-Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP
berylium 472M 4815 13 3727 6 14286 16 725.7 13

ext3 8gb sd ------Sequential Output------ --Sequential Input- --Random-
-Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP
berylium 472M 5732 11 3270 4 14349 18 68.9 0

thanks. looks like a class 2 card.

BTW, here's is a quote from ShadowJK from IRC. He uses nilfs2 on his sheevaplug:
So neither its performance nor its suitability for flash are impressive.
this only leaves brtfs or logfs as alternatives, but AFAIK they require a kernel >= 2.6.32.

I ran into titan on IRC and after some discussion about idea he asked me to continue here. everything IMO YMMV etc HAND.

Name

IMO "kernel-community" is better than "kernel-maemo" in indicating that this is indeed not the official maemo kernel and thus will be using that name in the following examples.

Packaging ideas

Use Provides liberally to denote features, this way applications can depend on the features and not specific kernel/module package.

First simple example, joydev.ko:

There could be package "kernel-modules-joydev" that is compiled against otherwise fully stock kernel since (unlike NAT) this module does not need any special symbols in the kernel proper. "kernel-modules-joydev" provides only one file 'joydev.ko' which is placed in the modules directory of the stock kernel. "kernel-modules-joydev" depends on the exact binary version of the stock kernel it was compiled against.

Now there's another package "kernel-community-modules-joydev", same idea as above but compiled against the "kernel-community" "stock" configuration, depends on the exact version of "kernel-community" etc. HOWEVER: it adds "Provides: kernel-modules-joydev" to the control file.

This way application depending on joydev can work with either kernel.

The joydev is example of a single module, but there could be plenty more Provides features like "kernel-modules-nat" and "kernel-modules-qos" both of which require extra features from the kernel itself so they're either provided by the "kernel-community-modules" package or as separate "kernel-community-modules-nat" and "kernel-community-modules-qos" packages.

Again an application should depend on the generic "kernel-modules-nat" feature and thus if there are many kernels providing it any one of them is usable, no need to switch from custom kernel X to custom kernel Y just because some app has stupid depends line.

I take this approach in http://mobilehotspot.garage.maemo.org/ (though for some reason I call the kernel I package hotspot-kernel and not kernel-hotspot)

Modularity

Another thing that should be though about sooner rather than later is the fact that everyone wants their favourite feature to the community kernel, this eventually leads to a huge modules package (the symbols that must be in the kernel itself are kind of hard to avoid). It would be better to have the modules as sane collection packages (like "kernel-community-modules-nat" and "kernel-community-modules-joydev" examples above)

For example the mobilehotspot could just as well use the community kernel if Provides lines are good, also it could do away with shipping it's own kernel altogether if the community kernel could be stripped down to as minimal as possible additions to the stock kernel.

There is an offical Nokia kernel. I think maemo is fine and indicates the name of the community. I'll wait for other people's opinions before taking any action.
Yes, that's a good idea.
I have added the some Provides to the new kernel in extras-devel non-free.
However, there is only a single modules packages, which provides all modules.
It could also symlink the modules, which also work with the stock kernel
to the stock modules directory.
I don't think this makes sense. A few kb more or less per module don't justify selecting tens of separate tiny module packages.

The new kernel also contains your hotspot patches and modules.

Sweet! Thanks Titan. A community kernel is a great idea; building a custom kernel was on my todo list, if only I could find more time. Oh how I miss being in my early 20s.

If I could request/suggest a few modules they would be:

ppp (ppp over ssh for vpn is just so handy)
fuse
bluetooth HID (kbd/mouse)