dev-manual: Edits to "Trim the Kernel" section.
(From yocto-docs rev: 521866ffe4e9ffe544acd259d2a1c6f05bd3c25a) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
f35f12d864
commit
ae53349aca
|
@ -2710,10 +2710,10 @@
|
||||||
<title>Trim the Kernel</title>
|
<title>Trim the Kernel</title>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
Kernel is built by including policies for hardware-independent
|
The kernel is built by including policies for hardware-independent
|
||||||
aspects.
|
aspects.
|
||||||
What subsystems do you enable?
|
What subsystems do you enable?
|
||||||
What architecture are you building for?
|
For what architecture are you building?
|
||||||
Which drivers do you build by default.
|
Which drivers do you build by default.
|
||||||
<note>You can modify the kernel source if you want to help
|
<note>You can modify the kernel source if you want to help
|
||||||
with boot time.
|
with boot time.
|
||||||
|
@ -2737,7 +2737,7 @@
|
||||||
will be smaller by a relatively constant factor in a compressed
|
will be smaller by a relatively constant factor in a compressed
|
||||||
kernel image.
|
kernel image.
|
||||||
Look to reduce the areas that are large and taking up around
|
Look to reduce the areas that are large and taking up around
|
||||||
the "90% rule".
|
the "90% rule."
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
|
@ -2760,7 +2760,7 @@
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
After figuring out what to eliminate, you need to reconfigure
|
After figuring out what to eliminate, you need to reconfigure
|
||||||
kernel to reflect those changes during the next build.
|
the kernel to reflect those changes during the next build.
|
||||||
You could run <filename>menuconfig</filename> and make all your
|
You could run <filename>menuconfig</filename> and make all your
|
||||||
changes at once.
|
changes at once.
|
||||||
However, that makes it difficult to see the effects of your
|
However, that makes it difficult to see the effects of your
|
||||||
|
@ -2772,7 +2772,7 @@
|
||||||
fragments into a single configuration file using
|
fragments into a single configuration file using
|
||||||
<filename>merge_config.sh</filename>.
|
<filename>merge_config.sh</filename>.
|
||||||
The tool makes it easy for you to iterate using the
|
The tool makes it easy for you to iterate using the
|
||||||
configuration change/build cycle.
|
configuration change and build cycle.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
|
|
|
@ -314,8 +314,7 @@
|
||||||
<link linkend='var-MACHINEOVERRIDES'><filename>MACHINEOVERRIDES</filename></link>
|
<link linkend='var-MACHINEOVERRIDES'><filename>MACHINEOVERRIDES</filename></link>
|
||||||
or <link linkend='var-DISTROOVERRIDES'><filename>DISTROOVERRIDES</filename></link>
|
or <link linkend='var-DISTROOVERRIDES'><filename>DISTROOVERRIDES</filename></link>
|
||||||
variables, as appropriate.
|
variables, as appropriate.
|
||||||
For more changes regarding the
|
For more related changes, see the
|
||||||
<filename>SRC_URI</filename> variable, see the
|
|
||||||
"<link linkend='migration-1.4-variables'>Variables</link>"
|
"<link linkend='migration-1.4-variables'>Variables</link>"
|
||||||
section.
|
section.
|
||||||
</para></listitem>
|
</para></listitem>
|
||||||
|
|
Loading…
Reference in New Issue