Kernel Building - Revision history

PaulEggleton at 16:42, 3 November 2012

2012-11-03T16:42:44Z

← Older revision		Revision as of 16:42, 3 November 2012
Line 1:		Line 1:
			{{Outdated}}

	== Default Build ==		== Default Build ==

Ynezz: add note about distro specific INHERIT

2011-03-09T13:43:47Z

add note about distro specific INHERIT

← Older revision		Revision as of 13:43, 9 March 2011
Line 49:		Line 49:

	The build environment will be well setup for you; you can run regular make commands like <tt>make bzImage</tt> ...etc		The build environment will be well setup for you; you can run regular make commands like <tt>make bzImage</tt> ...etc

			''Please note, that the INHERIT step depends on the distribution you're using, some of the distributions already include the INHERIT in their configuration, so it might work already. You can check that easily using listtask task.''

	== Preserving the custom configuration ==		== Preserving the custom configuration ==

Ynezz: fix devshell howto

2011-03-09T13:36:22Z

fix devshell howto

← Older revision		Revision as of 13:36, 9 March 2011
Line 42:		Line 42:

	== Fine control ==		== Fine control ==
	If you need more control over the configuration and compile process, you can go to the shell by:		If you need more control over the configuration and compile process, add this somewhere into your local.conf:
			INHERIT += "devshell"

			and then you can go to the shell by:
	bitbake -c devshell virtual/kernel		bitbake -c devshell virtual/kernel

	The build environment will be well setup for you; you can run regular make commands like <tt>make bzImage</tt> ...etc		The build environment will be well setup for you; you can run regular make commands like <tt>make bzImage</tt> ...etc

Michaelfung: /* Select kernel version */

2010-10-21T14:20:44Z

Select kernel version

← Older revision		Revision as of 14:20, 21 October 2010
Line 14:		Line 14:
	== Select kernel version ==		== Select kernel version ==

	~~To select which kernel version to build, edit config file ??? and set variable ??? to , for example, 2.6.35~~.		FIXME.

	== Default configuration ==		== Default configuration ==

Michaelfung: /* Kernel image type */

2010-10-21T14:19:25Z

Kernel image type

← Older revision		Revision as of 14:19, 21 October 2010
Line 9:		Line 9:
	== Kernel image type ==		== Kernel image type ==

	What kind of kernel image to build is controlled by the variable <tt>KERNEL_IMAGETYPE</tt>. For example, build image for u-boot		What kind of kernel image to build is controlled by the variable <tt>KERNEL_IMAGETYPE</tt>, which is normally defined in the machine config file. For example, build image for u-boot
	KERNEL_IMAGETYPE = "uImage"		KERNEL_IMAGETYPE = "uImage"

Michaelfung: /* Kernel patches */

2010-10-21T08:14:17Z

Kernel patches

← Older revision		Revision as of 08:14, 21 October 2010
Line 15:		Line 15:

	To select which kernel version to build, edit config file ??? and set variable ??? to , for example, 2.6.35.		To select which kernel version to build, edit config file ??? and set variable ??? to , for example, 2.6.35.

	~~== Kernel patches ==~~

	~~Where to place the patch files and how to configure OE to apply them?~~

	== Default configuration ==		== Default configuration ==

Michaelfung: /* Kernel configuration */

2010-10-21T08:13:07Z

Kernel configuration

← Older revision		Revision as of 08:13, 21 October 2010
Line 20:		Line 20:
	Where to place the patch files and how to configure OE to apply them?		Where to place the patch files and how to configure OE to apply them?

	~~== Kernel configuration ==~~		== Default configuration ==

	=== Default configuration ===

	The default .config file used is normally placed somewhere under recipes/linux named '''defconfig'''.		The default .config file used is normally placed somewhere under recipes/linux named '''defconfig'''.
Line 33:		Line 31:


	=== Apply custom patches ===		== Apply custom patches ==
	FIXME		FIXME

	=== Customize configuration ===		== Customize configuration ==
	If you need to customize the kernel configuration, you may run the menuconfig task by:		If you need to customize the kernel configuration, you may run the menuconfig task by:
	bitbake -c menuconfig virtual/kernel		bitbake -c menuconfig virtual/kernel
Line 43:		Line 41:
	'''Note:''' by default these command requires you to run in X Windows. If you want to work in text terminal only, here's a [[How_to_use_bitbake_without_X_Windows\|how to]].		'''Note:''' by default these command requires you to run in X Windows. If you want to work in text terminal only, here's a [[How_to_use_bitbake_without_X_Windows\|how to]].

	=== Compile ===		== Compile ==
	After that, you can compile the kernel by:		After that, you can compile the kernel by:
	bitbake -f -c compile virtual/kernel		bitbake -f -c compile virtual/kernel

	=== Fine control ===		== Fine control ==
	If you need more control over the configuration and compile process, you can go to the shell by:		If you need more control over the configuration and compile process, you can go to the shell by:
	bitbake -c devshell virtual/kernel		bitbake -c devshell virtual/kernel
	The build environment will be well setup for you; you can run regular make commands like <tt>make bzImage</tt> ...etc		The build environment will be well setup for you; you can run regular make commands like <tt>make bzImage</tt> ...etc

	=== Preserving the custom configuration ===		== Preserving the custom configuration ==
	Changes are lost if you remove the tmpdir or do a "<tt>bitbake -c clean virtual/kernel</tt>", so you		Changes are lost if you remove the tmpdir or do a "<tt>bitbake -c clean virtual/kernel</tt>", so you
	may consider replacing the defconfig with it.		may consider replacing the defconfig with it.

Michaelfung: /* Kernel configuration */

2010-10-21T08:11:19Z

Kernel configuration

← Older revision		Revision as of 08:11, 21 October 2010
Line 22:		Line 22:
	== Kernel configuration ==		== Kernel configuration ==

	~~The default .config file used is placed in ???/defconfig.~~		=== Default configuration ===

			The default .config file used is normally placed somewhere under recipes/linux named '''defconfig'''.
			You may want to search for it, say for vmware:

	If you need to customize the kernel configuration, run the menuconfig task by:		find recipes/linux -name "vmware*"

			And you find it in:
			recipes/linux/linux/vmware/defconfig


			=== Apply custom patches ===
			FIXME

			=== Customize configuration ===
			If you need to customize the kernel configuration, you may run the menuconfig task by:
	bitbake -c menuconfig virtual/kernel		bitbake -c menuconfig virtual/kernel

	~~'''Note:''' by default this command requires you to run in X Windows.~~

			'''Note:''' by default these command requires you to run in X Windows. If you want to work in text terminal only, here's a [[How_to_use_bitbake_without_X_Windows\|how to]].

			=== Compile ===
	After that, you can compile the kernel by:		After that, you can compile the kernel by:
	bitbake -f -c compile virtual/kernel		bitbake -f -c compile virtual/kernel

			=== Fine control ===
			If you need more control over the configuration and compile process, you can go to the shell by:
			bitbake -c devshell virtual/kernel
			The build environment will be well setup for you; you can run regular make commands like <tt>make bzImage</tt> ...etc

			=== Preserving the custom configuration ===
			Changes are lost if you remove the tmpdir or do a "<tt>bitbake -c clean virtual/kernel</tt>", so you
			may consider replacing the defconfig with it.

	[[Category:User]]		[[Category:User]]
	[[Category:FAQ]]		[[Category:FAQ]]

EFfeM at 07:11, 21 October 2010

2010-10-21T07:11:07Z

← Older revision		Revision as of 07:11, 21 October 2010
Line 35:		Line 35:

	[[Category:User]]		[[Category:User]]
			[[Category:FAQ]]

Michaelfung: /* Kernel configuration */

2010-10-20T14:56:40Z

Kernel configuration

← Older revision		Revision as of 14:56, 20 October 2010
Line 15:		Line 15:

	To select which kernel version to build, edit config file ??? and set variable ??? to , for example, 2.6.35.		To select which kernel version to build, edit config file ??? and set variable ??? to , for example, 2.6.35.

			== Kernel patches ==

			Where to place the patch files and how to configure OE to apply them?

	== Kernel configuration ==		== Kernel configuration ==