Rpi kernel compilation - Revision history

Tufty: Transferred to RPi Kernel Compilation, intentionally blanking and redirecting

2012-01-28T20:28:36Z

Transferred to RPi Kernel Compilation, intentionally blanking and redirecting

Tufty: Adding template

2012-01-28T16:26:26Z

Adding template

Phoque: Category

2012-01-26T14:56:50Z

Abusse at 07:27, 25 January 2012

2012-01-25T07:27:28Z

Abutkus: /* compiling */

2012-01-22T22:03:16Z

‎compiling

Abusse at 13:45, 22 January 2012

2012-01-22T13:45:12Z

Abusse: /* compiling */

2012-01-22T13:31:42Z

‎compiling

Abusse: /* compiling */

2012-01-22T12:49:53Z

‎compiling

Rew: Created page with "= Raspberry PI kernel compilation = You can compile the kernel on the board itself, but you can also cross compile on a standard Linux machine (or maybe even on Windows machines..."

2012-01-22T09:31:10Z

Created page with "= Raspberry PI kernel compilation = You can compile the kernel on the board itself, but you can also cross compile on a standard Linux machine (or maybe even on Windows machines..."

New page

= Raspberry PI kernel compilation =

You can compile the kernel on the board itself, but you can also cross compile on a standard Linux machine (or maybe even on Windows machines?) .

The following documents my attempts at compiling the raspberry pi kernel.

== cross compiling ==

=== getting the compiler ===

On Ubuntu Oneiric getting the arm cross compiler can be as easy as:

sudo apt-get install gcc-4.6-arm-linux-gnueabi

(TODO: Is this the right one? More packages required? I did this a while ago! TODO: Other distributions?)

=== getting the sources ===

==== using git ====
create a directory where you can work on the raspberry pi software. I called mine "raspberrypi". Then clone the git repository.

mkdir raspberrypi
cd raspberrypi
git clone https://github.com/raspberrypi/linux.git
cd linux

==== using the patch ====

TODO: write this.

=== compiling ===

Next you have to configure the kernel.
make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- oldconfig

This will ask the least amount of questions. I selected processor "6" (the first (only?) broadcom processor I saw). '''Someone at rapsberrypi foundation should publish a proper config'''.

Then building the kernel:
make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- -k

At the moment (Jan 22nd, 2012) there is an undeclared function and some undeclared variables in arch/arm/mach-bcmring/dma.c , and a whole bunch of mach/gpio.h not found errors.

You can add "-j 3" to improve compilation speed if you have enough RAM and 2 cores. Use "-j 5" if you have 4 cores. (I recommend one more than the number of cores, to allow a bit of overlapping CPU operations with IO)

== on the Raspberry pi itself ==

Get the sources just like above.

TODO: write the rest of this section.

@@ Line 1: / Line 1: @@
-= Raspberry PI kernel compilation =
+#REDIRECT [[RPi Kernel Compilation]]
-−
-You can compile the kernel on the board itself, but because of the limited resources it will take a lot of time. Alternatively you can crosscompile the kernel on another machine running Linux, Windows or OS X.
-−
-== Compiling on the Raspberry pi itself ==
-−
-TODO: write the rest of this section.
-−
-== Cross compiling on a foreign machine==
-−
-=== Ubuntu Linux ===
-−
-==== getting the compiler ====
-−
-On Ubuntu Oneiric getting the arm cross compiler can be as easy as:
-−
- sudo apt-get install gcc-4.6-arm-linux-gnueabi
-−
-(TODO: Is this the right one? More packages required? I did this a while ago! TODO: Other distributions?)
-−
-==== getting the sources ====
-−
-create a directory where you can work on  the raspberry pi software. I called mine "raspberrypi". Then clone the git repository.
-−
- mkdir raspberrypi
- cd raspberrypi
- git clone https://github.com/raspberrypi/linux.git
- cd linux
-−
-==== compiling ====
-−
-Next you have to configure the kernel:
- cp arch/arm/configs/bcmrpi_cutdown_defconfig .config
- make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- oldconfig
-−
-Then building the kernel:
- make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- -k
-−
-You can use the "-j" flag to improve compilation time. If you have a dual core machine you can use "-j 3", for a quad core machine you can use "-j 6", and so on.
-−
-If you get the error messages that arm-linux-gnueabi-gcc cannot be found when running make, run the following command:
-−
- sudo ln -s /usr/bin/arm-linux-gnueabi-gcc-4.6 /usr/bin/arm-linux-gnueabi-gcc
-−
-this creates a symbolic link to the 4.6 gcc binary
-−
-=== Gentoo Linux ===
-−
-==== getting the compiler ====
-−
-Build the cross toolchain:
- crossdev -v -t arm-unknown-linux-gnueabi
-−
-This command will most certainly fail on your machine. What you have to do to make it work, is to adjust the cross tools versions with the "--b", "--g", "--k" and "--l" flags. For the exact usage refer to the crossdev manpage. A good starting point for figuring out the right versions are those which are stable for the arm architecture.
-−
-==== getting the sources ====
-−
-create a directory where you can work on  the raspberry pi software. I called mine "raspberrypi". Then clone the git repository.
-−
- mkdir raspberrypi
- cd raspberrypi
- git clone https://github.com/raspberrypi/linux.git
- cd linux
-−
-==== compiling ====
-−
-Next you have to configure the kernel:
- cp arch/arm/configs/bcmrpi_cutdown_defconfig .config
- make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- oldconfig
-−
-Then building the kernel:
- make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- -k
-−
-You can use the "-j" flag to improve compilation time. If you have a dual core machine you can use "-j 3", for a quad core machine you can use "-j 6", and so on.
-−
-=== Windows ===
-−
-TODO
-−
-=== OS X ===
-−
-TODO
-−
-−
-−
-{{Template:Raspberry Pi}}
-[[Category: RaspberryPi]]

← Older revision		Revision as of 16:26, 28 January 2012
Line 83:		Line 83:


		+
		+	{{Template:Raspberry Pi}}
	[[Category: RaspberryPi]]		[[Category: RaspberryPi]]

← Older revision		Revision as of 14:56, 26 January 2012
Line 81:		Line 81:

	TODO		TODO
		+
		+
		+	[[Category: RaspberryPi]]

@@ Line 39: / Line 39: @@
 You can use the "-j" flag to improve compilation time. If you have a dual core machine you can use "-j 3", for a quad core machine you can use "-j 6", and so on.
-nb. If you get the error messages that arm-linux-gnueabi-gcc cannot be found when running make run the following command:
+If you get the error messages that arm-linux-gnueabi-gcc cannot be found when running make, run the following command:
-sudo ln -s /usr/bin/arm-linux-gnueabi-gcc-4.6 /usr/bin/arm-linux-gnueabi-gcc
+ sudo ln -s /usr/bin/arm-linux-gnueabi-gcc-4.6 /usr/bin/arm-linux-gnueabi-gcc
-this basically creates a symbolic link to the 4.6 binary
+this creates a symbolic link to the 4.6 gcc binary
 === Gentoo Linux ===

← Older revision		Revision as of 22:03, 22 January 2012
Line 38:		Line 38:

	You can use the "-j" flag to improve compilation time. If you have a dual core machine you can use "-j 3", for a quad core machine you can use "-j 6", and so on.		You can use the "-j" flag to improve compilation time. If you have a dual core machine you can use "-j 3", for a quad core machine you can use "-j 6", and so on.
		+
		+	nb. If you get the error messages that arm-linux-gnueabi-gcc cannot be found when running make run the following command:
		+
		+	sudo ln -s /usr/bin/arm-linux-gnueabi-gcc-4.6 /usr/bin/arm-linux-gnueabi-gcc
		+
		+	this basically creates a symbolic link to the 4.6 binary

	=== Gentoo Linux ===		=== Gentoo Linux ===

@@ Line 40: / Line 40: @@
   make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- -k
-At the moment (Jan 22nd, 2012) there is an undeclared function and some undeclared variables in arch/arm/mach-bcmring/dma.c , and a whole bunch of mach/gpio.h not found errors.
+You can use the "-j" flag to improve compilation time. If you have a dual core machine you can use "-j 3", for a quad core machine you can use "-j 6", and so on.
-−
-You can add "-j 3" to improve compilation speed if you have enough RAM and 2 cores. Use "-j 5" if you have 4 cores. (I recommend one more than the number of cores, to allow a bit of overlapping CPU operations with IO)
 == on the Raspberry pi itself ==