Changes in Makefile

657bc1d1 - r8153_ecm: avoid to be prior to r8152 driver

Wed, 18 Nov 2020 06:43:58 +0000

r8153_ecm: avoid to be prior to r8152 driverAvoid r8153_ecm is compiled as built-in, if r8152 driver is compiledas modules. Otherwise, the r8153_ecm would be used, even though thedevice is supported by r8152 driver.Fixes: c1aedf015ebd ("net/usb/r8153_ecm: support ECM mode for RTL8153")Reported-by: Marek Szyprowski Signed-off-by: Hayes Wang Tested-by: Marek Szyprowski Link: https://lore.kernel.org/r/1394712342-15778-394-Taiwan-albertk@realtek.comSigned-off-by: Jakub Kicinski List of files: /linux-6.15/drivers/net/usb/Makefile

c1aedf01 - net/usb/r8153_ecm: support ECM mode for RTL8153

Wed, 04 Nov 2020 02:19:22 +0000

net/usb/r8153_ecm: support ECM mode for RTL8153Support ECM mode based on cdc_ether with relative mii functions,when CONFIG_USB_RTL8152 is not set, or the device is not supportedby r8152 driver.Both r8152 and r8153_ecm would check the return value ofrtl8152_get_version() in porbe(). If rtl8152_get_version()return none zero value, the r8152 is used for the devicewith vendor mode. Otherwise, the r8153_ecm is used for thedevice with ECM mode.Signed-off-by: Hayes Wang Link: https://lore.kernel.org/r/1394712342-15778-392-Taiwan-albertk@realtek.comSigned-off-by: Jakub Kicinski List of files: /linux-6.15/drivers/net/usb/Makefile

17364b80 - net: usb: aqc111: Driver skeleton for Aquantia AQtion USB to 5GbE

Mon, 26 Nov 2018 09:32:59 +0000

net: usb: aqc111: Driver skeleton for Aquantia AQtion USB to 5GbEInitialize usb_driver structure skeletonSigned-off-by: Dmitry Bezrukov Signed-off-by: Igor Russkikh Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/usb/Makefile

b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license

Wed, 01 Nov 2017 14:07:57 +0000

License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense 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 bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe 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 caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode & Windriver) producing SPDXtag:value files created by Philippe Ombredanne. Philippe prepared thebase 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 filesassessed. Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately 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 licenseidentifiers 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 thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights. TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion 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 correctThis produced a worksheet with 20 files needing minor correction. Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg. Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected. This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.) Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart Reviewed-by: Philippe Ombredanne Reviewed-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/net/usb/Makefile

f3bb2376 - USB: cdc_subset: only build when one driver is enabled

Wed, 17 Feb 2016 22:25:11 +0000

USB: cdc_subset: only build when one driver is enabledThis avoids a harmless randconfig warning I get when USB_NET_CDC_SUBSETis enabled, but all of the more specific drivers are not:drivers/net/usb/cdc_subset.c:241:2: #warning You need to configure some hardware for this driverThe current behavior is clearly intentional, giving a warning whena user picks a configuration that won't do anything good. The onlyreason for even addressing this is that I'm getting close toeliminating all 'randconfig' warnings on ARM, and this came upa couple of times.My workaround is to not even build the module when none of theconfigurations are enable.Alternatively we could simply remove the #warning (nothing wrongfor compile-testing), turn it into a runtime warning, orchange the Kconfig options into a menu to hide CONFIG_USB_NET_CDC_SUBSET.Signed-off-by: Arnd Bergmann Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/usb/Makefile

4a476bd6 - usbnet: New driver for QinHeng CH9200 devices

Sun, 20 Sep 2015 09:25:38 +0000

usbnet: New driver for QinHeng CH9200 devicesThere's a bunch of cheap USB 10/100 devices based on QinHeng chipsets. Thevendor driver supports the CH9100 and CH9200 devices, but the majority ofthe code is of the if (ch9100) {} else {} form, with the most significantdifference being that CH9200 provides a real MII interface but CH9100 fakesone with a bunch of global variables and magic commands. I don't have aCH9100, so it's probably better if someone who does provides an independentdriver for it. In any case, this is a lightly cleaned up version of thevendor driver with all the CH9100 code dropped.Signed-off-by: Matthew Garrett Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/usb/Makefile

55d7de9d - Microchip's LAN7800 family USB 2/3 to 10/100/1000 Ethernet device driver

Thu, 30 Jul 2015 19:45:21 +0000

Microchip's LAN7800 family USB 2/3 to 10/100/1000 Ethernet device driverRepost patch of driver for LAN7800 family of USB 2.0 & USB 3.0 to Gigabit Ethernet.- remove module param which can be configurable by standard mechanism.- remove other module parms except msg_level per review comment.- update to handle byte swap for statistics structure correctly.Signed-off-by: Woojung Huh Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/usb/Makefile

10c32717 - r8152: disable the ECM mode

Tue, 04 Mar 2014 12:47:48 +0000

r8152: disable the ECM modeThere are known issues for switching the drivers between ECM mode andvendor mode. The interrup transfer may become abnormal. The hardwaremay have the opportunity to die if you change the configuration withoutunloading the current driver first, because all the control transfersof the current driver would fail after the command of switching theconfiguration.Although to use the ecm driver and vendor driver independently is fine,it may have problems to change the driver from one to the other byswitching the configuration. Additionally, now the vendor mode driveris more powerful than the ECM driver. Thus, disable the ECM mode driver,and let r8152 to set the configuration to vendor mode and reset thedevice automatically.Signed-off-by: Hayes Wang Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/usb/Makefile

19a38d8e - USB2NET : SR9800 : One chip USB2.0 USB2NET SR9800 Device Driver Support

Mon, 10 Feb 2014 06:31:42 +0000

USB2NET : SR9800 : One chip USB2.0 USB2NET SR9800 Device Driver SupportSigned-off-by: Liu Junliang Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/usb/Makefile

41c47d8c - net: huawei_cdc_ncm: Introduce the huawei_cdc_ncm driver

Mon, 04 Nov 2013 08:50:48 +0000

net: huawei_cdc_ncm: Introduce the huawei_cdc_ncm driverThis driver supports devices using the NCM protocol as an encapsulation layerfor other protocols, like the E3131 Huawei 3G modem. This drivers approach washeavily inspired by the qmi_wwan/cdc_mbim approach & code model.Signed-off-by: Enrico Mioso Signed-off-by: Bjørn Mork Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/usb/Makefile

c9b37458 - USB2NET : SR9700 : One chip USB 1.1 USB2NET SR9700Device Driver Support

Sun, 01 Sep 2013 11:38:08 +0000

USB2NET : SR9700 : One chip USB 1.1 USB2NET SR9700Device Driver SupportSigned-off-by: Liu Junliang Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/usb/Makefile

c073f666 - net/usb: add relative mii functions for r815x

Mon, 08 Jul 2013 02:41:21 +0000

net/usb: add relative mii functions for r815xBase on cdc_ether, add the mii functions for RTL8152 and RTL8153.The RTL8152 and RTL8153 support ECM mode which use the driver ofcdc_ether. Add the mii functions. Then, the basic PHY access ispossible.Signed-off-by: Hayes Wang Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/usb/Makefile

ac718b69 - net/usb: new driver for RTL8152

Thu, 02 May 2013 16:01:25 +0000

net/usb: new driver for RTL8152Add new driver for supporting Realtek RTL8152 Based USB 2.0 Ethernet AdaptersSigned-off-by: Hayes Wang Cc: Realtek linux nic maintainers Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/usb/Makefile

e2ca90c2 - ax88179_178a: ASIX AX88179_178A USB 3.0/2.0 to gigabit ethernet adapter driver

Sat, 02 Mar 2013 00:41:11 +0000

ax88179_178a: ASIX AX88179_178A USB 3.0/2.0 to gigabit ethernet adapter driverThis is a resubmission.Added kfree() in ax88179_get_eeprom to prevent memory leakage.Modified "__le16 rxctl" to "u16 rxctl" in "struct ax88179_data" and removed pointless casts.Removed asix_init and asix_exit functions and added "module_usb_driver(ax88179_178a_driver)".Fixed endianness issue on big endian systems and verified this driver on iBook G4.Removed steps that change net->features in ax88179_set_features function.Added "const" to ethtool_ops structure and fixed the coding style of AX88179_BULKIN_SIZE array.Fixed the issue that the default MTU is not 1500.Added ax88179_change_mtu function and enabled the hardware jumbo frame function to support anMTU higher than 1500.Fixed indentation and empty line coding style errors.The _nopm version usb functions were added to access register in suspend and resume functions.Serveral variables allocted dynamically were removed and replaced by stack variables.ax88179_get_eeprom were modified from asix_get_eeprom in asix_common.This patch adds a driver for ASIX's AX88179 family of USB 3.0/2.0to gigabit ethernet adapters. It's based on the AX88xxx driver butthe usb commands used to access registers for AX88179 are completely different.This driver had been verified on x86 system with AX88179/AX88178A andSitcomm LN-032 USB dongles.Signed-off-by: Freddy Xin Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/usb/Makefile

9084ccf9 - net: cdc_mbim: build the MBIM driver

Mon, 22 Oct 2012 10:56:37 +0000

net: cdc_mbim: build the MBIM driverSigned-off-by: Bjørn Mork Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/usb/Makefile

16626b0c - asix: Add a new driver for the AX88172A

Fri, 13 Jul 2012 05:26:31 +0000

asix: Add a new driver for the AX88172AThe Asix AX88172A is a USB 2.0 Ethernet interface that supports both aninternal PHY as well as an external PHY (connected via MII).This patch adds a driver for the AX88172A and provides support forboth modes and the phylib.Signed-off-by: Christian Riesch Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/usb/Makefile

607740bc - asix: Factor out common code

Fri, 13 Jul 2012 05:26:30 +0000

asix: Factor out common codeAllow the new driver for the AX88172A to share code with theexisting drivers for ASIX devices.Signed-off-by: Christian Riesch Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/usb/Makefile

b4cdae20 - asix: Rename asix.c to asix_devices.c

Fri, 13 Jul 2012 05:26:29 +0000

asix: Rename asix.c to asix_devices.cThis patch further creates two additional copies of asix.c.In another patch these copies will be used to factor outcommon code.Signed-off-by: Christian Riesch Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/usb/Makefile

423ce8ca - net: usb: qmi_wwan: New driver for Huawei QMI based WWAN devices

Thu, 19 Jan 2012 15:37:22 +0000

net: usb: qmi_wwan: New driver for Huawei QMI based WWAN devicesSome WWAN LTE/3G devices based on chipsets from Qualcomm providenear standard CDC ECM interfaces in addition to the usual serialinterfaces. The Huawei E392/E398 are examples of such devices.These typically cannot be fully configured using AT commandsover a serial interface. It is necessary to speak the proprietaryQualcomm MSM Interface (QMI) protocol to the device to enable theethernet proxy functionality.The devices embed the QMI protocol in CDC on the control interface,using standard CDC commands and notifications. The do not otherwiseuse CDC commands for the ethernet function. This driver doestherefore not need access to any other aspects of the controlinterface than the descriptors attached to it.Another driver, cdc-wdm, will provide userspace access to theQMI protocol independently of this driver. To facilitate this,this driver avoids binding to the control interface, and usesonly the associated data interface after parsing the common CDCfunctional descriptors on the control interface.You will want both the cdc-wdm and option drivers as companions tothis driver, to have full access to all interfaces and protocolsexported by the device.Signed-off-by: Bjørn Mork Signed-off-by: David S. Miller Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/net/usb/Makefile

9b28ecd6 - net: usb: qmi_wwan: New driver for Huawei QMI based WWAN devices

Thu, 19 Jan 2012 15:37:22 +0000

net: usb: qmi_wwan: New driver for Huawei QMI based WWAN devicesSome WWAN LTE/3G devices based on chipsets from Qualcomm providenear standard CDC ECM interfaces in addition to the usual serialinterfaces. The Huawei E392/E398 are examples of such devices.These typically cannot be fully configured using AT commandsover a serial interface. It is necessary to speak the proprietaryQualcomm MSM Interface (QMI) protocol to the device to enable theethernet proxy functionality.The devices embed the QMI protocol in CDC on the control interface,using standard CDC commands and notifications. The do not otherwiseuse CDC commands for the ethernet function. This driver doestherefore not need access to any other aspects of the controlinterface than the descriptors attached to it.Another driver, cdc-wdm, will provide userspace access to theQMI protocol independently of this driver. To facilitate this,this driver avoids binding to the control interface, and usesonly the associated data interface after parsing the common CDCfunctional descriptors on the control interface.You will want both the cdc-wdm and option drivers as companions tothis driver, to have full access to all interfaces and protocolsexported by the device.Signed-off-by: Bjørn Mork Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/usb/Makefile