1. 12 6月, 2015 6 次提交
  2. 31 5月, 2015 1 次提交
    • I
      bna: remove unreasonable iocpf timer start · 4918eb1e
      Ivan Vecera 提交于
      Driver starts iocpf timer prior bnad_ioceth_enable() call and this is
      unreasonable. This piece of code probably originates from Brocade/Qlogic
      out-of-box driver during initial import into upstream. This driver uses
      only one timer and queue to implement multiple timers and this timer is
      started at this place. The upstream driver uses multiple timers instead
      of this.
      
      Cc: Rasesh Mody <rasesh.mody@qlogic.com>
      Signed-off-by: NIvan Vecera <ivecera@redhat.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      4918eb1e
  3. 22 2月, 2015 1 次提交
  4. 14 1月, 2015 1 次提交
  5. 17 11月, 2014 1 次提交
  6. 18 10月, 2014 1 次提交
  7. 07 10月, 2014 1 次提交
    • I
      bna: allow transmit tagged frames · 6654cf60
      Ivan Vecera 提交于
      When Tx VLAN offloading is disabled frames with size ~ MTU are not
      transmitted as the driver does not account 4 bytes of VLAN header added
      by stack. It should use VLAN_ETH_HLEN instead of ETH_HLEN.
      
      The second problem is with newer BNA chips (BNA 1860). These chips filter
      out any VLAN tagged frames in Tx path. This is a problem when Tx VLAN
      offloading is disabled and frames are tagged by stack. Older chips like
      1010/1020 are not affected as they probably don't do such filtering.
      
      Cc: Rasesh Mody <rasesh.mody@qlogic.com>
      Signed-off-by: NIvan Vecera <ivecera@redhat.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      6654cf60
  8. 26 8月, 2014 1 次提交
    • V
      bna: Support TSO and partial checksum with non-accelerated vlans. · 1c53730a
      Vlad Yasevich 提交于
      This device claims TSO and checksum support for vlans.  It also
      allows a user to control vlan acceleration offloading.  As such,
      it is possible to turn off vlan acceleration and configure a vlan
      which will continue to support TSO.
      
      In such situation the packet passed down the the device will contain
      a vlan header and skb->protocol will be set to ETH_P_8021Q.
      The device assumes that skb->protocol contains network protocol
      value and uses that value to set up TSO information.  This results
      in corrupted frames sent on the wire.
      
      This patch extract the protocol value correctly and corrects TSO
      and checksums for non-accelerated traffic.
      
      CC: Rasesh Mody <rmody@brocade.com>
      Signed-off-by: NVladislav Yasevich <vyasevic@redhat.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      1c53730a
  9. 13 8月, 2014 1 次提交
  10. 31 7月, 2014 1 次提交
  11. 18 4月, 2014 1 次提交
  12. 30 3月, 2014 1 次提交
  13. 25 3月, 2014 1 次提交
  14. 13 3月, 2014 1 次提交
  15. 01 3月, 2014 1 次提交
  16. 19 2月, 2014 1 次提交
  17. 17 1月, 2014 1 次提交
  18. 07 1月, 2014 1 次提交
  19. 18 12月, 2013 9 次提交
  20. 10 12月, 2013 1 次提交
  21. 18 10月, 2013 1 次提交
  22. 17 9月, 2013 1 次提交
    • R
      DMA-API: net: brocade/bna/bnad.c: fix 32-bit DMA mask handling · 3e548079
      Russell King 提交于
      The fallback to 32-bit DMA mask is rather odd:
      	if (!dma_set_mask(&pdev->dev, DMA_BIT_MASK(64)) &&
      	    !dma_set_coherent_mask(&pdev->dev, DMA_BIT_MASK(64))) {
      		*using_dac = true;
      	} else {
      		err = dma_set_mask(&pdev->dev, DMA_BIT_MASK(32));
      		if (err) {
      			err = dma_set_coherent_mask(&pdev->dev,
      						    DMA_BIT_MASK(32));
      			if (err)
      				goto release_regions;
      		}
      
      This means we only try and set the coherent DMA mask if we failed to
      set a 32-bit DMA mask, and only if both fail do we fail the driver.
      Adjust this so that if either setting fails, we fail the driver - and
      thereby end up properly setting both the DMA mask and the coherent
      DMA mask in the fallback case.
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      3e548079
  23. 21 5月, 2013 1 次提交
  24. 14 5月, 2013 1 次提交
  25. 20 4月, 2013 3 次提交