Input: use svg files instead of xfig in force feedback documentation

Now that the images got converted to svg, add them at the
ff.rst file.

NOTE: After merging upstream, the "figure" tag should be
replaced by the new "kernel-figure" tag, in order for the
SVG images to be included at the PDF files.

Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>

diff --git a/Documentation/input/ff.rst b/Documentation/input/ff.rst
index 6d6688a63dd85e1398392f87c1612397bd829146..c30f185216a00d43025fc5ff4eb131ae3a7c4257 100644 (file)
--- a/Documentation/input/ff.rst
+++ b/Documentation/input/ff.rst
@@ -5,8 +5,8 @@ Force feedback for Linux
 :Author: Johann Deneux <johann.deneux@gmail.com> on 2001/04/22.
 :Updated: Anssi Hannula <anssi.hannula@gmail.com> on 2006/04/09.
 
-You may redistribute this file. Please remember to include shape.fig and
-interactive.fig as well.
+You may redistribute this file. Please remember to include shape.svg and
+interactive.svg as well.
 
 Introduction
 ~~~~~~~~~~~~
@@ -127,8 +127,15 @@ allocate a new effect.
 Effects are file descriptor specific.
 
 See <linux/input.h> for a description of the ff_effect struct. You should also
-find help in a few sketches, contained in files shape.fig and interactive.fig.
-You need xfig to visualize these files.
+find help in a few sketches, contained in files shape.svg and interactive.svg:
+
+.. figure:: shape.svg
+
+    Shape
+
+.. figure:: interactive.svg
+
+    Interactive
 
 
 Removing an effect from the device