Patched the latest maemo40 power kernel with BFS 350. Also created a garage project for kernel-bfs and uploaded the git repository.

All release files are currently here:
https://garage.maemo.org/frs/?group_id=1886

Which is the files section of the kernel-bfs garage project.

For details on what has changed from BFS 330 till BFS 350 see here:
http://ck.kolivas.org/patches/bfs/2....0-bfs350.patch

Right now this kernel installs over (or instead of) kernel-power. Until this kernel can be installed parallel to kernel-power the installation is going to be a bit manual.

This is not compatible with multiboot! The multiboot package will fail to setup this kernel for multiboot!

The fcam-drivers package on this project page are required if you want to use fcam after installing this kernel. The fcam-drivers provided in the repositories are not compiled against this kernel. Since this kernel is different enough from kernel-power they will fail to load and you will be without a camera.

1. Download the tarball contain all kernel .debs and the FCAM drivers: https://garage.maemo.org/frs/downloa...bfs0_armel.tgz

2. Extract to your device

3. As root cd to the extracted directory.

4. Run the following command twice*:
5. Install the FCAM drivers (if you want fcam camera support) with:

TODO:

1. Rename kernel-power in installed files and built debs to kernel-bfs
2. Embed the fcam drivers in the kernel... Unless I'm given a good reason why not.

* I don't think the .deb dependencies are correct. Installing twice assures the kernel flasher actually flashes the updated kernel.

thanks.

How does this play together with multiboot ? can you release a power40 inplace replacement working identical to the 'normal' multiboot power40 kernel ?

rootfs space is at a premium, i don't need another kernel there ...

thanks

Source / git deets please.

Isn't working with multiboot here. Multiboot can't find the kernel image. I uninstalled it, and now multiboot is in an infinite loop.

Has anyone benchmarked with latencytop or sth?

I can. However this will require an update to the multiboot-extras package. Currently this package only make kernels "multiboot ready" that have a name of the form:

However this kernel is installed as:
Meaning that the multiboot-kernel-power package will not properly set up this kernel for multiboot. Doh! An easy fix, but one that will require a re-release of multiboot-kernel-power.

Even better would be to rename this kernel to kernel-bfs instead of kernel-power and create a multiboot-kernel-bfs package created for it.

I think I will go straight to that route.

The source code can be located via the SCM page of the project page:
https://garage.maemo.org/scm/?group_id=1886

The patches included over kernel-power are:
bfs.patch
bfs-316-to-318.patch
bfs-318-to-330.patch
sched_reset_on_fork.diff
bfs-330-to-350.patch
voltage_scaling_1.diff
voltage_scaling_0.diff

Yeah do that. You are not kernel-power and should either leave them alone or state that your packages (kernel-bfs) are not compatible with them. Same for multiboot.

Btw fcam-drivers can be installed with apt-get.

This code is actually a branch of kernel-power plus additional patches. Which is why the installed packages all mention "kernel-power" Not very useful for something that isn't a true replacement. Or even an "upgrade"

The fcam-drivers installed via apt-get are not compatible with this kernel. They are compiled for kernel-power - not this kernel - and will fail to load. Which is why the fcam-driver package on the project's file page is required.

Either way something is wrong with the packaging.

You're not helpful.