1. 14 10月, 2007 1 次提交
  2. 11 10月, 2007 1 次提交
    • R
      mlx4_core: Fix section mismatches · 3d73c288
      Roland Dreier 提交于
          
      Commit ee49bd93 ("mlx4_core: Reset device when internal error is
      detected") introduced some section mismatch problems when
      CONFIG_HOTPLUG=n, because the error recovery code tears down and
      reinitializes the device after everything is loaded, which ends up
      calling into lots of code marked __devinit and __devexit from regular
      .text.  Fix this by getting rid of these now-incorrect section
      markers.
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      3d73c288
  3. 10 10月, 2007 5 次提交
  4. 18 7月, 2007 2 次提交
  5. 10 7月, 2007 1 次提交
  6. 03 7月, 2007 1 次提交
  7. 18 6月, 2007 1 次提交
    • R
      IB/mlx4: Handle FW command interface rev 3 · 5ae2a7a8
      Roland Dreier 提交于
      Upcoming firmware introduces command interface revision 3, which
      changes the way port capabilities are queried and set.  Update the
      driver to handle both the new and old command interfaces by adding a
      new MLX4_FLAG_OLD_PORT_CMDS that it is set after querying the firmware
      interface revision and then using the correct interface based on the
      setting of the flag.
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      5ae2a7a8
  8. 08 6月, 2007 1 次提交
    • R
      mlx4_core: Initialize ctx_list and ctx_lock earlier · b581401e
      Roland Dreier 提交于
      We may call mlx4_dispatch_event() before mlx4_register_device() is
      called for a device, because for example a catastrophic error happens
      immediately after we enable interrupts.  Therefore priv->ctx_list and
      priv->ctx_lock need to be initialized earlier.
      
      This bug was actually exposed by the MSI-X bug that returned IRQ numbers 
      to drivers in reverse order, so that the first FW command 
      interrupt looked to mlx4 like a catastrophic error.
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      b581401e
  9. 13 5月, 2007 1 次提交
  10. 09 5月, 2007 1 次提交
    • R
      IB/mlx4: Add a driver Mellanox ConnectX InfiniBand adapters · 225c7b1f
      Roland Dreier 提交于
      Add an InfiniBand driver for Mellanox ConnectX adapters.  Because
      these adapters can also be used as ethernet NICs and Fibre Channel 
      HBAs, the driver is split into two modules: 
       
        mlx4_core: Handles low-level things like device initialization and 
          processing firmware commands.  Also controls resource allocation 
          so that the InfiniBand, ethernet and FC functions can share a 
          device without stepping on each other. 
       
        mlx4_ib: Handles InfiniBand-specific things; plugs into the 
          InfiniBand midlayer. 
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      225c7b1f