Difference between revisions of "Linux Kernel Mainline"

From IGEP - ISEE Wiki

Jump to: navigation, search
(Created page with '<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 cut…')
 
m (Build kernel from sources)
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<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>
+
__TOC__
 +
 
 +
= Introduction =
 +
 
 +
The 'master' branch from git.isee.biz repository 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  
 
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 igep OMAP tree has unpublished patches for IGEP v2 support.  
+
= Build kernel from sources  =
 +
 
 +
'''Download''' the latest unstable version sources and follow next steps:
 +
 
 +
git clone git://git.isee.biz/pub/scm/linux-omap-2.6.git linux
 +
cd linux
 +
 
 +
'''Configure''' Linux kernel for IGEP Processor Boards. A generic configuration is provided for all ARM machines, and can be used as the default by
 +
 
 +
make ARCH=arm omap2plus_defconfig
 +
 
 +
Then '''build''' the kernel, the kernel modules and the device tree files. The result will be an ''zImage'' file in arch/arm/boot directory. Execute:
  
Clone GIT repository from git.isee.biz
+
make ARCH=arm CROSS_COMPILE=[your cross compiler prefix] zImage modules dtbs
  
git clone git://git.isee.biz/pub/scm/linux-omap-2.6.git
+
Note that you can '''install''' the kernel modules to your target rootfs
  
Enter in sources directory
+
make ARCH=arm CROSS_COMPILE=[your cross compiler prefix] modules_install INSTALL_MOD_PATH=[path to your target rootfs] modules_install
  
cd linux-omap-2.6
+
= Known issues =
  
Get your desired branch with
+
[[Category:Linux Kernel]]
git checkout <release> -b <your_named_release>
 
git checkout v2.6.37-2 -b v2.6.37-2-local
 

Latest revision as of 11:49, 2 June 2015

Introduction

The 'master' branch from git.isee.biz repository 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

Build kernel from sources

Download the latest unstable version sources and follow next steps:

git clone git://git.isee.biz/pub/scm/linux-omap-2.6.git linux
cd linux

Configure Linux kernel for IGEP Processor Boards. A generic configuration is provided for all ARM machines, and can be used as the default by

make ARCH=arm omap2plus_defconfig

Then build the kernel, the kernel modules and the device tree files. The result will be an zImage file in arch/arm/boot directory. Execute:

make ARCH=arm CROSS_COMPILE=[your cross compiler prefix] zImage modules dtbs

Note that you can install the kernel modules to your target rootfs

make ARCH=arm CROSS_COMPILE=[your cross compiler prefix] modules_install INSTALL_MOD_PATH=[path to your target rootfs] modules_install

Known issues