Changes in Makefile

3fed9fda - net: remove sb1000 cable modem driver

Wed, 12 Mar 2025 08:51:19 +0000

net: remove sb1000 cable modem driverThis one is hilariously outdated, it provided a faster downlink overTV cable for users of analog modems in the 1990s, through an ISA card.The web page for the userspace tools has been broken for 25 years, andthe driver has only ever seen mechanical updates.Link: http://web.archive.org/web/20000611165545/http://home.adelphia.net:80/~siglercm/sb1000.htmlSigned-off-by: Arnd Bergmann Reviewed-by: Simon Horman Link: https://patch.msgid.link/20250312085236.2531870-1-arnd@kernel.orgSigned-off-by: Paolo Abeni List of files: /linux-6.15/drivers/net/Makefile

b1fa60ec - net: Always descend into dsa/ folder with CONFIG_NET_DSA enabled

Thu, 16 May 2024 16:56:30 +0000

net: Always descend into dsa/ folder with CONFIG_NET_DSA enabledStephen reported that he was unable to get the dsa_loop driver to getprobed, and the reason ended up being because he had CONFIG_FIXED_PHY=yin his kernel configuration. As Masahiro explained it: "obj-m += dsa/" means everything under dsa/ must be modular. If there is a built-in object under dsa/ with CONFIG_NET_DSA=m, you cannot do "obj-$(CONFIG_NET_DSA) += dsa/". You need to change it back to "obj-y += dsa/".This was the case here whereby CONFIG_NET_DSA=m, and so theobj-$(CONFIG_FIXED_PHY) += dsa_loop_bdinfo.o rule is not executed andthe DSA loop mdio_board info structure is not registered with thekernel, and eventually the device is simply not found.To preserve the intention of the original commit of limiting the amountof folder descending, conditionally descend into drivers/net/dsa whenCONFIG_NET_DSA is enabled.Fixes: 227d72063fcc ("dsa: simplify Kconfig symbols and dependencies")Reported-by: Stephen Langstaff Signed-off-by: Florian Fainelli Reviewed-by: Vladimir Oltean Reviewed-by: Alexander Lobakin Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/Makefile

76c8764e - pfcp: add PFCP module

Wed, 27 Mar 2024 15:23:55 +0000

pfcp: add PFCP modulePacket Forwarding Control Protocol (PFCP) is a 3GPP Protocolused between the control plane and the user plane function.It is specified in TS 29.244[1].Note that this module is not designed to support this Protocolin the kernel space. There is no support for parsing any PFCP messages.There is no API that could be used by any userspace daemon.Basically it does not support PFCP. This protocol is sophisticatedand there is no need for implementing it in the kernel. The purposeof this module is to allow users to setup software and hardware offloadof PFCP packets using tc tool.When user requests to create a PFCP device, a new socket is created.The socket is set up with port number 8805 which is specific forPFCP [29.244 4.2.2]. This allow to receive PFCP request messages,response messages use other ports.Note that only one PFCP netdev can be created.Only IPv4 is supported at this time.[1] https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3111Signed-off-by: Wojciech Drewek Signed-off-by: Marcin Szycik Reviewed-by: Simon Horman Signed-off-by: Alexander Lobakin Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/Makefile

35dfaad7 - netkit, bpf: Add bpf programmable net device

Tue, 24 Oct 2023 21:48:58 +0000

netkit, bpf: Add bpf programmable net deviceThis work adds a new, minimal BPF-programmable device called "netkit"(former PoC code-name "meta") we recently presented at LSF/MM/BPF. Thecore idea is that BPF programs are executed within the drivers xmit routineand therefore e.g. in case of containers/Pods moving BPF processing closerto the source.One of the goals was that in case of Pod egress traffic, this allows tomove BPF programs from hostns tcx ingress into the device itself, providingearlier drop or forward mechanisms, for example, if the BPF programdetermines that the skb must be sent out of the node, then a redirect tothe physical device can take place directly without going through per-CPUbacklog queue. This helps to shift processing for such traffic from softirqto process context, leading to better scheduling decisions/performance (seemeasurements in the slides).In this initial version, the netkit device ships as a pair, but we plan toextend this further so it can also operate in single device mode. The paircomes with a primary and a peer device. Only the primary device, typicallyresiding in hostns, can manage BPF programs for itself and its peer. Thepeer device is designated for containers/Pods and cannot attach/detachBPF programs. Upon the device creation, the user can set the default policyto 'pass' or 'drop' for the case when no BPF program is attached.Additionally, the device can be operated in L3 (default) or L2 mode. Themanagement of BPF programs is done via bpf_mprog, so that multi-attach issupported right from the beginning with similar API and dependency controlsas tcx. For details on the latter see commit 053c8e1f235d ("bpf: Add genericattach/detach/query API for multi-progs"). tc BPF compatibility is provided,so that existing programs can be easily migrated.Going forward, we plan to use netkit devices in Cilium as the main devicetype for connecting Pods. They will be operated in L3 mode in order tosimplify a Pod's neighbor management and the peer will operate in defaultdrop mode, so that no traffic is leaving between the time when a Pod isbrought up by the CNI plugin and programs attached by the agent.Additionally, the programs we attach via tcx on the physical devices areusing bpf_redirect_peer() for inbound traffic into netkit device, hence thelatter is also supporting the ndo_get_peer_dev callback. Similarly, we usebpf_redirect_neigh() for the way out, pushing from netkit peer to phys devicedirectly. Also, BIG TCP is supported on netkit device. For the follow-upwork in single device mode, we plan to convert Cilium's cilium_host/_netdevices into a single one.An extensive test suite for checking device operations and the BPF programand link management API comes as BPF selftests in this series.Co-developed-by: Nikolay Aleksandrov Signed-off-by: Nikolay Aleksandrov Signed-off-by: Daniel Borkmann Reviewed-by: Toke Høiland-Jørgensen Acked-by: Stanislav Fomichev Acked-by: Martin KaFai Lau Link: https://github.com/borkmann/iproute2/tree/pr/netkitLink: http://vger.kernel.org/bpfconf2023_material/tcx_meta_netdev_borkmann.pdf (24ff.)Link: https://lore.kernel.org/r/20231024214904.29825-2-daniel@iogearbox.netSigned-off-by: Martin KaFai Lau List of files: /linux-6.15/drivers/net/Makefile

1dab4713 - appletalk: remove ipddp driver

Mon, 09 Oct 2023 14:10:28 +0000

appletalk: remove ipddp driverAfter the cops driver is removed, ipddp is now the onlyCONFIG_DEV_APPLETALK but as far as I can tell, this also has no usersand can be removed, making appletalk support purely based on ethertalk,using ethernet hardware.Link: https://lore.kernel.org/netdev/e490dd0c-a65d-4acf-89c6-c06cb48ec880@app.fastmail.com/Link: https://lore.kernel.org/netdev/9cac4fbd-9557-b0b8-54fa-93f0290a6fb8@schmorgal.com/Cc: Doug Brown Signed-off-by: Arnd Bergmann Acked-by: Greg Kroah-Hartman Link: https://lore.kernel.org/r/20231009141139.1766345-1-arnd@kernel.orgSigned-off-by: Jakub Kicinski List of files: /linux-6.15/drivers/net/Makefile

0d0950a9 - net: thunderbolt: Move into own directory

Wed, 11 Jan 2023 06:26:31 +0000

net: thunderbolt: Move into own directoryWe will be adding tracepoints to the driver so instead of littering themain network driver directory, move the driver into its own directory.While there, rename the module to thunderbolt_net (with underscore) tomatch with the thunderbolt_dma_test convention.Signed-off-by: Mika Westerberg Acked-by: Yehezkel Bernat Signed-off-by: Jakub Kicinski List of files: /linux-6.15/drivers/net/Makefile

3114b075 - net: add framework to support Ethernet PSE and PDs devices

Mon, 03 Oct 2022 06:51:57 +0000

net: add framework to support Ethernet PSE and PDs devicesThis framework was create with intention to provide support for Ethernet PSE(Power Sourcing Equipment) and PDs (Powered Device).At current step this patch implements generic PSE support for PoDL (Power overData Lines 802.3bu) specification with reserving name space for PD devices aswell.This framework can be extended to support 802.3af and 802.3at "Power via theMedia Dependent Interface" (or PoE/Power over Ethernet)Signed-off-by: Oleksij Rempel Reviewed-by: Andrew Lunn Signed-off-by: Jakub Kicinski List of files: /linux-6.15/drivers/net/Makefile

67653936 - vxlan: move to its own directory

Tue, 01 Mar 2022 05:04:28 +0000

vxlan: move to its own directoryvxlan.c has grown too long. This patch movesit to its own directory. subsequent patches add newfunctionality in new files.Signed-off-by: Roopa Prabhu Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/Makefile

b9022b53 - amt: add control plane of amt interface

Sun, 31 Oct 2021 16:00:02 +0000

amt: add control plane of amt interfaceIt adds definitions and control plane code for AMT.this is very similar to udp tunneling interfaces such as gtp, vxlan, etc.In the next patch, data plane code will be added.Signed-off-by: Taehee Yoo Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/Makefile

7ffa7542 - net: mhi: Remove MBIM protocol

Tue, 03 Aug 2021 13:36:29 +0000

net: mhi: Remove MBIM protocolThe MBIM protocol has now been integrated in a proper WWAN driver. Wecan then revert back to a simpler driver for mhi_net, which is usedfor raw IP or QMAP protocol (via rmnet link).- Remove protocol management- Remove WWAN framework usage (only valid for mbim)- Remove net/mhi directory for simpler mhi_net.c fileSigned-off-by: Loic Poulain Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/Makefile

4228c394 - make legacy ISA probe optional

Tue, 03 Aug 2021 11:40:47 +0000

make legacy ISA probe optionalThere are very few ISA drivers left that rely on the static probing fromdrivers/net/Space.o. Make them all select a new CONFIG_NETDEV_LEGACY_INITsymbol, and drop the entire probe logic when that is disabled.The 9 drivers that are called from Space.c are the same set thatcalls netdev_boot_setup_check().Signed-off-by: Arnd Bergmann Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/Makefile

4b2e6930 - mctp: Add initial driver infrastructure

Thu, 29 Jul 2021 02:20:43 +0000

mctp: Add initial driver infrastructureAdd an empty drivers/net/mctp/, for future interface drivers.Signed-off-by: Jeremy Kerr Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/Makefile

9a44c1cc - net: Add a WWAN subsystem

Fri, 16 Apr 2021 08:36:33 +0000

net: Add a WWAN subsystemThis change introduces initial support for a WWAN framework. Given thecomplexity and heterogeneity of existing WWAN hardwares and interfaces,there is no strict definition of what a WWAN device is and how it shouldbe represented. It's often a collection of multiple devices that performthe global WWAN feature (netdev, tty, chardev, etc).One usual way to expose modem controls and configuration is via highlevel protocols such as the well known AT command protocol, MBIM orQMI. The USB modems started to expose them as character devices, anduser daemons such as ModemManager learnt to use them.This initial version adds the concept of WWAN port, which is a logicalpipe to a modem control protocol. The protocols are rawly exposed touser via character device, allowing straigthforward support in existingtools (ModemManager, ofono...). The WWAN core takes care of the genericpart, including character device management, and relies on port driveroperations to receive/submit protocol data.Since the different devices exposing protocols for a same WWAN hardwaredo not necessarily know about each others (e.g. two different USBinterfaces, PCI/MHI channel devices...) and can be created/removed indifferent orders, the WWAN core ensures that all WAN ports contributingto the 'whole' WWAN feature are grouped under the same virtual WWANdevice, relying on the provided parent device (e.g. mhi controller,USB device). It's a 'trick' I copied from Johannes's earlier WWANsubsystem proposal.This initial version is purposely minimalist, it's essentially movingthe generic part of the previously proposed mhi_wwan_ctrl driver insidea common WWAN framework, but the implementation is open and flexibleenough to allow extension for further drivers.Signed-off-by: Loic Poulain Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/Makefile

227d7206 - dsa: simplify Kconfig symbols and dependencies

Fri, 19 Mar 2021 15:46:30 +0000

dsa: simplify Kconfig symbols and dependencies1. Remove CONFIG_HAVE_NET_DSA.CONFIG_HAVE_NET_DSA is a legacy leftover from the times when driversshould have selected CONFIG_NET_DSA manually.Currently, all drivers has explicit 'depends on NET_DSA', so this isno more needed.2. CONFIG_HAVE_NET_DSA dependencies became CONFIG_NET_DSA's ones. - dropped !S390 dependency which was introduced to be sure NET_DSA can select CONFIG_PHYLIB. DSA migrated to Phylink almost 3 years ago and the PHY library itself doesn't depend on !S390 since commit 870a2b5e4fcd ("phylib: remove !S390 dependeny from Kconfig"); - INET dependency is kept to be sure we can select NET_SWITCHDEV; - NETDEVICES dependency is kept to be sure we can select PHYLINK.3. DSA drivers menu now depends on NET_DSA.Instead on 'depends on NET_DSA' on every single driver, the entiremenu now depends on it. This eliminates a lot of duplicated linesfrom Kconfig with no loss (when CONFIG_NET_DSA=m, drivers also canbe only m or n).This also has a nice side effect that there's no more empty menu onconfigurations without DSA.4. Kbuild will now descend into 'drivers/net/dsa' only when CONFIG_NET_DSA is y or m.This is safe since no objects inside this folder can be built withoutDSA core, as well as when CONFIG_NET_DSA=m, no objects can bebuilt-in.Signed-off-by: Alexander Lobakin Reviewed-by: Vladimir Oltean Reviewed-by: Florian Fainelli Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/Makefile

b6ec6b89 - net: mhi: Add dedicated folder

Tue, 09 Feb 2021 09:05:55 +0000

net: mhi: Add dedicated folderCreate a dedicated mhi directory for mhi-net, mhi-net is going tobe split into differente files (for additional protocol support).Signed-off-by: Loic Poulain Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/Makefile

3ffec6a1 - net: Add mhi-net driver

Tue, 03 Nov 2020 17:23:54 +0000

net: Add mhi-net driverThis patch adds a new network driver implementing MHI transport fornetwork packets. Packets can be in any format, though QMAP (rmnet)is the usual protocol (flow control + PDN mux).It support two MHI devices, IP_HW0 which is, the path to the IPA(IP accelerator) on qcom modem, And IP_SW0 which is the softwaredriven IP path (to modem CPU).Signed-off-by: Loic Poulain Reviewed-by: Manivannan Sadhasivam Link: https://lore.kernel.org/r/1604424234-24446-2-git-send-email-loic.poulain@linaro.orgSigned-off-by: Jakub Kicinski List of files: /linux-6.15/drivers/net/Makefile

f54ec58f - wimax: move out to staging

Tue, 27 Oct 2020 20:12:12 +0000

wimax: move out to stagingThere are no known users of this driver as of October 2020, and it willbe removed unless someone turns out to still need it in future releases.According to https://en.wikipedia.org/wiki/List_of_WiMAX_networks, therehave been many public wimax networks, but it appears that many of thesehave migrated to LTE or discontinued their service altogether.As most PCs and phones lack WiMAX hardware support, the remainingnetworks tend to use standalone routers. These almost certainlyrun Linux, but not a modern kernel or the mainline wimax driver stack.NetworkManager appears to have dropped userspace support in 2015https://bugzilla.gnome.org/show_bug.cgi?id=747846, thewww.linuxwimax.orgsite had already shut down earlier.WiMax is apparently still being deployed on airport campus networks("AeroMACS"), but in a frequency band that was not supported by the oldIntel 2400m (used in Sandy Bridge laptops and earlier), which is theonly driver using the kernel's wimax stack.Move all files into drivers/staging/wimax, including the uapi headerfiles and documentation, to make it easier to remove it when it getsto that. Only minimal changes are made to the source files, in orderto make it possible to port patches across the move.Also remove the MAINTAINERS entry that refers to a broken mailinglist and website.Acked-by: Jakub Kicinski Acked-by: Greg Kroah-Hartman Acked-By: Inaky Perez-Gonzalez Acked-by: Johannes Berg Suggested-by: Inaky Perez-Gonzalez Signed-off-by: Arnd Bergmann List of files: /linux-6.15/drivers/net/Makefile

a9770eac - net: mdio: Move MDIO drivers into a new subdirectory

Thu, 27 Aug 2020 02:00:31 +0000

net: mdio: Move MDIO drivers into a new subdirectoryMove all the MDIO drivers and multiplexers into drivers/net/mdio. Themdio core is however left in the phy directory, due to mutualdependencies between the MDIO core and the PHY core.Take this opportunity to sort the Kconfig based on the menuconfigstrings, and move the multiplexers to the end with a separatingcomment.v2:Fix typo in commit messageAcked-by: Florian Fainelli Signed-off-by: Andrew Lunn Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/Makefile

2fa4e4b7 - net: pcs: Move XPCS into new PCS subdirectory

Thu, 27 Aug 2020 02:00:28 +0000

net: pcs: Move XPCS into new PCS subdirectoryCreate drivers/net/pcs and move the Synopsys DesignWare XPCS into thenew directory. Move the header file into a subdirectoryinclude/linux/pcsStart a naming convention of all PCS files use the prefix pcs-, andrename the XPCS files to fit.v2:Add include/linux/pcsv4:Fix include path in stmmac.Remove PCS_DEVICES to avoid new promptsCc: Jose Abreu Reviewed-by: Florian Fainelli Signed-off-by: Andrew Lunn Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/Makefile

08120d23 - soc: qcom: ipa: support build of IPA code

Fri, 06 Mar 2020 04:28:29 +0000

soc: qcom: ipa: support build of IPA codeAdd build and Kconfig support for the Qualcomm IPA driver.Signed-off-by: Alex Elder Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/Makefile