summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2011-10-05 12:07:29 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-10-06 18:46:55 +0100
commitfe76b87e8a9d797555869474daa38114ecddd3da (patch)
treef27e97ca3efc8b0fbbe00a4c2030b82c576da1ce /documentation
parent8d088b972d84a8ca257b16ce34d65d15b648722d (diff)
downloadast2050-yocto-poky-fe76b87e8a9d797555869474daa38114ecddd3da.zip
ast2050-yocto-poky-fe76b87e8a9d797555869474daa38114ecddd3da.tar.gz
documentation/dev-manual/dev-manual-kernel-appendix.xml: config example
I had to add some changes to the way we invoke qemu to show multiple processor support. I needed the qemuparam "-smp 2". There are other minor edits as well. (From yocto-docs rev: 508863634ce537b0936f8e44f87b90bef678c122) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
-rw-r--r--documentation/dev-manual/dev-manual-kernel-appendix.xml34
1 files changed, 29 insertions, 5 deletions
diff --git a/documentation/dev-manual/dev-manual-kernel-appendix.xml b/documentation/dev-manual/dev-manual-kernel-appendix.xml
index 03d1758..533875b 100644
--- a/documentation/dev-manual/dev-manual-kernel-appendix.xml
+++ b/documentation/dev-manual/dev-manual-kernel-appendix.xml
@@ -506,6 +506,23 @@
<para>
If you took the time to work through the example that modifies the kernel source code
in "<link linkend='modifying-the-kernel-source-code'>Modifying the Kernel Source
+ Code</link>" you should already have the Yocto Project files set up on your
+ host machine.
+ </para>
+
+ <para>
+ If you don't have the Yocto Project files established on your system,
+ See "<link linkend='setting-up-the-local-yocto-project-files-git-repository'>Setting
+ Up the Local Yocto Project Files Git Repository</link>" for
+ information.
+ To reconfigure the kernel, this is the only Git repository you need to have set up.
+ </para>
+
+<!--
+
+ <para>
+ If you took the time to work through the example that modifies the kernel source code
+ in "<link linkend='modifying-the-kernel-source-code'>Modifying the Kernel Source
Code</link>" you are already set up to quickly work through this example.
If not, then work through the following list to prepare:
<itemizedlist>
@@ -530,7 +547,7 @@
and Booting the Default QEMU Kernel image</link>" for information.
Do not boot the image in the QEMU emulator at this point.</para></listitem>
</itemizedlist>
- </para>
+ </para> -->
</section>
<section id='examining-the-default-config-smp-behavior'>
@@ -541,7 +558,7 @@
To see this default setting from within the QEMU emulator, boot your image using
the emulator as follows:
<literallayout class='monospaced'>
- $ runqemu qemux86
+ $ runqemu qemux86 qemuparams="-smp 2"
</literallayout>
</para>
@@ -627,12 +644,19 @@
<para>
A good method to isolate changed configurations is to use a combination of the
<filename>menuconfig</filename> tool and simple shell commands.
- Before changing configurations with <filename>menuconfig</filename>, simply rename
- the default <filename>.config</filename>, use <filename>menuconfig</filename> to make
+ Before changing configurations with <filename>menuconfig</filename>, copy the
+ existing <filename>.config</filename> and rename it to something else,
+ use <filename>menuconfig</filename> to make
as many changes an you want and save them, then compare the renamed configuration
file against the newly created file.
You can use the resulting differences as your base to create configuration fragments
to permanently save in your kernel layer.
+ <note>
+ Be sure to make a copy of the <filename>.config</filename> and don't just
+ rename it.
+ The Yocto Project build system needs an existing <filename>.config</filename>
+ from which to work.
+ </note>
</para>
</section>
@@ -651,7 +675,7 @@
<para>
Now run the QEMU emulator:
<literallayout class='monospaced'>
- $ runqemu qemux86
+ $ runqemu qemux86 qemuparams="-smp 2"
</literallayout>
</para>
OpenPOWER on IntegriCloud