The Mer Wiki now uses your Mer user account and password (create account on https://bugs.merproject.org/)
N9 Kernel update project
From Mer Wiki
Contents |
Summary
The N9 kernel currently used with various Mer images is based on old 2.6.32 maemo kernel. This page collects needed info for any developers who might want to help in updating that kernel to latest linux-stable version.
Developement
Development git: https://bitbucket.org/kjokinie/mer-n9-kernel
git clone https://bitbucket.org/kjokinie/mer-n9-kernel.git git checkout -b mer-latest origin/mer-latest
- mer-latest branch is the latest development branch
- The git tree is public, if you want to contribute patches, contact kjokinie in #mer IRC
- If you make patches it is recommended to send those also to relevant upstream kernel list (most likely linux-omap, as N9 uses omap SoC), this way we don't grow the upstream delta too big.
sb2 make n9_mer_defconfig sb2 make -j4 zImage sb2 make -j4 modules sb2 make modules_install INSTALL_MOD_PATH=./mods
- Deploying to device (kind of "flashing")
- We use helper scripts that prepare the modules etc
- Deploying to device (kind of "flashing")
./prepare_kernel.sh
- Then use copy script (NOTE: do this outside Mer-SDK chroot)
- Plug N9 to USB and let it boot so the filesystem gets mounted
- Then "flash" the kernel (it's just a simple cp actually...)
- Then use copy script (NOTE: do this outside Mer-SDK chroot)
sudo ./copy_kernel.sh /<path-to>/<mounted>/<N9 filesystem>
Packaging
- OBS used: https://build.pub.meego.com
- OBS API: https://api.pub.meego.com
Packaging development project:
TODO: fix OBS pack to use git-pkg and add info how to do it here...
TO DO list for kernel update
- Port needed device drivers from 2.6.32 kernel to latest kernel
- Some hint may come from missing kernel config options found in initial kernel config migration from 2.6.32 to 3.5.3
- Port needed Mer specific patches from old N950 kernel OBS pack
- Yes, all 100+ patches there should be checked