X-Git-Url: http://git.liburcu.org/?a=blobdiff_plain;f=README;h=1bcd5b2d69bd9109bdb38236063470294b3f3d7d;hb=a828b9d550419db8ff9594e3a983b541521739ed;hp=30f13386b9876bfde603e805bb0352bc33f2b3ba;hpb=1110c703b8c463c410b0695d0818429e7f686061;p=lttng-modules.git

diff --git a/README b/README
index 30f13386..1bcd5b2d 100644
--- a/README
+++ b/README
@@ -38,15 +38,16 @@ http://lttng.org/lttng2.0
 
 So far, it has been tested on vanilla Linux kernels 2.6.38, 2.6.39, 3.0,
 3.1, 3.2, 3.3 (on x86 32/64-bit, and powerpc 32-bit at the moment, build
-tested on ARM). It should work fine with newer kernels and other
-architectures, but expect build issues with kernels older than 2.6.36.
-The clock source currently used is the standard gettimeofday (slower,
-less scalable and less precise than the LTTng 0.x clocks).  Support for
-LTTng 0.x clocks will be added back soon into LTTng 2.0.  Please note
-that lttng-modules 2.0 can build on a Linux kernel patched with the
-LTTng 0.x patchset, but the lttng-modules 2.0 replace the lttng-modules
-0.x, so both tracers cannot be installed at the same time for a given
-kernel version.
+tested on ARM). Kernels 2.6.32 to 2.6.34 need up to 3 patches applied
+(refer to linux-patches within the lttng-modules tree). It should work
+fine with newer kernels and other architectures, but expect build issues
+with kernels older than 2.6.36.  The clock source currently used is the
+standard gettimeofday (slower, less scalable and less precise than the
+LTTng 0.x clocks).  Support for LTTng 0.x clocks will be added back soon
+into LTTng 2.0.  Please note that lttng-modules 2.0 can build on a Linux
+kernel patched with the LTTng 0.x patchset, but the lttng-modules 2.0
+replace the lttng-modules 0.x, so both tracers cannot be installed at
+the same time for a given kernel version.
 
 
 * Kernel config options required