summaryrefslogtreecommitdiffstats
path: root/documentation/dev-manual/dev-manual-common-tasks.xml
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2013-04-16 13:02:21 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-04-17 22:34:19 +0100
commit13dcc7835f8c8ad7b314341382e358c706a1e083 (patch)
tree472113dc7de32548eb94abf1e950ac4d714ff2f5 /documentation/dev-manual/dev-manual-common-tasks.xml
parentf4e04abc786036f8b8fee545ad5b3a4590ebdc28 (diff)
downloadpoky-13dcc7835f8c8ad7b314341382e358c706a1e083.tar.gz
dev-manual: Edits to "Online Mode" section.
(From yocto-docs rev: 1d60e57cbb98b988253989b15f294ba9a8e60630) 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/dev-manual-common-tasks.xml')
-rw-r--r--documentation/dev-manual/dev-manual-common-tasks.xml10
1 files changed, 6 insertions, 4 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 96ed079a25..2655b5a04c 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -4438,7 +4438,8 @@
4438 </para> 4438 </para>
4439 4439
4440 <para> 4440 <para>
4441 Downloaded archives reside in the Build Directory in 4441 Downloaded archives reside in the
4442 <link linkend='build-directory'>Build Directory</link> in
4442 <filename>/tmp</filename> and are cleared up when they are no longer in use. 4443 <filename>/tmp</filename> and are cleared up when they are no longer in use.
4443 </para> 4444 </para>
4444 4445
@@ -4451,7 +4452,7 @@
4451 The OpenEmbedded build system generates separate <filename>vmlinux</filename> 4452 The OpenEmbedded build system generates separate <filename>vmlinux</filename>
4452 packages for each kernel it builds. 4453 packages for each kernel it builds.
4453 Thus, it should just be a question of making sure a matching package is 4454 Thus, it should just be a question of making sure a matching package is
4454 installed (e.g. <filename>opkg install kernel-vmlinux</filename>. 4455 installed (e.g. <filename>opkg install kernel-vmlinux</filename>).
4455 The files are automatically installed into development and profiling images 4456 The files are automatically installed into development and profiling images
4456 alongside OProfile. 4457 alongside OProfile.
4457 A configuration option exists within the OProfileUI settings page that you can use to 4458 A configuration option exists within the OProfileUI settings page that you can use to
@@ -4463,9 +4464,10 @@
4463 is not always necessary to actually have them on the device for OProfile use. 4464 is not always necessary to actually have them on the device for OProfile use.
4464 All that is needed is a copy of the filesystem with the debug symbols present 4465 All that is needed is a copy of the filesystem with the debug symbols present
4465 on the viewer system. 4466 on the viewer system.
4466 The "<link linkend='platdev-gdb-remotedebug-launch-gdb'>Launching GDB on the Host Computer</link>" 4467 The "<link linkend='platdev-gdb-remotedebug-launch-gdb'>Launch GDB on the Host Computer</link>"
4467 section covers how to create such a directory with 4468 section covers how to create such a directory with
4468 the source directory and how to use the OProfileUI Settings dialog to specify the location. 4469 the <link linkend='source-directory'>Source Directory</link>
4470 and how to use the OProfileUI Settings Dialog to specify the location.
4469 If you specify the directory, it will be used when the file checksums 4471 If you specify the directory, it will be used when the file checksums
4470 match those on the system you are profiling. 4472 match those on the system you are profiling.
4471 </para> 4473 </para>