N9 Kernel update project

Revision as of 14:18, 1 October 2012

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.

Contact info

• IRC: #mer and #nemomobile @irc.freenode.net
• Mailing list: mer-general@lists.merproject.org

Developement

Development git:

• NOTE: Kernel tree moved from bitbucket to github starting 1st of October 2012!
• WWW github project: https://github.com/nemomobile/kernel-adaptation-n950-n9
• Command line shortcut to clone the repo:

git clone git@github.com:nemomobile/kernel-adaptation-n950-n9.git

• master branch is the latest development branch
• The git tree is public, if you want to contribute patches, read process below:
• Patch process:
  • 1. Send patches first to relevant upstream subsystem list (like linux-omap, linux-usb, etc.)
    • [Subscribe to relevant linux subsystem mailing list here]
  • 2. Once patches seem to be ok for upstream create a pull request in github like following:
    • NOTE: Pull request section below is under construction, instructions incomplete!
    • 2.1 fork the a personal kernel repo in github
    • 2.2 push your changes to your PERSONAL kernel github tree
    • 2.3 send a pull request from your personal repo to nemo-mobile/kernel-adaptation-n950-n9 tree
  • 3. If the patch seems ok for N9 kernel, we'll take it in, if not, you will receive comments what to fix.
  • Exception: Mer/Nemo specific patches (like config changes) can be sent as pull request directly.

Build instructions from git

• • Use Mer SDK and SB2 to build.
  • Building (inside Mer-SDK chroot):

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")

• Pre-requisite: have MOSLO set up on your N9 like this
• We use helper scripts that prepare the modules etc

./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...)

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:

• https://build.pub.meego.com/package/show?package=kernel-adaptation-n950&project=home%3Akjokinie%3Abranches%3AMer%3AMDS%3ACore%3Aarmv7hl

updating pack with git-pkg

• setup git-pkg by cloning it out and copy gp_make_src to PATH
• then do following to update patch set for the OBS pack

osc co <kernel pack>

• do changes in your local mer-n9-linux git mer-latest branch
• if you change base kernel tag version, edit _src to point to right initial commit
• then

#symlink .git from your git tree
ln -s /path-to/mer-n9-linux/.git .git
#run git-pkg script to generate tar and latest patches
gp_make_src

• then copy the "Patches:" lines to your .yaml

specify *.yaml
osc addremove
osc ci -m "latest changes from git..."

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