Difference between revisions of "The Linux kernel"

Revision as of 10:56, 24 July 2010

How to cross compile the linux kernel

Embedded Linux is the use of a Linux operating system in embedded computer systems such as mobile phones, personal digital assistants, media players, set-top boxes, and other consumer electronics devices, networking equipment, machine control, industrial automation, navigation equipment and medical instruments.

Unlike desktop and server versions of Linux, embedded versions of Linux are designed for devices with relatively limited resources, such as cell phones and set-top boxes. Due to concerns such as cost and size, embedded devices usually have much less RAM and secondary storage than desktop computers, and are likely to use flash memory instead of a hard drive. Since embedded devices serve specific rather than general purposes, developers optimize their embedded Linux distributions to target specific hardware configurations and usage situations. These optimizations can include reducing the number of device drivers and software applications, and modifying the Linux kernel to be a real-time operating system.

Overview of How-To

This How-To is meant to be a starting point for people to learn build a kernel image for IGEP v2 devices as quickly and easily as possible.

This How-To works with the Ubuntu 8.04 IGEP v2.0 SDK Virtual Machine but most of the contents are valid also for other GNU/Linux distributions. We do not issue any guarantee that this will work on other distributions.

Requirements

• Ubuntu 8.04 IGEP v2.0 SDK Virtual Machine

IGEP platforms

• IGEP0020 is also know as IGEP v2 platform.
• IGEP0030 is also know as OMAP3 IGEP module.

Supported kernels

First of all setup the build environment sourcing this script

$ source /usr/local/poky/eabi-glibc/arm/environment-setup

or

$ source /usr/local/poky/eabi-glibc/environment-setup-arm-none-linux-gnueabi

if you have updated your SDK environment to latest version (see Ubuntu 8.04 IGEP v2.0 SDK Virtual Machine)

Linux OMAP v2.6.33 series (stable)

Latest stable kernel version is: 2.6.33.5-0 (20100611)

Download the IGEP Linux kernel sources and follow next steps:

$ wget http://downloads.igep.es/sources/linux-omap-2.6.33.tar.gz
$ tar xzf linux-omap-2.6.33.tar.gz
$ cd [kernel version]
$ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- <board-config>
$ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- menuconfig
$ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- uImage modules

where:

• <board-config> is igep0020_defconfig for IGEP v2 platform.
• <board-config> is igep0030_defconfig for OMAP3 IGEP module.

The result will be an uImage file in arch/arm/boot directory. You can install the kernel modules to your target rootfs

$ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- modules_install INSTALL_MOD_PATH=[path to your target rootfs]

CHANGELOG

• 2010-06-11 Release 2.6.33.5-0
  • add support for OMAP3 IGEP module (igep0030)

Linux OMAP v2.6.28 series (stable)

Latest stable kernel version is: 2.6.28.10-3 (20100318)

Download the IGEP v2 Linux kernel sources and follow next steps:

$ wget http://downloads.igep.es/sources/linux-omap-2.6.28.tar.gz
$ tar xzf linux-omap-2.6.28.tar.gz
$ cd [kernel version]
$ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- igep0020_defconfig
$ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- uImage modules

The result will be an uImage file in arch/arm/boot directory. You can install the kernel modules to your target rootfs

$ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- modules_install INSTALL_MOD_PATH=[path to your target rootfs]

Linux Android 2.6 (development)

Clone the GIT repository from git.myigep.com. Based on rowboat project tree.

$ git clone git://git.igep.es/pub/scm/linux-omap-2.6.git
$ cd linux-omap-2.6
$ git checkout origin/linux-android-2.6 -b linux-android-2.6

and build with

$ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- igep0020_android_defconfig
$ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- uImage modules

The result will be an uImage file in arch/arm/boot directory. You can install the kernel modules to your target rootfs

$ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- modules_install INSTALL_MOD_PATH=[path to your target rootfs]

Linux mainline tree (development)

Note: The 'master' branch is where the development work takes place and you should use this if you're after to work with the latest cutting edge developments. It is possible trunk can suffer temporary periods of instability while new features are developed and if this is undesirable we recommend using one of the release branches. Use ONLY for development purposes.

Additional patches can be found at http://patchwork.kernel.org/project/linux-omap/list

This Linux kernel is also considered as a downstream of tmlind's Linux kernel. The main difference between this tree and the linux-omap tree is that the myigep OMAP tree has unpublished patches for IGEP v2 support.

Clone GIT repository from git.myigep.com

$ git clone git://git.igep.es/pub/scm/linux-omap-2.6.git
$ cd linux-omap-2.6

and build with

$ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- igep0020_defconfig
$ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- uImage modules

The result will be an uImage file in arch/arm/boot directory. You can install the kernel modules to your target rootfs

$ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- modules_install INSTALL_MOD_PATH=[path to your target rootfs]

Reference: Kernel features

Reference: QA, diagnosis & tests

OneNAND

This page describes basic testing of OneNAND/NAND Flash devices, controllers, and wear levelling filesystems.

Simple read and write test

How to test:

1. run 'nandtest -l 4194304 -k -p 5 /dev/mtd4'.

Result should be like this:

ECC corrections: 0
ECC failures   : 0
Bad blocks     : 0
BBT blocks     : 0
003c0000: checking...
Finished pass 1 successfully
003c0000: checking...
Finished pass 2 successfully
003c0000: checking...
Finished pass 3 successfully
003c0000: checking...
Finished pass 4 successfully
003c0000: checking...
Finished pass 5 successfully

Flash filesystem performance

How to test: run

1. flash_eraseall /dev/mtd4
2. mkdir /mnt/qa
3. mount -t jffs2 /dev/mtdblock4 /mnt/qa
4. cd /mnt/qa
5. bonnie++ -u 0:0 -s 32 -m 16 -r 16

Result should be like this:

Using uid:0, gid:0.
Writing with putc()...done
Writing intelligently...done
Rewriting...done
Reading with getc()...done
Reading intelligently...done
start 'em...done...done...done...
Create files in sequential order...done.
Stat files in sequential order...done.
Delete files in sequential order...done.
Create files in random order...done.
Stat files in random order...done.
Delete files in random order...done.

Version 1.03c       ------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
16              32M   268   8   282   0   311   0  3082  99 +++++ +++ 331.8   1
                    ------Sequential Create------ --------Random Create--------
                    -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
              files  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP
                 16    50   1  2296  24    48   1    48   1  2440  21    48   1
16,32M,268,8,282,0,311,0,3082,99,+++++,+++,331.8,1,16,50,1,2296,24,48,1,48,1,2440,21,48,1