summaryrefslogtreecommitdiffstats
path: root/documentation/poky-ref-manual/development.xml
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/poky-ref-manual/development.xml')
-rw-r--r--documentation/poky-ref-manual/development.xml13
1 files changed, 6 insertions, 7 deletions
diff --git a/documentation/poky-ref-manual/development.xml b/documentation/poky-ref-manual/development.xml
index 5479854d8b..45df028f86 100644
--- a/documentation/poky-ref-manual/development.xml
+++ b/documentation/poky-ref-manual/development.xml
@@ -937,8 +937,8 @@ $ opreport -cl
937 937
938 <para> 938 <para>
939 A graphical user interface for OProfile is also available. 939 A graphical user interface for OProfile is also available.
940 You can download and build it from svn at 940 You can download and build it from the Yocto Project at
941 <ulink url="http://svn.o-hand.com/repos/oprofileui/trunk/"></ulink>. 941 <ulink url="http://git.yoctoproject.org/cgit.cgi/oprofileui/"></ulink>.
942 If the "tools-profile" image feature is selected, all necessary binaries 942 If the "tools-profile" image feature is selected, all necessary binaries
943 are installed onto the target device for OProfileUI interaction. 943 are installed onto the target device for OProfileUI interaction.
944 </para> 944 </para>
@@ -954,7 +954,7 @@ $ opreport -cl
954 </caption> 954 </caption>
955 </mediaobject> 955 </mediaobject>
956 </screenshot> 956 </screenshot>
957--> 957
958 <para> 958 <para>
959 In order to convert the data in the sample format from the target 959 In order to convert the data in the sample format from the target
960 to the host you need the <filename>opimport</filename> program. 960 to the host you need the <filename>opimport</filename> program.
@@ -963,13 +963,12 @@ $ opreport -cl
963 <ulink url='http://debian.o-hand.com/'>OpenedHand repository</ulink>. 963 <ulink url='http://debian.o-hand.com/'>OpenedHand repository</ulink>.
964 We recommend using OProfile 0.9.3 or greater. 964 We recommend using OProfile 0.9.3 or greater.
965 </para> 965 </para>
966-->
966 <para> 967 <para>
967 Even though Poky usually includes all needed patches on the target device, you 968 Even though Poky usually includes all needed patches on the target device, you
968 might find you need other OProfile patches for recent OProfileUI features. 969 might find you need other OProfile patches for recent OProfileUI features.
969 If so, see the <ulink url='http://svn.o-hand.com/repos/oprofileui/trunk/README'> 970 If so, see the <ulink url='http://git.yoctoproject.org/cgit.cgi/oprofileui/tree/README'>
970 OProfileUI README</ulink> for the most recent information. 971 OProfileUI README</ulink> for the most recent information.
971 You can also see <ulink url="http://labs.o-hand.com/oprofileui">OProfileUI website
972 </ulink> for general information on the OProfileUI project.
973 </para> 972 </para>
974 973
975 <section id="platdev-oprofile-oprofileui-online"> 974 <section id="platdev-oprofile-oprofileui-online">
@@ -1066,7 +1065,7 @@ $ opreport -cl
1066 a "vmlinux" file that matches the running kernel is available. 1065 a "vmlinux" file that matches the running kernel is available.
1067 In Poky, that file is usually located in 1066 In Poky, that file is usually located in
1068 <filename>/boot/vmlinux-KERNELVERSION</filename>, where KERNEL-version is the 1067 <filename>/boot/vmlinux-KERNELVERSION</filename>, where KERNEL-version is the
1069 version of the kernel (e.g. 2.6.23). 1068 version of the kernel.
1070 Poky generates separate vmlinux packages for each kernel 1069 Poky generates separate vmlinux packages for each kernel
1071 it builds so it should be a question of just making sure a matching package is 1070 it builds so it should be a question of just making sure a matching package is
1072 installed - for example: <filename>opkg install kernel-vmlinux</filename>. 1071 installed - for example: <filename>opkg install kernel-vmlinux</filename>.