1. 28 Aug, 2016 1 commit
  2. 23 Jun, 2016 1 commit
  3. 14 Jun, 2016 1 commit
  4. 25 May, 2016 1 commit
    • Feng Tang's avatar
      net: alx: use custom skb allocator · 26c5f03b
      Feng Tang authored
      This patch follows Eric Dumazet's commit 7b701764 for Atheros
      atl1c driver to fix one exactly same bug in alx driver, that the
      network link will be lost in 1-5 minutes after the device is up.
      
      My laptop Lenovo Y580 with Atheros AR8161 ethernet device hit the
      same problem with kernel 4.4, and it will be cured by Jarod Wilson's
      commit c406700c for alx driver which get merged in 4.5. But there
      are still some alx devices can't function well even with Jarod's
      patch, while this patch could make them work fine. More details on
      	https://bugzilla.kernel.org/show_bug.cgi?id=70761
      
      The debug shows the issue is very likely to be related with the RX
      DMA address, specifically 0x...f80, if RX buffer get 0x...f80 several
      times, their will be RX overflow error and device will stop working.
      
      For kernel 4.5.0 with Jarod's patch which works fine with my
      AR8161/Lennov Y580, if I made some change to the
      	__netdev_alloc_skb
      		--> __alloc_page_frag()
      to make the allocated buffer can get an address with 0x...f80,
      then the same error happens. If I make it to 0x...f40 or 0x....fc0,
      everything will be still fine. So I tend to believe that the
      0x..f80 address cause the silicon to behave abnormally.
      
      Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=70761
      
      
      Cc: Eric Dumazet <edumazet@google.com>
      Cc: Johannes Berg <johannes@sipsolutions.net>
      Cc: Jarod Wilson <jarod@redhat.com>
      Signed-off-by: default avatarFeng Tang <feng.tang@intel.com>
      Tested-by: default avatarOle Lukoie <olelukoie@mail.ru>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      26c5f03b
  5. 04 May, 2016 1 commit
  6. 06 Jan, 2016 1 commit
    • Jarod Wilson's avatar
      ethernet/atheros/alx: sanitize buffer sizing and padding · c406700c
      Jarod Wilson authored
      This is based on the work done by Przemek Rudy in bug 70761 at
      bugzilla.kernel.org, but with some work done to disentagle and clarify
      things a bit.
      
      Similar to Przemek's work and other drivers, we're adding a padding of 16
      here, but we're also disentangling mtu size calculations from max buffer
      size calculations a bit, and adding ETH_HLEN to the value written into
      ALX_MTU. Hopefully, with a bit more consistency and clarity, things behave
      better here. Sadly, I can only test in my alx-driven E2200, which worked
      just fine before this patch.
      
      In comment #58 of bug 70761, Eugene A. Shatokhin reports that this patch
      does help considerably for a ROSA Linux user of his with an AR8162 network
      adapter when patched into a 4.1.x-based kernel, with several days of
      normal operation where wired network previously wasn't usable without
      setting MTU to 9000 as a work-around.
      
      Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=70761
      
      
      CC: "Eugene A. Shatokhin" <eugene.shatokhin@rosalab.ru>
      CC: Przemek Rudy <prudy1@o2.pl>
      CC: Jay Cliburn <jcliburn@gmail.com>
      CC: Chris Snook <chris.snook@gmail.com>
      CC: netdev@vger.kernel.org
      Signed-off-by: default avatarJarod Wilson <jarod@redhat.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      c406700c
  7. 03 Dec, 2015 1 commit
  8. 18 Nov, 2015 1 commit
    • Ben Pope's avatar
      ethernet/atheros/alx: add Killer E2400 device ID · 0208e951
      Ben Pope authored
      This patch adds the PCI device ID (0xe0a1) and alx_pci_tbl entry for the
      Killer E2400 Ethernet controller, modeled after the Killer E2200
      controller support (0xe091) already present in the alx driver.
      
      This patch was originally authored by Ben Pope, but it got held up by
      issues in the commit message, so I'm resubmitting it on his behalf.
      
      I've extensively used a kernel with this patch on a System76 serw9
      laptop and am quite confident it works well (at least on the hardware I
      have available for testing).
      
      Note that as a favor to System76, Ubuntu has been carrying this as a
      sauce patch in their 4.2 based Wily kernel, which presumably has given
      it real-world testing on other E2400 equipped hardware (I don't know of
      any Ubuntu kernel bugs filed about it):
      
      https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1498633
      
      Signed-off-by: default avatarJason Gerard DeRose <jason@system76.com>
      Signed-off-by: default avatarBen Pope <benpope81@gmail.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      0208e951
  9. 11 Jan, 2015 1 commit
  10. 12 Aug, 2014 1 commit
  11. 13 May, 2014 1 commit
  12. 26 Mar, 2014 1 commit
  13. 24 Mar, 2014 1 commit
  14. 17 Mar, 2014 1 commit
  15. 10 Feb, 2014 1 commit
  16. 11 Jan, 2014 1 commit
  17. 14 Nov, 2013 1 commit
  18. 17 Oct, 2013 1 commit
  19. 13 Sep, 2013 1 commit
  20. 11 Jul, 2013 1 commit
  21. 03 Jul, 2013 1 commit
  22. 01 Jul, 2013 1 commit
  23. 17 Jun, 2013 1 commit
    • Johannes Berg's avatar
      alx: add a simple AR816x/AR817x device driver · ab69bde6
      Johannes Berg authored
      
      
      This is a very simple driver, based on the original vendor
      driver that Qualcomm/Atheros published/submitted previously,
      but reworked to make the code saner. However, it also lost
      a number of features (TSO/GSO, VLAN acceleration and multi-
      queue support) in the process, as well as debugging support
      features I didn't have any use for. The only thing I left
      is checksum offload.
      
      More features can obviously be added, but this seemed like
      a good start for having a driver in mainline at all.
      
      Johannes Stezenbach has verified that the driver works on
      AR8161, I have a AR8171 myself. The E2200 device ID I found
      on github in somebody's repository.
      Signed-off-by: default avatarJohannes Berg <johannes@sipsolutions.net>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      ab69bde6