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. 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
      driver.
      
      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>
      fe1a5642
  6. 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).
      
      6c541b45
      
       ("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>
      d39db3b4
  7. 05 Jul, 2018 2 commits
  8. 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>
      a556c76a
  9. 29 Mar, 2018 1 commit
  10. 26 Mar, 2018 2 commits
  11. 15 Jan, 2018 1 commit
  12. 28 Dec, 2017 1 commit
  13. 02 Nov, 2017 1 commit
    • Greg Kroah-Hartman's avatar
      License cleanup: add SPDX GPL-2.0 license identifier to files with no license · b2441318
      Greg Kroah-Hartman authored
      
      
      Many source files in the tree are missing licensing information, which
      makes it harder for compliance tools to determine the correct license.
      
      By default all files without license information are under the default
      license of the kernel, which is GPL version 2.
      
      Update the files which contain no license information with the 'GPL-2.0'
      SPDX license identifier.  The SPDX identifier is a legally binding
      shorthand, which can be used instead of the full boiler plate text.
      
      This patch is based on work done by Thomas Gleixner and Kate Stewart and
      Philippe Ombredanne.
      
      How this work was done:
      
      Patches were generated and checked against linux-4.14-rc6 for a subset of
      the use cases:
       - file had no licensing information it it.
       - file was a */uapi/* one with no licensing information in it,
       - file was a */uapi/* one with existing licensing information,
      
      Further patches will be generated in subsequent months to fix up cases
      where non-standard license headers were used, and references to license
      had to be inferred by heuristics based on keywords.
      
      The analysis to determine which SPDX License Identifier to be applied to
      a file was done in a spreadsheet of side by side results from of the
      output of two independent scanners (ScanCode & Windriver) producing SPDX
      tag:value files created by Philippe Ombredanne.  Philippe prepared the
      base worksheet, and did an initial spot review of a few 1000 files.
      
      The 4.13 kernel was the starting point of the analysis with 60,537 files
      assessed.  Kate Stewart did a file by file comparison of the scanner
      results in the spreadsheet to determine which SPDX license identifier(s)
      to be applied to the file. She confirmed any determination that was not
      immediately clear with lawyers working with the Linux Foundation.
      
      Criteria used to select files for SPDX license identifier tagging was:
       - Files considered eligible had to be source code files.
       - Make and config files were included as candidates if they contained >5
         lines of source
       - File already had some variant of a license header in it (even if <5
         lines).
      
      All documentation files were explicitly excluded.
      
      The following heuristics were used to determine which SPDX license
      identifiers to apply.
      
       - when both scanners couldn't find any license traces, file was
         considered to have no license information in it, and the top level
         COPYING file license applied.
      
         For non */uapi/* files that summary was:
      
         SPDX license identifier                            # files
         ---------------------------------------------------|-------
         GPL-2.0                                              11139
      
         and resulted in the first patch in this series.
      
         If that file was a */uapi/* path one, it was "GPL-2.0 WITH
         Linux-syscall-note" otherwise it was "GPL-2.0".  Results of that was:
      
         SPDX license identifier                            # files
         ---------------------------------------------------|-------
         GPL-2.0 WITH Linux-syscall-note                        930
      
         and resulted in the second patch in this series.
      
       - if a file had some form of licensing information in it, and was one
         of the */uapi/* ones, it was denoted with the Linux-syscall-note if
         any GPL family license was found in the file or had no licensing in
         it (per prior point).  Results summary:
      
         SPDX license identifier                            # files
         ---------------------------------------------------|------
         GPL-2.0 WITH Linux-syscall-note                       270
         GPL-2.0+ WITH Linux-syscall-note                      169
         ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause)    21
         ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)    17
         LGPL-2.1+ WITH Linux-syscall-note                      15
         GPL-1.0+ WITH Linux-syscall-note                       14
         ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause)    5
         LGPL-2.0+ WITH Linux-syscall-note                       4
         LGPL-2.1 WITH Linux-syscall-note                        3
         ((GPL-2.0 WITH Linux-syscall-note) OR MIT)              3
         ((GPL-2.0 WITH Linux-syscall-note) AND MIT)             1
      
         and that resulted in the third patch in this series.
      
       - when the two scanners agreed on the detected license(s), that became
         the concluded license(s).
      
       - when there was disagreement between the two scanners (one detected a
         license but the other didn't, or they both detected different
         licenses) a manual inspection of the file occurred.
      
       - In most cases a manual inspection of the information in the file
         resulted in a clear resolution of the license that should apply (and
         which scanner probably needed to revisit its heuristics).
      
       - When it was not immediately clear, the license identifier was
         confirmed with lawyers working with the Linux Foundation.
      
       - If there was any question as to the appropriate license identifier,
         the file was flagged for further research and to be revisited later
         in time.
      
      In total, over 70 hours of logged manual review was done on the
      spreadsheet to determine the SPDX license identifiers to apply to the
      source files by Kate, Philippe, Thomas and, in some cases, confirmation
      by lawyers working with the Linux Foundation.
      
      Kate also obtained a third independent scan of the 4.13 code base from
      FOSSology, and compared selected files where the other two scanners
      disagreed against that SPDX file, to see if there was new insights.  The
      Windriver scanner is based on an older version of FOSSology in part, so
      they are related.
      
      Thomas did random spot checks in about 500 files from the spreadsheets
      for the uapi headers and agreed with SPDX license identifier in the
      files he inspected. For the non-uapi files Thomas did random spot checks
      in about 15000 files.
      
      In initial set of patches against 4.14-rc6, 3 files were found to have
      copy/paste license identifier errors, and have been fixed to reflect the
      correct identifier.
      
      Additionally Philippe spent 10 hours this week doing a detailed manual
      inspection and review of the 12,461 patched files from the initial patch
      version early this week with:
       - a full scancode scan run, collecting the matched texts, detected
         license ids and scores
       - reviewing anything where there was a license detected (about 500+
         files) to ensure that the applied SPDX license was correct
       - reviewing anything where there was no detection but the patch license
         was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied
         SPDX license was correct
      
      This produced a worksheet with 20 files needing minor correction.  This
      worksheet was then exported into 3 different .csv files for the
      different types of files to be modified.
      
      These .csv files were then reviewed by Greg.  Thomas wrote a script to
      parse the csv files and add the proper SPDX tag to the file, in the
      format that the file expected.  This script was further refined by Greg
      based on the output to detect more types of files automatically and to
      distinguish between header and source .c files (which need different
      comment types.)  Finally Greg ran the script using the .csv files to
      generate the patches.
      Reviewed-by: default avatarKate Stewart <kstewart@linuxfoundation.org>
      Reviewed-by: default avatarPhilippe Ombredanne <pombredanne@nexb.com>
      Reviewed-by: default avatarThomas Gleixner <tglx@linutronix.de>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      b2441318
  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. 06 Dec, 2016 1 commit
  19. 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>
      5a6681e2
  20. 13 Aug, 2016 1 commit
  21. 18 Mar, 2016 1 commit
  22. 10 Mar, 2016 1 commit
  23. 03 Dec, 2015 1 commit
  24. 20 Nov, 2015 1 commit
  25. 16 Nov, 2015 1 commit
  26. 25 Aug, 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
      4006e565
      
      . 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>
      f3ba9d49
  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 1 commit
  36. 09 May, 2014 1 commit
  37. 26 Mar, 2014 1 commit
  38. 18 Mar, 2014 1 commit