1. 22 Sep, 2019 1 commit
  2. 05 Sep, 2019 1 commit
  3. 04 Sep, 2019 1 commit
  4. 02 Jul, 2019 1 commit
  5. 21 May, 2019 1 commit
  6. 13 Sep, 2018 1 commit
    • Hauke Mehrtens's avatar
      net: lantiq: Add Lantiq / Intel VRX200 Ethernet driver · fe1a5642
      Hauke Mehrtens authored
      This drives the PMAC between the GSWIP Switch and the CPU in the VRX200
      SoC. This is currently only the very basic version of the Ethernet
      When the DMA channel is activated we receive some packets which were
      send to the SoC while it was still in U-Boot, these packets have the
      wrong header. Resetting the IP cores did not work so we read out the
      extra packets at the beginning and discard them.
      This also adapts the clock code in sysctrl.c to use the default name of
      the device node so that the driver gets the correct clock. sysctrl.c
      should be replaced with a proper common clock driver later.
      Signed-off-by: default avatarHauke Mehrtens <hauke@hauke-m.de>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
  7. 01 Aug, 2018 1 commit
    • Jon Mason's avatar
      net: change Exar/Neterion menu items to be alphabetical · d39db3b4
      Jon Mason authored
      Neterion was standalone for several years, then acquired by Exar and
      shutdown in 11 months without ever making any new Exar branded adapters.
      Users would probably think of them as Neterion and not Exar (as there
      have been no follow-on adapters and the vast majority ever sold were
      under the Neterion name).
       ("net: ethernet: Sort Kconfig sourcing alphabetically")
      sorted Kconfig sourcing based on directory names, but in a couple cases,
      the menu item text is quite different from the directory name and is not
      sorted correctly:
        drivers/net/ethernet/neterion/Kconfig    => "Exar devices"
      To address that and clear up any confusion about the name, "Exar" was
      changed to "Neterion (Exar)" and the relevant entries in the Makefile
      and Kconfig were reordered to match the alphabetical organization.
      Inspired-by: default avatarBjorn Helgaas <bhelgaas@google.com>
      Signed-off-by: default avatarJon Mason <jdmason@kudzu.us>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
  8. 21 May, 2018 1 commit
  9. 15 May, 2018 1 commit
    • Alexandre Belloni's avatar
      net: mscc: Add initial Ocelot switch support · a556c76a
      Alexandre Belloni authored
      Add a driver for Microsemi Ocelot Ethernet switch support.
      This makes two modules:
      mscc_ocelot_common handles all the common features that doesn't depend on
      how the switch is integrated in the SoC. Currently, it handles offloading
      bridging to the hardware. ocelot_io.c handles register accesses. This is
      unfortunately needed because the register layout is packed and then depends
      on the number of ports available on the switch. The register definition
      files are automatically generated.
      ocelot_board handles the switch integration on the SoC and on the board.
      Frame injection and extraction to/from the CPU port is currently done using
      register accesses which is quite slow. DMA is possible but the port is not
      able to absorb the whole switch bandwidth.
      Signed-off-by: default avatarAlexandre Belloni <alexandre.belloni@bootlin.com>
      Reviewed-by: default avatarAndrew Lunn <andrew@lunn.ch>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
  10. 29 Mar, 2018 1 commit
  11. 26 Mar, 2018 2 commits
  12. 15 Jan, 2018 1 commit
  13. 28 Dec, 2017 1 commit
  14. 22 Aug, 2017 1 commit
  15. 09 Mar, 2017 1 commit
  16. 24 Jan, 2017 1 commit
  17. 16 Jan, 2017 1 commit
  18. 20 Dec, 2016 1 commit
  19. 06 Dec, 2016 1 commit
  20. 30 Nov, 2016 1 commit
    • Edward Cree's avatar
      sfc: separate out SFC4000 ("Falcon") support into new sfc-falcon driver · 5a6681e2
      Edward Cree authored
      Rationale: The differences between Falcon and Siena are in many ways larger
       than those between Siena and EF10 (despite Siena being nominally "Falcon-
       architecture"); for instance, Falcon has no MCPU, so there is no MCDI.
       Removing Falcon support from the sfc driver should simplify the latter,
       and avoid the possibility of Falcon support being broken by changes to sfc
       (which are rarely if ever tested on Falcon, it being end-of-lifed hardware).
      The sfc-falcon driver created in this changeset is essentially a copy of the
       sfc driver, but with Siena- and EF10-specific code, including MCDI, removed
       and with the "efx_" identifier prefix changed to "ef4_" (for "EFX 4000-
       series") to avoid collisions when both drivers are built-in.
      This changeset removes Falcon from the sfc driver's PCI ID table; then in
       sfc I've removed obvious Falcon-related code: I removed the Falcon NIC
       functions, Falcon PHY code, and EFX_REV_FALCON_*, then fixed up everything
       that referenced them.
      Also, increment minor version of both drivers (to 4.1).
      For now, CONFIG_SFC selects CONFIG_SFC_FALCON, so that updating old configs
       doesn't cause Falcon support to disappear; but that should be undone at
       some point in the future.
      Signed-off-by: default avatarEdward Cree <ecree@solarflare.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
  21. 13 Aug, 2016 1 commit
  22. 18 Mar, 2016 1 commit
  23. 10 Mar, 2016 1 commit
  24. 03 Dec, 2015 1 commit
  25. 20 Nov, 2015 1 commit
  26. 16 Nov, 2015 1 commit
  27. 29 Jul, 2015 1 commit
  28. 23 Jun, 2015 1 commit
  29. 27 May, 2015 1 commit
  30. 22 Dec, 2014 1 commit
    • Daniel Glöckner's avatar
      net: s6gmac: remove driver · f3ba9d49
      Daniel Glöckner authored
      The s6000 Xtensa support has been removed from the kernel in
      . There are no other chips using this driver.
      While the Mentor/Alcatel PE-MCXMAC IP core is also used in other
      designs (Freescale Gianfar/UCC, QLogic NetXen, Solarflare, Agere
      ET-1310, Netlogic XLR/XLS), none of these use this driver as it
      heavily depends on the s6000 DMA engine. In fact, there is no
      code sharing across any of the aforementioned devices.
      Signed-off-by: default avatarDaniel Glöckner <dg@emlix.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
  31. 03 Dec, 2014 1 commit
  32. 03 Oct, 2014 1 commit
  33. 29 Sep, 2014 1 commit
  34. 11 Aug, 2014 1 commit
  35. 03 Jun, 2014 2 commits
  36. 09 May, 2014 1 commit
  37. 26 Mar, 2014 1 commit
  38. 18 Mar, 2014 1 commit