X-Git-Url: http://git.liburcu.org/?a=blobdiff_plain;f=trunk%2Flttv%2FQUICKSTART.html;h=bbde9ecfd9cc6bf23a2b93928f4d5060a1336602;hb=196f71c403099b015052b9b1bc2ee6a0eb382f81;hp=8678c6d91ca77d87f5238dac15c8c50ab34d3861;hpb=1aeeacdba90c3a79df5b39423c2826e7b9565f36;p=lttv.git

diff --git a/trunk/lttv/QUICKSTART.html b/trunk/lttv/QUICKSTART.html
index 8678c6d9..bbde9ecf 100644
--- a/trunk/lttv/QUICKSTART.html
+++ b/trunk/lttv/QUICKSTART.html
@@ -82,7 +82,12 @@ To see the list of compatibilities between LTTng, ltt-control, LTTV, please
 refer to :
 <a
 href="http://ltt.polymtl.ca/svn/trunk/lttv/doc/developer/lttng-lttv-compatibility.html">LTTng+LTTV versions compatibility</a>
-The lttng patch is necessary to have the tracing hooks in the kernel.
+
+The ongoing work had the Linux Kernel Markers integrated in the mainline Linux
+kernel since Linux 2.6.24 and the Tracepoints since 2.6.28. In its current
+state, the lttng patchset is necessary to have the trace clocksource, the
+instrumentation and the LTTng high-speed data extraction mechanism added to the
+kernel.
 
 <br>
 <br>
@@ -430,7 +435,7 @@ see lttctl --help for details.
 </PRE>
 <p>
 (note : to see if the buffers has been filled, look at the dmesg output after
-lttctl -R or after stopping tracing from the GUI, it will show an event lost
+lttctl -D or after stopping tracing from the GUI, it will show an event lost
 count. If it is the case, try using larger buffers. See lttctl --help to learn 
 how. lttv now also shows event lost messages in the console when loading a trace
 with missing events or lost subbuffers.)