1. 03 12月, 2014 1 次提交
  2. 30 11月, 2014 2 次提交
  3. 27 11月, 2014 11 次提交
  4. 26 11月, 2014 6 次提交
  5. 25 11月, 2014 5 次提交
    • G
      net/smsc911x: Add minimal runtime PM support · 3a611e26
      Geert Uytterhoeven 提交于
      Add minimal runtime PM support (enable on probe, disable on remove), to
      ensure proper operation with a parent device that uses runtime PM.
      
      This is needed on systems where the external bus controller module of
      the SoC is contained in a PM domain and/or has a gateable functional
      clock. In such cases, before accessing any device connected to the
      external bus, the PM domain must be powered up, and/or the functional
      clock must be enabled, which is typically handled through runtime PM by
      the bus controller driver.
      
      An example of this is the kzm9g development board, where an smsc9220
      Ethernet controller is connected to the Bus State Controller (BSC) of a
      Renesas sh73a0 SoC.
      Signed-off-by: NGeert Uytterhoeven <geert+renesas@glider.be>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      3a611e26
    • A
      xen-netback: do not report success if backend_create_xenvif() fails · 2dd34339
      Alexey Khoroshilov 提交于
      If xenvif_alloc() or xenbus_scanf() fail in backend_create_xenvif(),
      xenbus is left in offline mode but netback_probe() reports success.
      
      The patch implements propagation of error code for backend_create_xenvif().
      
      Found by Linux Driver Verification project (linuxtesting.org).
      Signed-off-by: NAlexey Khoroshilov <khoroshilov@ispras.ru>
      Acked-by: NWei Liu <wei.liu2@citrix.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      2dd34339
    • M
      ipvlan: Initial check-in of the IPVLAN driver. · 2ad7bf36
      Mahesh Bandewar 提交于
      This driver is very similar to the macvlan driver except that it
      uses L3 on the frame to determine the logical interface while
      functioning as packet dispatcher. It inherits L2 of the master
      device hence the packets on wire will have the same L2 for all
      the packets originating from all virtual devices off of the same
      master device.
      
      This driver was developed keeping the namespace use-case in
      mind. Hence most of the examples given here take that as the
      base setup where main-device belongs to the default-ns and
      virtual devices are assigned to the additional namespaces.
      
      The device operates in two different modes and the difference
      in these two modes in primarily in the TX side.
      
      (a) L2 mode : In this mode, the device behaves as a L2 device.
      TX processing upto L2 happens on the stack of the virtual device
      associated with (namespace). Packets are switched after that
      into the main device (default-ns) and queued for xmit.
      
      RX processing is simple and all multicast, broadcast (if
      applicable), and unicast belonging to the address(es) are
      delivered to the virtual devices.
      
      (b) L3 mode : In this mode, the device behaves like a L3 device.
      TX processing upto L3 happens on the stack of the virtual device
      associated with (namespace). Packets are switched to the
      main-device (default-ns) for the L2 processing. Hence the routing
      table of the default-ns will be used in this mode.
      
      RX processins is somewhat similar to the L2 mode except that in
      this mode only Unicast packets are delivered to the virtual device
      while main-dev will handle all other packets.
      
      The devices can be added using the "ip" command from the iproute2
      package -
      
      	ip link add link <master> <virtual> type ipvlan mode [ l2 | l3 ]
      Signed-off-by: NMahesh Bandewar <maheshb@google.com>
      Cc: Eric Dumazet <edumazet@google.com>
      Cc: Maciej Żenczykowski <maze@google.com>
      Cc: Laurent Chavey <chavey@google.com>
      Cc: Tim Hockin <thockin@google.com>
      Cc: Brandon Philips <brandon.philips@coreos.com>
      Cc: Pavel Emelianov <xemul@parallels.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      2ad7bf36
    • A
      8139too: The maximum MTU should allow for VLAN headers · 2bbea0a8
      Alban Bedel 提交于
      As pointed out by Ben Hutchings drivers that allow using VLAN have to
      provide enough headroom for the VLAN tags.
      Signed-off-by: NAlban Bedel <albeu@free.fr>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      2bbea0a8
    • N
      net: fec: init maximum receive buffer size for ring1 and ring2 · d543a762
      Nimrod Andy 提交于
      i.MX6SX fec support three rx ring1, the current driver lost to init
      ring1 and ring2 maximum receive buffer size, that cause receving
      frame date length error. The driver reports "rcv is not +last" error
      log in user case.
      Signed-off-by: NFugang Duan <B38611@freescale.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      d543a762
  6. 24 11月, 2014 12 次提交
  7. 23 11月, 2014 3 次提交