Re: BFS for the power kernel
 

I think we're veering wildly off-topic here; I only shared my settings in an attempt to help out. This isn't really the place for I/O benchmarks (though I do find them interesting) - BFS can only affect read/write speeds if a task is deactivated when it shouldn't be, causing I/O to remain unflushed, and the -ck patchset deals with swap primarily (though another of his patches drops dirty ratios to 1 - this wouldn't work in our kernel anyway as the code specifically sets a minimum of 5, so I left it out).

Re: BFS for the power kernel
 

There was a fairly major bug in my backport of the mm-make_swappiness_really_mean_it patch, which I've now fixed by backporting a few lines of code from 2.6.32 to check whether priority is greater than 0 _or_ there is no swap space, as intended. I also took out the final vm_swap_full() check and tidied up the remnants of a previously-removed one (it had code that was no longer needed) in the drop_swap_cache_aggressively patch.

Also, the deadline and anticipatory I/O schedulers have now been built as modules into the kernel (if you cat /sys/block/mmcblk0/queue/scheduler you will still see only noop [cfq], but deadline or anticipatory can be echo'd as root and this will automagically insert the relevant module - it'll stay in memory from there on, even if the scheduler is reverted to cfq/noop).

Here're the relevant files (the latest changes are reflected in the git tree, and neither the flasher package nor dummy package have changed, so they're pointless to re-post):

Mandatory:
Modules

Then one of:
Standard package (for use with flasher package)
Multiboot package
u-boot uImage

Add-ons:
FCam Drivers 1.0.7.2
Bleeding-edge wireless modules

Developers:
Headers (for scratchbox/MADDE)

Re: BFS for the power kernel
 

Great! I think I'm going back to kernel-bfs from kernel-power47. Do we still use the old kernel-power-settings or did you build a new one?

Re: BFS for the power kernel
 

The old one should work fine - I did build a settings package without the dependency to either bfs-flasher or power-flasher, though:

Settings package

I'm also currently trying to get CK's swap prefetch working - rather tricky with just a 2.6.22 and 2.6.32 patch to work from, and nothing inbetween. I only succeeded in making the device crash every time it swaps anything so far ;)

Re: BFS for the power kernel
 

BTW, is the kernel built with EXT4 support?

EDIT: Nevermind. After reflashing, I discovered that kernel-bfs didn't play nice with my pmconfig. Ugh, had to reflash twice today. I'm going to install Backupmenu this time.

Re: BFS for the power kernel
 

You should only have had to reflash the kernel, not the entire FIASCO image? Anyway, yes it does have EXT4 support, and more than that, the fixes I backported from 2.6.30 are included too (they are not yet in kernel-power). What's in your pmconfig? I can't think of anything that BFS would bork at, particularly..

Re: BFS for the power kernel
 

SmartReflex VDD1&2 = 1.
I installed the kernel package, then modules, then flasher. Edited pmconfig, and it bombed. Going to do a little more testing after installing BackupMenu.

Re: BFS for the power kernel
 

I've got SmartReflex on myself (albeit through kernel-config, rather than pmconfig) and have no problems..?

Re: BFS for the power kernel
 

Got mine enabled on pmconfig, and kernel-power set to default without any problems at all.

Re: BFS for the power kernel
 

Well, you know SR's a touchy-feely part of the device.
Odd that it only happens on kernel-bfs6 and not on power47. I've got multiboot and backupmenu-multiboot, going to test to confirm tomorrow.

EDIT: What the bloody hell, it works! With SR VDD1&2 on! I must've screwed up the modules installation part/the kernel flashing part. Works as smooth as kernel-power47, without the schedtool tweaks (to be applied later. I'm sleepy.)
Anyways, I'm keeping multiboot. I NEVER, EVER want to touch Flasher-3.5 again.

BTW, can you rebuild wl1251-bfs' DEB to also depend on the bootimg? It's demanding the regular flashable kernel image.

EDIT2: Anyone else notice that fcam-driver using apps aren't working normally? blessn900 doesn't start, and fCamera keeps showing the "shutter closed" message. Blame catorise.Not catorise.