CM-T54: Linux: Kernel - Revision history

Ilya: /* Git clone */

2016-10-19T04:40:12Z

‎Git clone

Lifshitz: /* Git clone */

2015-06-18T12:41:33Z

‎Git clone

Grinberg: /* Git clone */

2015-04-20T06:37:18Z

‎Git clone

Igor: /* Overview */

2014-11-04T11:40:02Z

‎Overview

Grinberg: /* Getting kernel sources */

2014-09-17T07:46:05Z

‎Getting kernel sources

Grinberg: /* Git clone */

2014-06-23T11:05:35Z

‎Git clone

Grinberg: /* Overview */

2014-05-04T14:17:21Z

‎Overview

New page

== Overview ==
Linux kernel for CM-T54 modules provides support for on-board peripherals and abstracts the functionality provided by the hardware.
Current support coverage is specified at [http://compulab.co.il/operating-systems-and-drivers-for-cm-t54-and-sbc-t54/ O/S support coverage map] page.
CompuLab provides ready-to-run binary kernel images, and source code of the modifications and additions made to the Linux kernel to work properly with CM-T54 modules.

== Building kernel for CM-T54 ==
=== Cross-Compiler ===
There are several options for cross-compilation toolchain setup. You can either compile your cross-compiler or use an already built cross-compiler. The cross-compiler should support the ARM embedded-application binary interface ("[http://en.wikipedia.org/wiki/Application_binary_interface#EABI EABI]")
* Pre-built toolchain (recommended):
** [http://www.mentor.com/embedded-software/sourcery-tools/sourcery-codebench/editions/lite-edition/ Sourcery CodeBench Lite]
* Tools for creating cross-compilers:
** [http://crosstool-ng.org/ Crosstool-ng]: Builds a cross-compiler from source. Non-distribution specific.
** [http://www.gentoo.org/proj/en/base/embedded/handbook/index.xml?part=1&chap=4 Crossdev]: Gentoo's cross-compiler builder. Needs Gentoo.

=== Getting kernel sources ===
We assume that you have created {{filename|/home/development/cm-t54/kernel}} directory for CM-T54 kernel development.

==== Git clone ====
* Install [http://git-scm.com/ git] version control system.
* Create a clone of linux kernel tree
<pre>
cd /home/development/cm-t54/kernel
git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git linux-cm-t54
</pre>
* Create a branch for CM-T54 development. The CM-T54 patches are generated vs. v3.14 tag (455c6fdbd219161bd09b1165f11699d6d73de11c commit) in the Linux tree. It is recommended to use exactly the same baseline to avoid merge conflicts.
<pre>
cd /home/development/cm-t54/kernel/linux-cm-t54
git checkout -b cm-t54-dev v3.14
</pre>
* Apply the CM-T54 patch
<pre>
git apply /path/to/cm-t54-linux/kernel/linux-3.14-cm-t54-1.patch
</pre>

{{Note|Future stable kernel versions of 3.14 can also be used by checking out any later tag of v3.14.y stable kernel tree.}}

=== Building the kernel ===
<pre>
export ARCH=arm
export CROSS_COMPILE=arm-none-linux-eabi-
make cm_t54_defconfig
make menuconfig
make && make zImage && make omap5-sbc-t54.dtb \
INSTALL_MOD_PATH=/home/development/cm-t54/rootfs make modules_install
</pre>

In the example above:

* The Linux kernel image {{filename|zImage}} will be created in {{filename|/home/development/cm-t54/kernel/linux-cm-t54/arch/arm/boot}}
* The Device Tree binary {{filename|omap5-sbc-t54.dtb}} will be created in {{filename|/home/development/cm-t54/kernel/linux-cm-t54/arch/arm/boot/dts}}
* The loadable kernel modules will be installed into the {{filename|/home/development/cm-t54/rootfs/lib/modules}} directory.

When the CM-T54 is booted with the kernel image and Device Tree binary created as described above and with networked root filesystem at {{filename|/home/development/cm-t54/rootfs/}}, the system will be able to load the kernel modules properly, thus avoiding module version problems.

== See also ==
* [[CM-T54: Linux: Getting started]]
* [[CM-T54: Linux: Debian]]

[[Category:Linux]]
[[Category:CM-T54]]

@@ Line 55: / Line 55: @@
 <pre>
 cd /home/development/cm-t54/kernel
-git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git linux-cm-t54
+git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-cm-t54
 </pre>
 * Create a branch for CM-T54 development. The CM-T54 patches are generated vs. v4.0.5 tag (be4cb235441a691ee63ba5e00843a9c210be5b8a commit) in the Linux tree. It is recommended to use exactly the same baseline to avoid merge conflicts.
@@ Line 64: / Line 64: @@
 * Apply the CM-T54 patch
 <pre>
-git apply /path/to/cm-t54-linux/kernel/linux-4.0.5-cm-t54-5.patch
+git apply /path/to/cm-t54-linux/kernel/v4.0.5-cm-t54-5/linux-4.0.5-cm-t54-5.patch
 </pre>

@@ Line 27: / Line 27: @@
 === Getting kernel sources ===
 There are various ways to get Linux kernel sources that can be used as a baseline for CM-T54 kernel.
 For instance, a copy of linux-stable git tree can be created or a Linux kernel sources snapshot can be downloaded.
@@ Line 32: / Line 35: @@
 Assuming that the {{filename|/home/development/cm-t54/kernel}} directory structure has been created for CM-T54 kernel development.
-==== Snapshot download ====
+===== Snapshot download =====
-* Download [https://www.kernel.org/pub/linux/kernel/v4.x/linux-4.0.tar.gz v4.0] snapshot with a web browser.
+* Download [https://www.kernel.org/pub/linux/kernel/v4.x/linux-4.0.5.tar.gz v4.0.5] snapshot with a web browser.
-* Extract the downloaded archive {{filename|linux-4.0.tar.gz}}
+* Extract the downloaded archive {{filename|linux-4.0.5.tar.gz}}
 <pre>
 cd /home/development/cm-t54/kernel
-tar xvf /path/to/downloaded/linux-4.0.tar.gz
+tar xvf /path/to/downloaded/linux-4.0.5.tar.gz
-mv linux-4.0 linux-cm-t54
+mv linux-4.0.5 linux-cm-t54
 </pre>
 : This will create {{filename|/home/development/cm-t54/kernel/linux-cm-t54}} directory containing linux kernel tree.
@@ Line 44: / Line 47: @@
 <pre>
 cd /home/development/cm-t54/kernel/linux-cm-t54
-patch -p1 < /path/to/cm-t54-linux/kernel/linux-4.0-cm-t54-4.patch
+patch -p1 < /path/to/cm-t54-linux/kernel/v4.0.5-cm-t54-5/linux-4.0.5-cm-t54-5.patch
 </pre>
-==== Git clone ====
+===== Git clone =====
 * Install [http://git-scm.com/ git] version control system.
 * Create a clone of linux kernel tree
@@ Line 54: / Line 57: @@
 git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git linux-cm-t54
 </pre>
-* Create a branch for CM-T54 development. The CM-T54 patches are generated vs. v4.0 tag (39a8804455fb23f09157341d3ba7db6d7ae6ee76 commit) in the Linux tree. It is recommended to use exactly the same baseline to avoid merge conflicts.
+* Create a branch for CM-T54 development. The CM-T54 patches are generated vs. v4.0.5 tag (be4cb235441a691ee63ba5e00843a9c210be5b8a commit) in the Linux tree. It is recommended to use exactly the same baseline to avoid merge conflicts.
 <pre>
 cd /home/development/cm-t54/kernel/linux-cm-t54
-git checkout -b cm-t54-dev v4.0
+git checkout -b cm-t54-dev v4.0.5
 </pre>
 * Apply the CM-T54 patch
 <pre>
-git apply /path/to/cm-t54-linux/kernel/linux-4.0-cm-t54-4.patch
+git apply /path/to/cm-t54-linux/kernel/linux-4.0.5-cm-t54-5.patch
 </pre>
 {{Note|Future stable kernel versions of 4.0 can also be used by adding the Linux kernel stable repository as a remote and checking out any later tag of the v4.0.y stable kernel branch.}}
 === Building the kernel ===
@@ Line 83: / Line 110: @@
 When the CM-T54 is booted with the kernel image and Device Tree binary created as described above and with networked root filesystem at {{filename|/home/development/cm-t54/rootfs/}}, the system will be able to load the kernel modules properly, thus avoiding module version problems.
 == See also ==
 * [[CM-T54: Linux: Getting started]]
 * [[CM-T54: Linux: Debian]]
 [[Category:Linux]]
 [[Category:CM-T54]]

@@ Line 33: / Line 33: @@
 ==== Snapshot download ====
-* Download [https://www.kernel.org/pub/linux/kernel/v3.x/linux-3.16.2.tar.gz v3.16.2] snapshot with a web browser.
+* Download [https://www.kernel.org/pub/linux/kernel/v4.x/linux-4.0.tar.gz v4.0] snapshot with a web browser.
-* Extract the downloaded archive {{filename|linux-3.16.2.tar.gz}}
+* Extract the downloaded archive {{filename|linux-4.0.tar.gz}}
 <pre>
 cd /home/development/cm-t54/kernel
-tar xvf /path/to/downloaded/linux-3.16.2.tar.gz
+tar xvf /path/to/downloaded/linux-4.0.tar.gz
-mv linux-3.16.2 linux-cm-t54
+mv linux-4.0 linux-cm-t54
 </pre>
 : This will create {{filename|/home/development/cm-t54/kernel/linux-cm-t54}} directory containing linux kernel tree.
@@ Line 44: / Line 44: @@
 <pre>
 cd /home/development/cm-t54/kernel/linux-cm-t54
-patch -p1 < /path/to/cm-t54-linux/kernel/linux-3.16.2-cm-t54-3.patch
+patch -p1 < /path/to/cm-t54-linux/kernel/linux-4.0-cm-t54-4.patch
 </pre>
@@ Line 52: / Line 52: @@
 <pre>
 cd /home/development/cm-t54/kernel
-git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-cm-t54
+git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git linux-cm-t54
 </pre>
-* Create a branch for CM-T54 development. The CM-T54 patches are generated vs. v3.16.2 tag (62de88e8e65811010deac5375f8f0d8b14dc4d94 commit) in the Linux tree. It is recommended to use exactly the same baseline to avoid merge conflicts.
+* Create a branch for CM-T54 development. The CM-T54 patches are generated vs. v4.0 tag (39a8804455fb23f09157341d3ba7db6d7ae6ee76 commit) in the Linux tree. It is recommended to use exactly the same baseline to avoid merge conflicts.
 <pre>
 cd /home/development/cm-t54/kernel/linux-cm-t54
-git checkout -b cm-t54-dev v3.16.2
+git checkout -b cm-t54-dev v4.0
 </pre>
 * Apply the CM-T54 patch
 <pre>
-git apply /path/to/cm-t54-linux/kernel/linux-3.16.2-cm-t54-3.patch
+git apply /path/to/cm-t54-linux/kernel/linux-4.0-cm-t54-4.patch
 </pre>
-{{Note|Future stable kernel versions of 3.16 can also be used by checking out any later tag of the v3.16.y stable kernel branch.}}
+{{Note|Future stable kernel versions of 4.0 can also be used by adding the Linux kernel stable repository as a remote and checking out any later tag of the v4.0.y stable kernel branch.}}
 === Building the kernel ===

@@ Line 3: / Line 3: @@
 Current support coverage is specified at [http://compulab.co.il/operating-systems-and-drivers-for-cm-t54-and-sbc-t54/ O/S support coverage map] page.
 CompuLab provides ready-to-run binary kernel images, and source code of the modifications and additions made to the Linux kernel to work properly with CM-T54 modules.
 == Building kernel for CM-T54 ==
@@ Line 14: / Line 27: @@
 === Getting kernel sources ===
-We assume that you have created {{filename|/home/development/cm-t54/kernel}} directory for CM-T54 kernel development.
+There are various ways to get Linux kernel sources that can be used as a baseline for CM-T54 kernel.
 ==== Git clone ====
@@ Line 23: / Line 54: @@
 git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-cm-t54
 </pre>
-* Create a branch for CM-T54 development. The CM-T54 patches are generated vs. v3.14.8 tag (0c5b3b80f7aeba9b8d25e12f7b321d148a1b1cb9 commit) in the Linux tree. It is recommended to use exactly the same baseline to avoid merge conflicts.
+* Create a branch for CM-T54 development. The CM-T54 patches are generated vs. v3.16.2 tag (62de88e8e65811010deac5375f8f0d8b14dc4d94 commit) in the Linux tree. It is recommended to use exactly the same baseline to avoid merge conflicts.
 <pre>
 cd /home/development/cm-t54/kernel/linux-cm-t54
-git checkout -b cm-t54-dev v3.14.8
+git checkout -b cm-t54-dev v3.16.2
 </pre>
 * Apply the CM-T54 patch
 <pre>
-git apply /path/to/cm-t54-linux/kernel/linux-3.14.8-cm-t54-2.patch
+git apply /path/to/cm-t54-linux/kernel/linux-3.16.2-cm-t54-3.patch
 </pre>
-{{Note|Future stable kernel versions of 3.14 can also be used by checking out any later tag of v3.14.y stable kernel tree.}}
+{{Note|Future stable kernel versions of 3.16 can also be used by checking out any later tag of the v3.16.y stable kernel branch.}}
 === Building the kernel ===

@@ Line 1: / Line 1: @@
 == Overview ==
-Linux kernel for CM-T54 modules provides support for on-board peripherals and abstracts the functionality provided by the hardware.
+Linux kernel for the CompuLab CM-T54 System-on-Module / Computer-on-Module provides support for on-board peripherals and abstracts the functionality provided by the hardware.
 Current support coverage is specified at [http://compulab.co.il/operating-systems-and-drivers-for-cm-t54-and-sbc-t54/ O/S support coverage map] page.
 CompuLab provides ready-to-run binary kernel images, and source code of the modifications and additions made to the Linux kernel to work properly with CM-T54 modules.