Personal tools

Log in

Changes

From IGEP - ISEE Wiki

Jump to: navigation, search

The Linux kernel

399 bytes removed, 16:25, 19 January 2012
no edit summary
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|'''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 moduleCOM MODULE=== Supported kernels === First of all setup the build environment sourcing this script   source /usr/local/poky/eabi-glibc/arm/environment-setup or * IGEP0032 is also know as IGEP COM PROTON.
source /usr/local/poky/eabi-glibc/environment-setup-arm-none-linux-gnueabi=== Linux OMAP v2.6.37 series ===
if you have updated your SDK environment to latest version (see See the [[Ubuntu 8Linux Kernel 2.04 IGEP v26.0 SDK Virtual Machine37.y]])article
==== Linux OMAP v2.6.35 series ====
See the [[Linux Kernel 2.6.35.y]] article
==== Linux mainline tree (development) ====
<span style="color: rgb(255, 0, 0);">'''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.'''</span>
and build with
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- [cross compiler] omap2plus_defconfig make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- [cross compiler] 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- [cross compiler] modules_install INSTALL_MOD_PATH=[path to your target rootfs]
=See also=
*[[Linux Kernel 2.6.35.y]]
*[[How to setup a cross compiler]]
0
edits