X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=FAQ;h=dfe8242e0ab729f75f1895f9a1ec73d1f713fd5d;hb=5ca1ba484bd9ade5116a49cf241cb98219d7d696;hp=15fb6940bc19e03dff972256026381e302c33775;hpb=314e60e19507f12b89faaf8e605bd8e818cfe0a2;p=sliver-openvswitch.git

diff --git a/FAQ b/FAQ
index 15fb6940b..dfe8242e0 100644
--- a/FAQ
+++ b/FAQ
@@ -145,7 +145,7 @@ A: The following table lists the Linux kernel versions against which the
        1.6.x      2.6.18 to 3.2
        1.7.x      2.6.18 to 3.3
        1.8.x      2.6.18 to 3.4
-       1.9.x      2.6.18 to 3.6
+       1.9.x      2.6.18 to 3.7
 
    Open vSwitch userspace should also work with the Linux kernel module
    built into Linux 3.3 and later.
@@ -160,15 +160,6 @@ Q: What features are not available in the Open vSwitch kernel datapath
 A: The kernel module in upstream Linux 3.3 and later does not include
    the following features:
 
-       - Bridge compatibility, that is, support for the ovs-brcompatd
-         daemon that (if you enable it) lets "brctl" and other Linux
-         bridge tools transparently work with Open vSwitch instead.
-
-         We do not expect bridge compatibility to ever be available in
-         upstream Linux.  If you need bridge compatibility, use the
-         kernel module from the Open vSwitch distribution instead of the
-         upstream Linux kernel module.
-
        - Tunnel virtual ports, that is, interfaces with type "gre",
          "ipsec_gre", "capwap".  It is possible to create tunnels in
          Linux and attach them to Open vSwitch as system devices.