X-Git-Url: https://review.openocd.org/gitweb?a=blobdiff_plain;f=README;h=e3b49a93a65f51b69d20bb79f7890ab9d8588748;hb=b747da266344ae9f17b5e27a38bbe51e28f00e7a;hp=34f790746a1151984bc84337d7e8e5f499a386d0;hpb=ff5170a979221ed5c3962c716f63a5ef3c83d9d5;p=openocd.git

diff --git a/README b/README
index 34f790746a..e3b49a93a6 100644
--- a/README
+++ b/README
@@ -64,6 +64,12 @@ you can build the in-tree documentation.
 Installing OpenOCD
 ==================
 
+On Linux, you may have permissions problems to address.  The best
+way to do this is to use the contrib/udev.rules file.  It probably
+belongs somewhere in /etc/udev/rules.d, but consult your operating
+system documentation to be sure.  In particular, make sure that it
+matches the syntax used by your operating system's version of udev.
+
 A Note to OpenOCD Users
 -----------------------
 
@@ -325,7 +331,7 @@ Then type ``make'', and perhaps ``make install''.
 Using FTDI's FTD2XX
 -------------------
 
-Some claim the (closed) FTDICHIP.COM solution is faster, which
+The (closed source) FTDICHIP.COM solution is faster on MS-Windows.  That
 is the motivation for supporting it even though its licensing restricts
 it to non-redistributable OpenOCD binaries, and it is not available for
 all operating systems used with OpenOCD.  You may, however, build such
@@ -370,6 +376,9 @@ the following:
         --with-ft2xx-linux-tardir=../libftd2xx0.4.16 \
 	... other options ...
 
+Note that on Linux there is no good reason to use these FTDI binaries;
+they are no faster (on Linux) than libftdi, and cause licensing issues.
+
 =================================
 Obtaining OpenOCD From Subversion
 ---------------------------------