Kernel Reconfiguration - Revision history

Ashcharles at 23:42, 1 April 2016

2016-04-01T23:42:08Z

Gerardo Richarte: added info on configuring 2.6.39

2011-08-02T18:06:57Z

added info on configuring 2.6.39

Nick: /* Overo */

2011-02-21T15:51:36Z

‎Overo

Searchworks: remove spam

2010-11-23T23:02:47Z

remove spam

Aqisecoxefi at 22:37, 23 November 2010

2010-11-23T22:37:06Z

Searchworks: remove spam

2010-11-11T06:17:46Z

remove spam

Shescort1: /* Overo */

2010-11-11T03:12:39Z

‎Overo

Sellis: Removed redundant cd command

2010-08-30T09:21:14Z

Removed redundant cd command

Sellis: Use virtual/kernel in bitbake commands

2010-08-30T09:18:22Z

Use virtual/kernel in bitbake commands

Searchworks: Overo before Verdex

2010-08-06T15:48:31Z

Overo before Verdex

← Older revision		Revision as of 23:42, 1 April 2016
Line 1:		Line 1:
		+	[http://www.yoctoproject.org/docs/1.6.1/kernel-dev/kernel-dev.html This] provides the most complete documentation for kernel development in a Yocto environment.
		+
	[[Category:How_to_-_linux]]		[[Category:How_to_-_linux]]
	[[Category:How_to_-_general]]		[[Category:How_to_-_general]]

@@ Line 47: / Line 47: @@
   $ cp ${OVEROTOP}/tmp/work/overo-angstrom-linux/gnueabi/linux-omap3-2.6.32-r51/git/.config \
      ${OVEROTOP}/org.openembedded.dev/recipes/linux/linux-omap3-2.6.32/overo/defconfig
 Then rebuild the kernel.

@@ Line 37: / Line 37: @@
 To modify the kernel configuration, run menuconfig via bitbake. Make your changes and save the configuration.
-  $ bitbake -c menuconfig virtual/linux
+  $ bitbake -c menuconfig virtual/kernel
 The new kernel configuration file you created can be found here.

@@ Line 1: / Line 1: @@
 [[Category:How_to_-_linux]]
 [[Category:How_to_-_general]]
@@ Line 13: / Line 12: @@
   $ cd $OVEROTOP
   $ grep linux org.openembedded/conf/machine/overo.conf
-  PREFERRED_PROVIDER_virtual/kernel = &quot;linux-omap3&quot;
+  PREFERRED_PROVIDER_virtual/kernel = "linux-omap3"
 And the current revision as defined here
@@ Line 68: / Line 67: @@
 To reconfigure the kernel with the current state of Gumstix's OE things, you will need ''gnome-terminal''. Run this command: '''bitbake gumstix-kernel -c menuconfig'''
-NOTE: You have to have ncurses and ncurses-dev installed in order for the MENUCONFIG to actually work.&lt;br&gt;
+NOTE: You have to have ncurses and ncurses-dev installed in order for the MENUCONFIG to actually work.<br>
-NOTE: If a screen flashes infront of you and dissapears edit $OE_HOME/org.openembedded.snapshot/conf/bitbake.conf to the following &lt;br&gt;
+NOTE: If a screen flashes infront of you and dissapears edit $OE_HOME/org.openembedded.snapshot/conf/bitbake.conf to the following <br>
-&lt;code&gt;&lt;pre&gt;
+<code><pre>
 -GNOME_TERMCMDRUN = '${GNOME_TERMCMD} -x ${SHELLRCCMD}'
 +GNOME_TERMCMDRUN = '${GNOME_TERMCMD} -x ${SHELLCMDS}'
-&lt;/pre&gt;&lt;/code&gt;
+</pre></code>
 NOTE: If you don't have gnome-terminal installed and wish to use xterm instead, use:
-&lt;code&gt;&lt;pre&gt;
+<code><pre>
--GNOME_TERMCMD = 'gnome-terminal --disable-factory -t &quot;$TERMWINDOWTITLE&quot;'
+-GNOME_TERMCMD = 'gnome-terminal --disable-factory -t "$TERMWINDOWTITLE"'
 -GNOME_TERMCMDRUN = '${GNOME_TERMCMD} -x ${SHELLRCCMD}'
-+GNOME_TERMCMD = 'xterm -title &quot;$TERMWINDOWTITLE&quot;'
++GNOME_TERMCMD = 'xterm -title "$TERMWINDOWTITLE"'
 +GNOME_TERMCMDRUN = '${GNOME_TERMCMD} -e ${SHELLCMDS}'
-&lt;/pre&gt;&lt;/code&gt;
+</pre></code>
-The kernel config information is kept in&lt;br&gt;
+The kernel config information is kept in<br>
-''$OE_HOME/com.gumstix.collection/packages/linux/gumstix-kernel-2.6.XX/gumstix-custom-YYYYY/defconfig''&lt;br&gt;
+''$OE_HOME/com.gumstix.collection/packages/linux/gumstix-kernel-2.6.XX/gumstix-custom-YYYYY/defconfig''<br>
 where XX is the current default kernel version for your bitbake environment.  That nugget is set in the
 ''$OE_HOME/com.gumstix.collection/conf/machine/include/gumstix.inc'' file, under the PREFERRED_VERSION_gumstix-kernel
-and YYYYY is usually one of connex/basix/verdex.  That nugget comes from&lt;br&gt;
+and YYYYY is usually one of connex/basix/verdex.  That nugget comes from<br>
 ''$OE_HOME/build/conf/auto.conf''
-After running menuconfig, running &quot;bitbake -c rebuild gumstix-kernel&quot; will blow away the customizations just made.  There is probably a better way to do this, but in order to preserve the customizations, you can copy the new config file and replace the default config.  For example, to preserve a verdex board's config, do:
+After running menuconfig, running "bitbake -c rebuild gumstix-kernel" will blow away the customizations just made.  There is probably a better way to do this, but in order to preserve the customizations, you can copy the new config file and replace the default config.  For example, to preserve a verdex board's config, do:
-&lt;code&gt;&lt;pre&gt;
+<code><pre>
 cp \
   $OE_HOME/tmp/work/gumstix-custom-verdex-angstrom-linux-gnueabi/gumstix-kernel-2.6.21-r1/linux-2.6.21/.config \
   $OE_HOME/com.gumstix.collection/packages/linux/gumstix-kernel-2.6.21/gumstix-custom-verdex/defconfig
-&lt;/pre&gt;&lt;/code&gt;
+</pre></code>
 Now that you have replaced the default config, the following commands will rebuild and repackage the new kernel and create new images for you:
-&lt;code&gt;&lt;pre&gt;
+<code><pre>
 bitbake -c rebuild gumstix-kernel
 bitbake -c rebuild task-base-gumstix
 bitbake gumstix-basic-image
-&lt;/pre&gt;&lt;/code&gt;
+</pre></code>
@@ Line 113: / Line 112: @@
 Your kernel is now larger than the 1MB originally specified so do_sizecheck() fails?
-You'll probably want to edit the ~/verdex-oe/org.openembedded.dev/conf/machine/include and change the maximum image size to, say, 2MB, i.e. KERNEL_IMAGE_MAXSIZE = &quot;2097153&quot;.  Actually, you should really do this in the user.collections directory to keep the original source tree clean.
+You'll probably want to edit the ~/verdex-oe/org.openembedded.dev/conf/machine/include and change the maximum image size to, say, 2MB, i.e. KERNEL_IMAGE_MAXSIZE = "2097153".  Actually, you should really do this in the user.collections directory to keep the original source tree clean.

@@ Line 1: / Line 1: @@
 [[Category:How_to_-_linux]]
 [[Category:How_to_-_general]]
@@ Line 12: / Line 13: @@
   $ cd $OVEROTOP
   $ grep linux org.openembedded/conf/machine/overo.conf
-  PREFERRED_PROVIDER_virtual/kernel = "linux-omap3"
+  PREFERRED_PROVIDER_virtual/kernel = &quot;linux-omap3&quot;
 And the current revision as defined here
@@ Line 67: / Line 68: @@
 To reconfigure the kernel with the current state of Gumstix's OE things, you will need ''gnome-terminal''. Run this command: '''bitbake gumstix-kernel -c menuconfig'''
-NOTE: You have to have ncurses and ncurses-dev installed in order for the MENUCONFIG to actually work.<br>
+NOTE: You have to have ncurses and ncurses-dev installed in order for the MENUCONFIG to actually work.&lt;br&gt;
-NOTE: If a screen flashes infront of you and dissapears edit $OE_HOME/org.openembedded.snapshot/conf/bitbake.conf to the following <br>
+NOTE: If a screen flashes infront of you and dissapears edit $OE_HOME/org.openembedded.snapshot/conf/bitbake.conf to the following &lt;br&gt;
-<code><pre>
+&lt;code&gt;&lt;pre&gt;
 -GNOME_TERMCMDRUN = '${GNOME_TERMCMD} -x ${SHELLRCCMD}'
 +GNOME_TERMCMDRUN = '${GNOME_TERMCMD} -x ${SHELLCMDS}'
-</pre></code>
+&lt;/pre&gt;&lt;/code&gt;
 NOTE: If you don't have gnome-terminal installed and wish to use xterm instead, use:
-<code><pre>
+&lt;code&gt;&lt;pre&gt;
--GNOME_TERMCMD = 'gnome-terminal --disable-factory -t "$TERMWINDOWTITLE"'
+-GNOME_TERMCMD = 'gnome-terminal --disable-factory -t &quot;$TERMWINDOWTITLE&quot;'
 -GNOME_TERMCMDRUN = '${GNOME_TERMCMD} -x ${SHELLRCCMD}'
-+GNOME_TERMCMD = 'xterm -title "$TERMWINDOWTITLE"'
++GNOME_TERMCMD = 'xterm -title &quot;$TERMWINDOWTITLE&quot;'
 +GNOME_TERMCMDRUN = '${GNOME_TERMCMD} -e ${SHELLCMDS}'
-</pre></code>
+&lt;/pre&gt;&lt;/code&gt;
-The kernel config information is kept in<br>
+The kernel config information is kept in&lt;br&gt;
-''$OE_HOME/com.gumstix.collection/packages/linux/gumstix-kernel-2.6.XX/gumstix-custom-YYYYY/defconfig''<br>
+''$OE_HOME/com.gumstix.collection/packages/linux/gumstix-kernel-2.6.XX/gumstix-custom-YYYYY/defconfig''&lt;br&gt;
 where XX is the current default kernel version for your bitbake environment.  That nugget is set in the
 ''$OE_HOME/com.gumstix.collection/conf/machine/include/gumstix.inc'' file, under the PREFERRED_VERSION_gumstix-kernel
-and YYYYY is usually one of connex/basix/verdex.  That nugget comes from<br>
+and YYYYY is usually one of connex/basix/verdex.  That nugget comes from&lt;br&gt;
 ''$OE_HOME/build/conf/auto.conf''
-After running menuconfig, running "bitbake -c rebuild gumstix-kernel" will blow away the customizations just made.  There is probably a better way to do this, but in order to preserve the customizations, you can copy the new config file and replace the default config.  For example, to preserve a verdex board's config, do:
+After running menuconfig, running &quot;bitbake -c rebuild gumstix-kernel&quot; will blow away the customizations just made.  There is probably a better way to do this, but in order to preserve the customizations, you can copy the new config file and replace the default config.  For example, to preserve a verdex board's config, do:
-<code><pre>
+&lt;code&gt;&lt;pre&gt;
 cp \
   $OE_HOME/tmp/work/gumstix-custom-verdex-angstrom-linux-gnueabi/gumstix-kernel-2.6.21-r1/linux-2.6.21/.config \
   $OE_HOME/com.gumstix.collection/packages/linux/gumstix-kernel-2.6.21/gumstix-custom-verdex/defconfig
-</pre></code>
+&lt;/pre&gt;&lt;/code&gt;
 Now that you have replaced the default config, the following commands will rebuild and repackage the new kernel and create new images for you:
-<code><pre>
+&lt;code&gt;&lt;pre&gt;
 bitbake -c rebuild gumstix-kernel
 bitbake -c rebuild task-base-gumstix
 bitbake gumstix-basic-image
-</pre></code>
+&lt;/pre&gt;&lt;/code&gt;
@@ Line 112: / Line 113: @@
 Your kernel is now larger than the 1MB originally specified so do_sizecheck() fails?
-You'll probably want to edit the ~/verdex-oe/org.openembedded.dev/conf/machine/include and change the maximum image size to, say, 2MB, i.e. KERNEL_IMAGE_MAXSIZE = "2097153".  Actually, you should really do this in the user.collections directory to keep the original source tree clean.
+You'll probably want to edit the ~/verdex-oe/org.openembedded.dev/conf/machine/include and change the maximum image size to, say, 2MB, i.e. KERNEL_IMAGE_MAXSIZE = &quot;2097153&quot;.  Actually, you should really do this in the user.collections directory to keep the original source tree clean.

@@ Line 9: / Line 9: @@
 These instructions assume you are using the default gumstix-oe kernel which is declared here
-   On this site in the lowest consumption 60 USD
-[http://www.ck-wholeslae.com calvin klein] Underwear Known as the world's finest designer underwear, Calvin Klein Underwear was formed in 1982 and would forever alter the way the world viewed-and bought - Men's Calvin klein underwear.
-On this site in the lowest consumption 60 USD
-Once a utilitarian product, Men's [http://www.ck-wholeslae.com calvin klein underwear]suddenly became an object of desire. New advertising campaigns communicated the message of the updated, sexy sensibility that distinguished ck underwear from all others. A complete woMen's [http://www.ck-wholeslae.com underwear] line followed in 1983. Each season since then, the brand has delivered a new line including basics, basics in fashion colors, as well as fashion-forward, trendy [http://www.ck-wholeslae.com ck underwear] to their customers. Defined by iconic simplicity and subtle seduction, there is nothing like a Calvin Klein design.
-−
   $ cd $OVEROTOP
   $ grep linux org.openembedded/conf/machine/overo.conf

@@ Line 37: / Line 37: @@
 To modify the kernel configuration, run menuconfig via bitbake. Make your changes and save the configuration.
   $ bitbake -c menuconfig virtual/linux
@@ Line 56: / Line 55: @@
 Then rebuild the rootfs to get the modules installed correctly.
-Substitute the image you are using, the example assumes the omap3-console-image.
+Substitute the image you are using, the example if you are using the omap3-console-image.
   $ bitbake omap3-console-image

@@ Line 8: / Line 8: @@
 ==Overo==
-These instructions assume you are using the default gumstix-oe kernel as defined here
+These instructions assume you are using the default gumstix-oe kernel which is declared here
   $ cd $OVEROTOP
@@ Line 19: / Line 19: @@
   linux-omap3                            0:2.6.32-r51
-So the rest of the example will assume linux-omap3-2.6.32 revision 51.
+So the rest of the example will assume linux-omap3-2.6.32 revision 51. This is the kernel that will be built when we use the reference 'virtual/kernel' in bitbake commands.
 Substitute the kernel version and revision your system is using in the following steps.
@@ Line 28: / Line 28: @@
 If not run this command
-  $ bitbake linux-omap3-2.6.32
+  $ bitbake virtual/kernel
 This will create a source directory in the ${OVEROTOP}/tmp/work/overo-angstrom-linux-gnueabi directory.
@@ Line 38: / Line 38: @@
   $ cd $OVEROTOP
-  $ bitbake -c menuconfig linux-omap3-2.6.32
+  $ bitbake -c menuconfig virtual/linux
 The new kernel configuration file you created can be found here.
@@ Line 51: / Line 51: @@
 Then rebuild the kernel.
-  $ bitbake -c clean linux-omap3-2.6.32
+  $ bitbake -c clean virtual/kernel
-  $ bitbake -c rebuild linux-omap3-2.6.32
+  $ bitbake virtual/kernel
 Then rebuild the rootfs to get the modules installed correctly.

@@ Line 5: / Line 5: @@
 [[http://bec-systems.com/site/521/best-practices-for-kernel-development-with-openembedded Using kernel tools]]
 ==Overo==
@@ Line 104: / Line 63: @@
 [http://www.gumstix.net/Setup-and-Programming/view/Overo-Setup-and-Programming/Creating-a-bootable-microSD-card/111.html microSD card]
 or by copying to [http://www.gumstix.net/Setup-and-Programming/view/Overo-Setup-and-Programming/Writing-images-to-onboard-nand/111.html onboard nand].
 ==Other notes==