diff options
| author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2013-04-16 09:19:57 -0700 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-04-17 22:34:16 +0100 |
| commit | ae53349aca845ca89d5d43cf00e5a2d9b708843b (patch) | |
| tree | d8e42dfb9aee69d9bc2ab18ec0fb874dee683f4b /documentation/dev-manual | |
| parent | f35f12d864203f7940ca37a2ca41d97a2fc57af1 (diff) | |
| download | ast2050-yocto-poky-ae53349aca845ca89d5d43cf00e5a2d9b708843b.zip ast2050-yocto-poky-ae53349aca845ca89d5d43cf00e5a2d9b708843b.tar.gz | |
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>
Diffstat (limited to 'documentation/dev-manual')
| -rw-r--r-- | documentation/dev-manual/dev-manual-common-tasks.xml | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index aeb8902..3eb8feb 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -2710,10 +2710,10 @@ <title>Trim the Kernel</title> <para> - Kernel is built by including policies for hardware-independent + The kernel is built by including policies for hardware-independent aspects. What subsystems do you enable? - What architecture are you building for? + For what architecture are you building? Which drivers do you build by default. <note>You can modify the kernel source if you want to help with boot time. @@ -2737,7 +2737,7 @@ will be smaller by a relatively constant factor in a compressed kernel image. Look to reduce the areas that are large and taking up around - the "90% rule". + the "90% rule." </para> <para> @@ -2760,7 +2760,7 @@ <para> 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 changes at once. However, that makes it difficult to see the effects of your @@ -2772,7 +2772,7 @@ fragments into a single configuration file using <filename>merge_config.sh</filename>. The tool makes it easy for you to iterate using the - configuration change/build cycle. + configuration change and build cycle. </para> <para> |
