Compiling the kernel - Revision history

79.65.221.138: /* Serial Console */

79.65.221.138 — Tue, 16 Feb 2016 17:06:41 GMT

Serial Console

← Older revision		Revision as of 17:06, 16 February 2016
Line 97:		Line 97:
	4		4

-	There is ~~an other~~ 4 Pin connector ~~near~~ on ~~booth th~~ n800 and n810. those are related to usb.(we did get some bus reset signals when playing with them)	+	There is another 4 Pin connector nearby, on both the n800 and n810. those are related to usb.(we did get some bus reset signals when playing with them)

	1		1

79.65.221.138: /* Menuconfig */

79.65.221.138 — Tue, 16 Feb 2016 17:03:33 GMT

Menuconfig

← Older revision		Revision as of 17:03, 16 February 2016
Line 49:		Line 49:
	$cc -print-file-name=libncursesw.so \| grep -q /		$cc -print-file-name=libncursesw.so \| grep -q /
	if [ $? -eq 0 ]; then		if [ $? -eq 0 ]; then
-
-	Ken and Jen Perkes - What a great idea, Luisa: THE GRATEFUL COUNTDOWN!!! That is one of your many divine aueribttts your gratitude . . . and love! Let me just add that I am surely grateful to have such a wonderful daughter! DadP.S. Do we have any photos of Nate WITHOUT a camera in his hand? : )

	=Things to Remember When Working with Linux Kernel and Maemo=		=Things to Remember When Working with Linux Kernel and Maemo=

188.165.15.156: /* Deploying the Kernel Onto the Device */

188.165.15.156 — Thu, 14 Jun 2012 05:06:09 GMT

Deploying the Kernel Onto the Device

← Older revision		Revision as of 05:06, 14 June 2012
Line 50:		Line 50:
	if [ $? -eq 0 ]; then		if [ $? -eq 0 ]; then

-	~~=Deploying the Kernel Onto the Device=~~	+	Ken and Jen Perkes - What a great idea, Luisa: THE GRATEFUL COUNTDOWN!!! That is one of your many divine aueribttts your gratitude . . . and love! Let me just add that I am surely grateful to have such a wonderful daughter! DadP.S. Do we have any photos of Nate WITHOUT a camera in his hand? : )
-		+
-	~~The kernel kernel image is deployed onto the device by issuing the following command~~:	+
-		+
-	~~# flasher -f -k /scratchbox/users/<username>/targets/MAEMO_KERNEL/usr/share/osso/kernels/zImage-su-18-<yyyyww>~~	+
-		+
-	~~This command~~ is ~~executed outside Scratchbox, assuming that the flasher utility is in $PATH~~.	+
-		+
-	~~Or if you want to be safe, you can test boot it with: (without actually permanently modifying the kernel)~~	+
-		+
-	~~# flasher -l -b -k /scratchbox/users/<username>/targets/MAEMO_KERNEL/usr/share/osso/kernels/zImage-su-18-<yyyyww>~~	+
-		+
-	~~instead.~~	+
-		+
-	If that ~~doesn't work (hangs indefinitely while trying~~ to ~~find device~~)~~, try:~~	+
-	~~mount -t usbfs none /proc/bus/usb/~~	+

	=Things to Remember When Working with Linux Kernel and Maemo=		=Things to Remember When Working with Linux Kernel and Maemo=

213.226.131.133: /* Flash Kernel Image from maemo.org */

213.226.131.133 — Thu, 11 Nov 2010 20:02:26 GMT

Flash Kernel Image from maemo.org

← Older revision		Revision as of 20:02, 11 November 2010
Line 87:		Line 87:

	After this, flash the kernel image as instructed in Section 4.		After this, flash the kernel image as instructed in Section 4.
		+
		+	----
		+
		+	----

	==Flash from Fiasco Image==		==Flash from Fiasco Image==

twaelti at 21:07, 19 October 2009

twaelti — Mon, 19 Oct 2009 21:07:25 GMT

← Older revision		Revision as of 21:07, 19 October 2009
Line 129:		Line 129:


-	[[Category:~~HowTos~~]]	+	[[Category:HowTo]]
	[[Category:Midgard wiki]]		[[Category:Midgard wiki]]

87.72.215.200: /* Serial Console */ Some odd tags had made their way into the command

87.72.215.200 — Fri, 19 Jun 2009 20:19:59 GMT

Serial Console: Some odd tags had made their way into the command

← Older revision		Revision as of 20:19, 19 June 2009
Line 118:		Line 118:
	Once your done with your cable, enable the R&D mode and set the serial console flag and connect via 8N1,115200.		Once your done with your cable, enable the R&D mode and set the serial console flag and connect via 8N1,115200.
	<pre>		<pre>
-	$sudo ./flasher ~~<del>~~enable-rd-mode ~~</del>~~set-rd-flags=serial-console	+	$sudo ./flasher --enable-rd-mode --set-rd-flags=serial-console
	Password:		Password:
	Suitable USB device not found, waiting		Suitable USB device not found, waiting

sjgadsby: /* Modifying Default Kernel Configuration */ cleaning up

sjgadsby — Sun, 08 Mar 2009 22:03:45 GMT

Modifying Default Kernel Configuration: cleaning up

← Older revision		Revision as of 22:03, 8 March 2009
Line 28:		Line 28:
	'''3.''' Make your modifications to ~/maemo_kernel/kernel-source-diablo-2.6.21/kernel-source/arch/arm/configs/n770_defconfig		'''3.''' Make your modifications to ~/maemo_kernel/kernel-source-diablo-2.6.21/kernel-source/arch/arm/configs/n770_defconfig

-	'''4.''' Recompile the kernel image.	+	'''4.''' Recompile the kernel image:

	$ cd		$ cd

sjgadsby: /* Modifying Default Kernel Configuration */ cleaning up

sjgadsby — Sun, 08 Mar 2009 22:02:35 GMT

Modifying Default Kernel Configuration: cleaning up

← Older revision		Revision as of 22:02, 8 March 2009
Line 16:		Line 16:
	In order to modify the default kernel configuration, a few things need to be done. Assuming that the kernel has been built at least once, perform the following procedure to build a modified kernel for Maemo:		In order to modify the default kernel configuration, a few things need to be done. Assuming that the kernel has been built at least once, perform the following procedure to build a modified kernel for Maemo:

-	'''1.''' Edit ~/maemo-kernel/kernel-source-diablo-2.6.21/debian/rules so that modifications may be done	+	'''1.''' Edit ~/maemo-kernel/kernel-source-diablo-2.6.21/debian/rules so that modifications may be done.

-	Make sure the following two lines are commented or removed completely:	+	Make sure the following two lines are commented out or removed completely:
	* build-stamp section: tar jxf /usr/src/kernel-source-$(SOURCE_VERSION).tar.bz2		* build-stamp section: tar jxf /usr/src/kernel-source-$(SOURCE_VERSION).tar.bz2
	* clean section: rm -rf kernel-source-$(SOURCE_VERSION)		* clean section: rm -rf kernel-source-$(SOURCE_VERSION)

-	'''2.''' Change file permissions for default config file	+	'''2.''' Change file permissions for default config file.

	$ chmod a+w ~/maemo-kernel/kernel-source-diablo-2.6.21/kernel-source/arch/arm/configs/n770_defconfig		$ chmod a+w ~/maemo-kernel/kernel-source-diablo-2.6.21/kernel-source/arch/arm/configs/n770_defconfig
Line 28:		Line 28:
	'''3.''' Make your modifications to ~/maemo_kernel/kernel-source-diablo-2.6.21/kernel-source/arch/arm/configs/n770_defconfig		'''3.''' Make your modifications to ~/maemo_kernel/kernel-source-diablo-2.6.21/kernel-source/arch/arm/configs/n770_defconfig

-	'''4.''' Recompile the kernel image	+	'''4.''' Recompile the kernel image.

	$ cd		$ cd

sjgadsby: /* Modules and initfs */ cleaning up

sjgadsby — Sun, 08 Mar 2009 21:59:47 GMT

Modules and initfs: cleaning up

← Older revision		Revision as of 21:59, 8 March 2009
Line 71:		Line 71:
	Below is a list of things that should be taken into consideration when working with the Linux kernel and Maemo.		Below is a list of things that should be taken into consideration when working with the Linux kernel and Maemo.

-	=Modules and ~~initfs~~=	+	=Modules and Initfs=
-	Your kernel image ~~have to~~ be compatible with modules in initfs image on the device. If you flash custom kernel image incompatible with modules in ~~this~~ initfs you may see constants reboots. This can be fixed either by making the kernel compatible (use same or very similar gcc compiler and kernel configuration) or by rebuilding initfs image with your version of modules. For a list of ~~those~~ essential modules see: '''/lib/modules/current''' in the initfs image or '''/mnt/initfs/lib/modules/current''' directly on the device. Also if you enabled some additional functionality as modules you may need to copy them manually to the initfs on the device (if there is free space) or ~~better~~ put them somewhere in the root filesystem.	+	Your kernel image must be compatible with the modules in the initfs image on the device. If you flash a custom kernel image that is incompatible with the modules in initfs, you may see constants reboots. This can be fixed either by making the kernel compatible (use same or very similar gcc compiler and kernel configuration) or by rebuilding the initfs image with your version of modules. For a list of essential modules see: '''/lib/modules/current''' in the initfs image or '''/mnt/initfs/lib/modules/current''' directly on the device. Also, if you enabled some additional functionality as modules, you may need to copy them manually to the initfs on the device (if there is free space) or put them somewhere in the root filesystem of the device.

	=Kernel Partition Size=		=Kernel Partition Size=

sjgadsby: /* Flash Kernel Image from Maemo.org */ "maemo.org", not "Maemo.org"

sjgadsby — Sun, 08 Mar 2009 21:43:20 GMT

Flash Kernel Image from Maemo.org: "maemo.org", not "Maemo.org"

← Older revision		Revision as of 21:43, 8 March 2009
Line 81:		Line 81:
	For example, flashing an oversized kernel image renders the device useless. In order to get the device working again, select one of the following two options.		For example, flashing an oversized kernel image renders the device useless. In order to get the device working again, select one of the following two options.

-	==Flash Kernel Image from ~~Maemo~~.org==	+	==Flash Kernel Image from maemo.org==
	You can install a fully working kernel image by installing the su-18-kernel image available on maemo.org. Issue the following command in Scratchbox:		You can install a fully working kernel image by installing the su-18-kernel image available on maemo.org. Issue the following command in Scratchbox: