diff options
Diffstat (limited to 'documentation')
-rw-r--r-- | documentation/dev-manual/dev-manual-common-tasks.xml | 13 | ||||
-rw-r--r-- | documentation/ref-manual/ref-variables.xml | 3 | ||||
-rw-r--r-- | documentation/sdk-manual/sdk-intro.xml | 11 | ||||
-rw-r--r-- | documentation/sdk-manual/sdk-using.xml | 26 |
4 files changed, 7 insertions, 46 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index 5e6dafd5b6..372d7b788f 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -8179,21 +8179,20 @@ This line pulls in the listed include file that contains numerous lines of exactly that form: <literallayout class='monospaced'> + #SRCREV_pn-opkg-native ?= "${AUTOREV}" + #SRCREV_pn-opkg-sdk ?= "${AUTOREV}" + #SRCREV_pn-opkg ?= "${AUTOREV}" + #SRCREV_pn-opkg-utils-naitve ?= "${AUTOREV}" + #SRCREV_pn-opkg-utils ?= "${AUTOREV}" SRCREV_pn-gconf-dbus ?= "${AUTOREV}" SRCREV_pn-matchbox-common ?= "${AUTOREV}" SRCREV_pn-matchbox-config-gtk ?= "${AUTOREV}" SRCREV_pn-matchbox-desktop ?= "${AUTOREV}" SRCREV_pn-matchbox-keyboard ?= "${AUTOREV}" - SRCREV_pn-matchbox-panel ?= "${AUTOREV}" SRCREV_pn-matchbox-panel-2 ?= "${AUTOREV}" SRCREV_pn-matchbox-themes-extra ?= "${AUTOREV}" SRCREV_pn-matchbox-terminal ?= "${AUTOREV}" - SRCREV_pn-matchbox-wm ?= "${AUTOREV}" - SRCREV_pn-matchbox-wm-2 ?= "${AUTOREV}" - SRCREV_pn-settings-daemon ?= "${AUTOREV}" - SRCREV_pn-screenshot ?= "${AUTOREV}" - SRCREV_pn-libfakekey ?= "${AUTOREV}" - SRCREV_pn-oprofileui ?= "${AUTOREV}" + SRCREV_pn-matchbox-wm ?= "${AUTOREV}" . . . . diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml index fd15dff9a1..b26f6f73f7 100644 --- a/documentation/ref-manual/ref-variables.xml +++ b/documentation/ref-manual/ref-variables.xml @@ -3819,9 +3819,6 @@ "tools-debug" - Adds debugging tools such as gdb and strace. -"tools-profile" - Adds profiling tools such as oprofile, - exmap, lttng and valgrind (x86 only). - "tools-sdk" - Adds development tools such as gcc, make, pkgconfig and so forth. diff --git a/documentation/sdk-manual/sdk-intro.xml b/documentation/sdk-manual/sdk-intro.xml index ae27562037..88ae77831c 100644 --- a/documentation/sdk-manual/sdk-intro.xml +++ b/documentation/sdk-manual/sdk-intro.xml @@ -203,7 +203,7 @@ <para> User-space tools are available as part of the SDK development process and can be helpful. - The tools include LatencyTOP, PowerTOP, OProfile, Perf, SystemTap, + The tools include LatencyTOP, PowerTOP, Perf, SystemTap, and Lttng-ust. These tools are common development tools for the Linux platform. <itemizedlist> @@ -216,15 +216,6 @@ determine what software is using the most power. You can find out more about PowerTOP at <ulink url='https://01.org/powertop/'></ulink>.</para></listitem> - <listitem><para><emphasis>OProfile:</emphasis> A system-wide - profiler for Linux systems that is capable of profiling all - running code at low overhead. - You can find out more about OProfile at - <ulink url='http://oprofile.sourceforge.net/about/'></ulink>. - For examples on how to setup and use this tool, see the - "<ulink url='&YOCTO_DOCS_PROF_URL;#profile-manual-oprofile'>OProfile</ulink>" - section in the Yocto Project Profiling and Tracing Manual. - </para></listitem> <listitem><para><emphasis>Perf:</emphasis> Performance counters for Linux used to keep track of certain types of hardware and software events. diff --git a/documentation/sdk-manual/sdk-using.xml b/documentation/sdk-manual/sdk-using.xml index 9a942d1c1c..618e57030f 100644 --- a/documentation/sdk-manual/sdk-using.xml +++ b/documentation/sdk-manual/sdk-using.xml @@ -1341,32 +1341,6 @@ <para> Here are some specifics about the remote tools: <itemizedlist> - <listitem><para><emphasis><filename>OProfile</filename>:</emphasis> - Selecting this tool causes the - <filename>oprofile-server</filename> on the remote - target to launch on the local host machine. - The <filename>oprofile-viewer</filename> must be - installed on the local host machine and the - <filename>oprofile-server</filename> must be installed - on the remote target, respectively, in order to use. - You must compile and install the - <filename>oprofile-viewer</filename> from the source - code on your local host machine. - Furthermore, in order to convert the target's sample - format data into a form that the host can use, you must - have OProfile version 0.9.4 or greater installed on the - host.</para> - <para>You can locate both the viewer and server from - <ulink url='&YOCTO_GIT_URL;/cgit/cgit.cgi/oprofileui/'></ulink>. - You can also find more information on setting up and - using this tool in the - "<ulink url='&YOCTO_DOCS_PROF_URL;#profile-manual-oprofile'>oprofile</ulink>" - section of the Yocto Project Profiling and Tracing - Manual. - <note>The <filename>oprofile-server</filename> is - installed by default on the - <filename>core-image-sato-sdk</filename> image.</note> - </para></listitem> <listitem><para><emphasis><filename>Lttng2.0 trace import</filename>:</emphasis> Selecting this tool transfers the remote target's <filename>Lttng</filename> tracing data back to the |