Kernel build instructions - Revision history

Linux-SWAT at 23:08, 17 March 2014

2014-03-17T23:08:13Z

2013-10-08T05:40:46Z

2011-11-14T18:59:44Z

2011-11-14T18:58:33Z

2011-11-14T18:58:09Z

2011-11-14T18:57:15Z

2011-11-03T00:11:39Z

2011-11-02T23:44:06Z

2011-11-02T23:43:17Z

2011-11-02T23:35:38Z

← Older revision		Revision as of 23:08, 17 March 2014
Line 1:		Line 1:
		+	{{hint\|This tutorial is outdated, as it covers the 2.6.x kernel. Now the Pandora runs on 3.2.x . The new git command is "git checkout --track -b pandora-3.2 origin/pandora-3.2", and the default config is "make omap3_pandora_defconfig". All patches are already applied.
		+	}}
		+
	{{hint\|Kernel will not be binary compatible with one that comes with firmware, meaning you'll need to rebuild all modules too, unless exact same toolchain and source code is used. See "Firmware Compatibility" section.		{{hint\|Kernel will not be binary compatible with one that comes with firmware, meaning you'll need to rebuild all modules too, unless exact same toolchain and source code is used. See "Firmware Compatibility" section.
	}}		}}

@@ Line 17: / Line 17: @@
 ===CodeSourcery G++===
-Usually [https://sourcery.mentor.com/sgpp/lite/arm/portal/subscription?@template=lite CodeSourcery's ARM GNU/Linux tool chain] is used to build OMAP3 kernels, but other variations can be used as well. For [[CodeSourcery]], 2009q1-203 version is recommended (click "all versions" in above page), as 2007q3 doesn't work with kernels above 2.6.29, and 2008q1-2008q3 produce bad code in some situations. The 2011.03 does not work.
+Usually [https://sourcery.mentor.com/sgpp/lite/arm/portal/subscription?@template=lite CodeSourcery's ARM GNU/Linux tool chain] is used to build OMAP3 kernels, but other variations can be used as well. For CodeSourcery, 2009q1-203 version is recommended (click "all versions" in above page), as 2007q3 doesn't work with kernels above 2.6.29, and 2008q1-2008q3 produce bad code in some situations. The 2011.03 does not work.
 See [http://www.elinux.org/ARMCompilers BeagleBoard page] for more information.
@@ Line 57: / Line 57: @@
 ==Firmware Compatibility==
-The firmware kernel is built using OE (openembedded), so the only sure way to get binary compatibility is to use that (see [[Firmware_build_instructions]]).
+The firmware kernel is built using OE (openembedded), so the only sure way to get binary compatibility is to use that. see [[http://pandorawiki.org/%C3%85ngstr%C3%B6m#Firmware_build_instructions]]
 The manual procedure to do the same without using OE would be:

@@ Line 172: / Line 172: @@
 And (almost) finally :
 <source lang="bash">
 cp arch/arm/boot/uImage /path/to/your/pandora/filesystem/boot/
 INSTALL_MOD_PATH="/path/to/your/pandora/filesystem/" make modules_install

@@ Line 175: / Line 175: @@
 INSTALL_MOD_PATH="/path/to/your/pandora/filesystem/" make modules_install
 </source>
 == Building Wi-Fi modules==
@@ Line 229: / Line 230: @@
 chmod 0644 /media/OS/lib/modules/2.6.27.46-omap1/updates/kernel/drivers/net/wireless/p54/*.ko
 </source>
 == First Boot ==

@@ Line 179: / Line 179: @@
 Come back to your main directory, then clone the Wi-Fi git:
 <source lang="bash">
 git clone git://openpandora.org/pandora-wifi.git
 cd pandora-wifi

@@ Line 178: / Line 178: @@
 At the first boot, if modules don't load, type as root :
 <source lang="bash">
-depmod
+depmod -ae
 </source>
 And reboot.

@@ Line 128: / Line 128: @@
 == Building ==
-To build you need to have several environment variables set. If you don't have your toolchain in PATH, you need to add it there:
+To build you need to have several environment variables set. If you don't have your toolchain in PATH, you need to add it:
 DJWillis:
 <source lang="bash">

@@ Line 117: / Line 117: @@
 == More Dirty Things ==
-If you have "mixed implicit and normal rules" errors, edit the Makefile:
+If you have "mixed implicit and normal rules" errors (make >= 3.82), edit the Makefile:
 Remove the "config" at the beginning of the line 448.