<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Makefile</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>110c18bf - net: dsa: mt7530: introduce driver for MT7988 built-in switch</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/net/dsa/Makefile#110c18bf</link>
        <description>net: dsa: mt7530: introduce driver for MT7988 built-in switchAdd driver for the built-in Gigabit Ethernet switch which can be foundin the MediaTek MT7988 SoC.The switch shares most of its design with MT7530 and MT7531, but hasit&apos;s registers mapped into the SoCs register space rather than beingconnected externally or internally via MDIO.Introduce a new platform driver to support that.Signed-off-by: Daniel Golle &lt;daniel@makrotopia.org&gt;Reviewed-by: Andrew Lunn &lt;andrew@lunn.ch&gt;Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

            List of files:
            /linux-6.15/drivers/net/dsa/Makefile</description>
        <pubDate>Mon, 03 Apr 2023 01:19:40 +0000</pubDate>
        <dc:creator>Daniel Golle &lt;daniel@makrotopia.org&gt;</dc:creator>
    </item>
<item>
        <title>cb675afc - net: dsa: mt7530: introduce separate MDIO driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/net/dsa/Makefile#cb675afc</link>
        <description>net: dsa: mt7530: introduce separate MDIO driverSplit MT7530 switch driver into a common part and a part specificfor MDIO connected switches and multi-chip modules.Move MDIO-specific functions to newly introduced mt7530-mdio.c whilekeeping the common parts in mt7530.c.Introduce new Kconfig symbol CONFIG_NET_DSA_MT7530_MDIO which isimplied by CONFIG_NET_DSA_MT7530.Signed-off-by: Daniel Golle &lt;daniel@makrotopia.org&gt;Reviewed-by: Andrew Lunn &lt;andrew@lunn.ch&gt;Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

            List of files:
            /linux-6.15/drivers/net/dsa/Makefile</description>
        <pubDate>Mon, 03 Apr 2023 01:19:13 +0000</pubDate>
        <dc:creator>Daniel Golle &lt;daniel@makrotopia.org&gt;</dc:creator>
    </item>
<item>
        <title>4bbaf764 - net: dsa: qca8k: move driver to qca dir</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/net/dsa/Makefile#4bbaf764</link>
        <description>net: dsa: qca8k: move driver to qca dirMove qca8k driver to qca dir in preparation for code split andintroduction of ipq4019 switch based on qca8k.Signed-off-by: Christian Marangi &lt;ansuelsmth@gmail.com&gt;Reviewed-by: Florian Fainelli &lt;f.fainelli@gmail.com&gt;Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

            List of files:
            /linux-6.15/drivers/net/dsa/Makefile</description>
        <pubDate>Wed, 13 Jul 2022 20:53:50 +0000</pubDate>
        <dc:creator>Christian Marangi &lt;ansuelsmth@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>888cdb89 - net: dsa: rzn1-a5psw: add Renesas RZ/N1 advanced 5 port switch driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/net/dsa/Makefile#888cdb89</link>
        <description>net: dsa: rzn1-a5psw: add Renesas RZ/N1 advanced 5 port switch driverAdd Renesas RZ/N1 advanced 5 port switch driver. This switch handles 5ports including 1 CPU management port. A MDIO bus is also exposed bythis switch and allows to communicate with PHYs connected to the ports.Each switch port (except for the CPU management ports) is connected tothe MII converter.This driver includes basic bridging support, more support will be addedlater (vlan, etc).Suggested-by: Jean-Pierre Geslin &lt;jean-pierre.geslin@non.se.com&gt;Suggested-by: Phil Edworthy &lt;phil.edworthy@renesas.com&gt;Signed-off-by: Cl&#233;ment L&#233;ger &lt;clement.leger@bootlin.com&gt;Reviewed-by: Vladimir Oltean &lt;olteanv@gmail.com&gt;Reviewed-by: Florian Fainelli &lt;f.fainelli@gmail.com&gt;Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

            List of files:
            /linux-6.15/drivers/net/dsa/Makefile</description>
        <pubDate>Fri, 24 Jun 2022 14:39:52 +0000</pubDate>
        <dc:creator>Cl&#233;ment L&#233;ger &lt;clement.leger@bootlin.com&gt;</dc:creator>
    </item>
<item>
        <title>319a70a5 - net: dsa: realtek-smi: move to subdirectory</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/net/dsa/Makefile#319a70a5</link>
        <description>net: dsa: realtek-smi: move to subdirectorySigned-off-by: Luiz Angelo Daros de Luca &lt;luizluca@gmail.com&gt;Tested-by: Ar&#305;n&#231; &#220;NAL &lt;arinc.unal@arinc9.com&gt;Reviewed-by: Alvin &#352;ipraga &lt;alsi@bang-olufsen.dk&gt;Reviewed-by: Linus Walleij &lt;linus.walleij@linaro.org&gt;Reviewed-by: Florian Fainelli &lt;f.fainelli@gmail.com&gt;Reviewed-by: Vladimir Oltean &lt;olteanv@gmail.com&gt;Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

            List of files:
            /linux-6.15/drivers/net/dsa/Makefile</description>
        <pubDate>Fri, 28 Jan 2022 06:04:58 +0000</pubDate>
        <dc:creator>Luiz Angelo Daros de Luca &lt;luizluca@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>4af2950c - net: dsa: realtek-smi: add rtl8365mb subdriver for RTL8365MB-VC</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/net/dsa/Makefile#4af2950c</link>
        <description>net: dsa: realtek-smi: add rtl8365mb subdriver for RTL8365MB-VCThis patch adds a realtek-smi subdriver for the RTL8365MB-VC 4+1 port10/100/1000M switch controller. The driver has been developed based on aGPL-licensed OS-agnostic Realtek vendor driver known as rtl8367c foundin the OpenWrt source tree.Despite the name, the RTL8365MB-VC has an entirely different registerlayout to the already-supported RTL8366RB ASIC. Notwithstanding this,the structure of the rtl8365mb subdriver is loosely based on the rtl8366rbsubdriver. Like the &apos;rb, it establishes its own irqchip to handlecascaded PHY link status interrupts.The RTL8365MB-VC switch is capable of offloading a large number offeatures from the software, but this patch introduces only the mostbasic DSA driver functionality. The ports always function as standaloneports, with bridging handled in software.One more thing. Realtek&apos;s nomenclature for switches makes it hard toknow exactly what other ASICs might be supported by this driver. Thevendor driver goes by the name rtl8367c, but as far as I can tell, nochip actually exists under this name. As such, the subdriver is namedrtl8365mb to emphasize the potentially limited support. But it is clearfrom the vendor sources that a number of other more advanced switchesshare a similar register layout, and further support should not be toohard to add given access to the relevant hardware. With this in mind,the subdriver has been written with as few assumptions about theparticular chip as is reasonable. But the RTL8365MB-VC is the onlyhardware I have available, so some further work is surely needed.Co-developed-by: Michael Rasmussen &lt;mir@bang-olufsen.dk&gt;Signed-off-by: Michael Rasmussen &lt;mir@bang-olufsen.dk&gt;Signed-off-by: Alvin &#352;ipraga &lt;alsi@bang-olufsen.dk&gt;Reviewed-by: Vladimir Oltean &lt;olteanv@gmail.com&gt;Reviewed-by: Linus Walleij &lt;linus.walleij@linaro.org&gt;Reviewed-by: Florian Fainelli &lt;f.fainelli@gmail.com&gt;Tested-by: Ar&#305;n&#231; &#220;NAL &lt;arinc.unal@arinc9.com&gt;Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

            List of files:
            /linux-6.15/drivers/net/dsa/Makefile</description>
        <pubDate>Mon, 18 Oct 2021 09:38:01 +0000</pubDate>
        <dc:creator>Alvin &#352;ipraga &lt;alsi@bang-olufsen.dk&gt;</dc:creator>
    </item>
<item>
        <title>ee00b24f - net: dsa: add Arrow SpeedChips XRS700x driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/net/dsa/Makefile#ee00b24f</link>
        <description>net: dsa: add Arrow SpeedChips XRS700x driverAdd a driver with initial support for the Arrow SpeedChips XRS7000series of gigabit Ethernet switch chips which are typically used incritical networking applications.The switches have up to three RGMII ports and one RMII port.Management to the switches can be performed over i2c or mdio.Support for advanced features such as PTP andHSR/PRP (IEC 62439-3 Clause 5 &amp; 4) is not included in this patch andmay be added at a later date.Signed-off-by: George McCollister &lt;george.mccollister@gmail.com&gt;Reviewed-by: Florian Fainelli &lt;f.fainelli@gmail.com&gt;Reviewed-by: Andrew Lunn &lt;andrew@lunn.ch&gt;Reviewed-by: Vladimir Oltean &lt;olteanv@gmail.com&gt;Signed-off-by: Jakub Kicinski &lt;kuba@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/net/dsa/Makefile</description>
        <pubDate>Thu, 14 Jan 2021 19:57:33 +0000</pubDate>
        <dc:creator>George McCollister &lt;george.mccollister@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>e4b27ebc - net: dsa: Add DSA driver for Hirschmann Hellcreek switches</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/net/dsa/Makefile#e4b27ebc</link>
        <description>net: dsa: Add DSA driver for Hirschmann Hellcreek switchesAdd a basic DSA driver for Hirschmann Hellcreek switches. Those switches areimplementing features needed for Time Sensitive Networking (TSN) such as supportfor the Time Precision Protocol and various shapers like the Time Aware Shaper.This driver includes basic support for networking: * VLAN handling * FDB handling * Port statistics * STP * PhylinkSigned-off-by: Kurt Kanzenbach &lt;kurt@linutronix.de&gt;Reviewed-by: Vladimir Oltean &lt;olteanv@gmail.com&gt;Reviewed-by: Florian Fainelli &lt;f.fainelli@gmail.com&gt;Signed-off-by: Jakub Kicinski &lt;kuba@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/net/dsa/Makefile</description>
        <pubDate>Tue, 03 Nov 2020 07:10:56 +0000</pubDate>
        <dc:creator>Kurt Kanzenbach &lt;kurt@linutronix.de&gt;</dc:creator>
    </item>
<item>
        <title>ec6698c2 - net: dsa: add support for Atheros AR9331 built-in switch</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/net/dsa/Makefile#ec6698c2</link>
        <description>net: dsa: add support for Atheros AR9331 built-in switchProvide basic support for Atheros AR9331 built-in switch. So far itworks as port multiplexer without any hardware offloading support.Reviewed-by: Andrew Lunn &lt;andrew@lunn.ch&gt;Reviewed-by: Vivien Didelot &lt;vivien.didelot@gmail.com&gt;Signed-off-by: Oleksij Rempel &lt;o.rempel@pengutronix.de&gt;Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

            List of files:
            /linux-6.15/drivers/net/dsa/Makefile</description>
        <pubDate>Wed, 18 Dec 2019 08:02:15 +0000</pubDate>
        <dc:creator>Oleksij Rempel &lt;o.rempel@pengutronix.de&gt;</dc:creator>
    </item>
<item>
        <title>56051948 - net: dsa: ocelot: add driver for Felix switch family</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/net/dsa/Makefile#56051948</link>
        <description>net: dsa: ocelot: add driver for Felix switch familyThis supports an Ethernet switching core from Vitesse / Microsemi /Microchip (VSC9959) which is part of the Ocelot family (a brand name),and whose code name is Felix. The switch can be (and is) integrated ondifferent SoCs as a PCIe endpoint device.The functionality is provided by the core of the Ocelot switch driver(drivers/net/ethernet/mscc). In this regard, the current driver is aninstance of Microsemi&apos;s Ocelot core driver, with a DSA front-end. Itinherits its name from VSC9959&apos;s code name, to distinguish itself fromthe switchdev ocelot driver.The patch adds the logic for probing a PCI device and defines theregister map for the VSC9959 switch core, since it has some differencesin register addresses and bitfield mappings compared to the other Ocelotswitches (VSC7511, VSC7512, VSC7513, VSC7514).The Felix driver declares the register map as part of the &quot;instancetable&quot;. Currently the VSC9959 inside NXP LS1028A is the only instance,but presumably it can support other switches in the Ocelot family, whenused in DSA mode (Linux running on the external CPU, and not on theembedded MIPS).In a few cases, some h/w operations have to be done differently onVSC9959 due to missing bitfields.  This is the case for the switch corereset and init.  Because for this operation Ocelot uses some bits thatare not present on Felix, the latter has to use a register from theglobal registers block (GCB) instead.Although it is a PCI driver, it relies on DT bindings for compatibilitywith DSA (CPU port link, PHY library). It does not have any customdevice tree bindings, since we would like to minimize its dependency ondevice tree though.Signed-off-by: Claudiu Manoil &lt;claudiu.manoil@nxp.com&gt;Signed-off-by: Vladimir Oltean &lt;vladimir.oltean@nxp.com&gt;Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

            List of files:
            /linux-6.15/drivers/net/dsa/Makefile</description>
        <pubDate>Thu, 14 Nov 2019 15:03:30 +0000</pubDate>
        <dc:creator>Vladimir Oltean &lt;vladimir.oltean@nxp.com&gt;</dc:creator>
    </item>
<item>
        <title>631e83bf - net: dsa: vsc73xx: add support for parallel mode</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/net/dsa/Makefile#631e83bf</link>
        <description>net: dsa: vsc73xx: add support for parallel modeThis patch add platform part of vsc73xx driver.It allows to use chip connected to a parallel memory bus and work inmemory-mapped I/O mode. (aka PI bus in chip manual)By default device is working in big endian mode.Signed-off-by: Pawel Dembicki &lt;paweldembicki@gmail.com&gt;Reviewed-by: Linus Walleij &lt;linus.walleij@linaro.org&gt;Reviewed-by: Florian Fainelli &lt;f.fainelli@gmail.com&gt;Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

            List of files:
            /linux-6.15/drivers/net/dsa/Makefile</description>
        <pubDate>Thu, 04 Jul 2019 22:29:06 +0000</pubDate>
        <dc:creator>Pawel Dembicki &lt;paweldembicki@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>95711cd5 - net: dsa: vsc73xx: Split vsc73xx driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/net/dsa/Makefile#95711cd5</link>
        <description>net: dsa: vsc73xx: Split vsc73xx driverThis driver (currently) only takes control of the switch chip overSPI and configures it to route packages around when connected to aCPU port. But Vitesse chip support also parallel interface.This patch split driver into two parts: core and spi. It is requiredfor add support to another managing interface.Tested-by: Linus Walleij &lt;linus.walleij@linaro.org&gt;Signed-off-by: Pawel Dembicki &lt;paweldembicki@gmail.com&gt;Reviewed-by: Linus Walleij &lt;linus.walleij@linaro.org&gt;Reviewed-by: Florian Fainelli &lt;f.fainelli@gmail.com&gt;Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

            List of files:
            /linux-6.15/drivers/net/dsa/Makefile</description>
        <pubDate>Thu, 04 Jul 2019 22:29:05 +0000</pubDate>
        <dc:creator>Pawel Dembicki &lt;paweldembicki@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>f0c03ee0 - net: dsa: fix warning same module names</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/net/dsa/Makefile#f0c03ee0</link>
        <description>net: dsa: fix warning same module namesWhen building with CONFIG_NET_DSA_REALTEK_SMI and CONFIG_REALTEK_PHYenabled as loadable modules, we see the following warning:warning: same module names found:  drivers/net/phy/realtek.ko  drivers/net/dsa/realtek.koRework so the driver name is realtek-smi instead of realtek.Reviewed-by: Linus Walleij &lt;linus.walleij@linaro.org&gt;Reviewed-by: Andrew Lunn &lt;andrew@lunn.ch&gt;Signed-off-by: Anders Roxell &lt;anders.roxell@linaro.org&gt;Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

            List of files:
            /linux-6.15/drivers/net/dsa/Makefile</description>
        <pubDate>Thu, 13 Jun 2019 11:35:03 +0000</pubDate>
        <dc:creator>Anders Roxell &lt;anders.roxell@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>8aa9ebcc - net: dsa: Introduce driver for NXP SJA1105 5-port L2 switch</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/net/dsa/Makefile#8aa9ebcc</link>
        <description>net: dsa: Introduce driver for NXP SJA1105 5-port L2 switchAt this moment the following is supported:* Link state management through phylib* Autonomous L2 forwarding managed through iproute2 bridge commands.IP termination must be done currently through the master netdevice,since the switch is unmanaged at this point and usingDSA_TAG_PROTO_NONE.Signed-off-by: Vladimir Oltean &lt;olteanv@gmail.com&gt;Signed-off-by: Georg Waibel &lt;georg.waibel@sensor-technik.de&gt;Acked-by: Florian Fainelli &lt;f.fainelli@gmail.com&gt;Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

            List of files:
            /linux-6.15/drivers/net/dsa/Makefile</description>
        <pubDate>Thu, 02 May 2019 20:23:30 +0000</pubDate>
        <dc:creator>Vladimir Oltean &lt;olteanv@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>14fceff4 - net: dsa: Add Lantiq / Intel DSA driver for vrx200</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/net/dsa/Makefile#14fceff4</link>
        <description>net: dsa: Add Lantiq / Intel DSA driver for vrx200This adds the DSA driver for the GSWIP Switch found in the VRX200 SoC.This switch is integrated in the DSL SoC, this SoC uses a GSWIP version2.1, there are other SoCs using different versions of this IP block, butthis driver was only tested with the version found in the VRX200.Currently only the basic features are implemented which will forward allpackages to the CPU and let the CPU do the forwarding. The hardware alsosupport Layer 2 offloading which is not yet implemented in this driver.The GPHY FW loaded is now done by this driver and not any more by theseparate driver in drivers/soc/lantiq/gphy.c, I will remove this driveris a separate patch. to make use of the GPHY this switch driver isneeded anyway. Other SoCs have more embedded GPHYs so this driver shouldsupport a variable number of GPHYs. After the firmware was loaded theGPHY can be probed on the MDIO bus and it behaves like an external GPHY,without the firmware it can not be probed on the MDIO bus.The clock names in the sysctrl.c file have to be changed because theclocks are now used by a different driver. This should be cleaned up anda real common clock driver should provide the clocks instead.Signed-off-by: Hauke Mehrtens &lt;hauke@hauke-m.de&gt;Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

            List of files:
            /linux-6.15/drivers/net/dsa/Makefile</description>
        <pubDate>Sun, 09 Sep 2018 20:20:39 +0000</pubDate>
        <dc:creator>Hauke Mehrtens &lt;hauke@hauke-m.de&gt;</dc:creator>
    </item>
<item>
        <title>d8652956 - net: dsa: realtek-smi: Add Realtek SMI driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/net/dsa/Makefile#d8652956</link>
        <description>net: dsa: realtek-smi: Add Realtek SMI driverThis adds a driver core for the Realtek SMI chips and asubdriver for the RTL8366RB. I just added this chip simplybecause it is all I can test.The code is a massaged variant of the code that has beensitting out-of-tree in OpenWRT for years in the absence ofa proper switch subsystem. This creates a DSA driver for it.I have tried to credit the original authors whereverpossible.The main changes I&apos;ve done from the OpenWRT code:- Added an IRQ chip inside the RTL8366RB switch to demux and  handle the line state IRQs.- Distributed the phy handling out to the PHY driver.- Added some RTL8366RB code that was missing in the driver at  the time, such as setting up &quot;green ethernet&quot; with a funny  jam table and forcing MAC5 (the CPU port) into 1 GBit.- Select jam table and add the default jam table from the  vendor driver, also for ASIC &quot;version 0&quot; if need be.- Do not store jam tables in the device tree, store them  in the driver.- Pick in the &quot;initvals&quot; jam tables from OpenWRT&apos;s driver  and make those get selected per compatible for the  whole system. It&apos;s apparently about electrical settings  for this system and whatnot, not really configuration  from device tree.- Implemented LED control: beware of bugs because there are  no LEDs on the device I am using!We do not implement custom DSA tags. This is explained ina comment in the driver as well: this &quot;tagging protocol&quot; isnot simply a few extra bytes tagged on to the ethernetframe as DSA is used to. Instead, enabling the CPU tagswill make the switch start talking Realtek RRCP internally.For example a simple ping will make this kind of packetsappear inside the switch:0000   ff ff ff ff ff ff bc ae c5 6b a8 3d 88 99 a2 000010   08 06 00 01 08 00 06 04 00 01 bc ae c5 6b a8 3d0020   a9 fe 01 01 00 00 00 00 00 00 a9 fe 01 02 00 000030   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00As you can see a custom &quot;8899&quot; tagged packet using theprotocol 0xa2. Norm RRCP appears to always have thisprotocol set to 0x01 according to OpenRRCP. You can alsosee that this is not a ping packet at all, instead theswitch is starting to talk network management issueswith the CPU port.So for now custom &quot;tagging&quot; is disabled.This was tested on the D-Link DIR-685 with initramfs andOpenWRT userspaces and works fine on all the LAN ports(lan0 .. lan3). The WAN port is yet not working.Cc: Antti Sepp&#228;l&#228; &lt;a.seppala@gmail.com&gt;Cc: Roman Yeryomin &lt;roman@advem.lv&gt;Cc: Colin Leitner &lt;colin.leitner@googlemail.com&gt;Cc: Gabor Juhos &lt;juhosg@openwrt.org&gt;Cc: Florian Fainelli &lt;f.fainelli@gmail.com&gt;Signed-off-by: Linus Walleij &lt;linus.walleij@linaro.org&gt;Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

            List of files:
            /linux-6.15/drivers/net/dsa/Makefile</description>
        <pubDate>Sat, 14 Jul 2018 09:45:55 +0000</pubDate>
        <dc:creator>Linus Walleij &lt;linus.walleij@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>05bd97fc - net: dsa: Add Vitesse VSC73xx DSA router driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/net/dsa/Makefile#05bd97fc</link>
        <description>net: dsa: Add Vitesse VSC73xx DSA router driverThis adds a DSA driver for:Vitesse VSC7385 SparX-G5 5-port Integrated Gigabit Ethernet SwitchVitesse VSC7388 SparX-G8 8-port Integrated Gigabit Ethernet SwitchVitesse VSC7395 SparX-G5e 5+1-port Integrated Gigabit Ethernet SwitchVitesse VSC7398 SparX-G8e 8-port Integrated Gigabit Ethernet SwitchThese switches have a built-in 8051 CPU and can download and executefirmware in this CPU. They can also be configured to use an externalCPU handling the switch in a memory-mapped manner by connecting tothat external CPU&apos;s memory bus.This driver (currently) only takes control of the switch chip overSPI and configures it to route packages around when connected to aCPU port. The chip has embedded PHYs and VLAN support so we model itusing DSA as a best fit so we can easily add VLAN support and maybelater also exploit the internal frame header to get more directcontrol over the switch.The four built-in GPIO lines are exposed using a standard GPIO chip.Signed-off-by: Linus Walleij &lt;linus.walleij@linaro.org&gt;Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

            List of files:
            /linux-6.15/drivers/net/dsa/Makefile</description>
        <pubDate>Sat, 30 Jun 2018 11:17:31 +0000</pubDate>
        <dc:creator>Linus Walleij &lt;linus.walleij@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>40013ff2 - net: dsa: Fix functional dsa-loop dependency on FIXED_PHY</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/net/dsa/Makefile#40013ff2</link>
        <description>net: dsa: Fix functional dsa-loop dependency on FIXED_PHYWe have a functional dependency on the FIXED_PHY MDIO bus because we registerfixed PHY devices &quot;the old way&quot; which only works if the code that does this hashad a chance to run before the fixed MDIO bus is probed. Make sure we accountfor that and have dsa_loop_bdinfo.o be either built-in or modular depending onwhether CONFIG_FIXED_PHY reflects that too.Fixes: 98cd1552ea27 (&quot;net: dsa: Mock-up driver&quot;)Signed-off-by: Florian Fainelli &lt;f.fainelli@gmail.com&gt;Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

            List of files:
            /linux-6.15/drivers/net/dsa/Makefile</description>
        <pubDate>Wed, 21 Mar 2018 00:31:10 +0000</pubDate>
        <dc:creator>Florian Fainelli &lt;f.fainelli@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/net/dsa/Makefile#b2441318</link>
        <description>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 &apos;GPL-2.0&apos;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 &amp; 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 &gt;5   lines of source - File already had some variant of a license header in it (even if &lt;5   lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn&apos;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 &quot;GPL-2.0 WITH   Linux-syscall-note&quot; otherwise it was &quot;GPL-2.0&quot;.  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&apos;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 &lt;kstewart@linuxfoundation.org&gt;Reviewed-by: Philippe Ombredanne &lt;pombredanne@nexb.com&gt;Reviewed-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/net/dsa/Makefile</description>
        <pubDate>Wed, 01 Nov 2017 14:07:57 +0000</pubDate>
        <dc:creator>Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;</dc:creator>
    </item>
<item>
        <title>b987e98e - dsa: add DSA switch driver for Microchip KSZ9477</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/net/dsa/Makefile#b987e98e</link>
        <description>dsa: add DSA switch driver for Microchip KSZ9477The KSZ9477 is a fully integrated layer 2, managed, 7 ports GigE switchwith numerous advanced features. 5 ports incorporate 10/100/1000 Mbps PHYs.The other 2 ports have interfaces that can be configured as SGMII, RGMII, MIIor RMII. Either of these may connect directly to a host processor orto an external PHY. The SGMII port may interface to a fiber optic transceiver.This driver currently supports vlan, fdb, mdb &amp; mirror dsa switch operations.Reviewed-by: Florian Fainelli &lt;f.fainelli@gmail.com&gt;Signed-off-by: Woojung Huh &lt;Woojung.Huh@microchip.com&gt;Reviewed-by: Andrew Lunn &lt;andrew@lunn.ch&gt;Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

            List of files:
            /linux-6.15/drivers/net/dsa/Makefile</description>
        <pubDate>Wed, 31 May 2017 20:19:19 +0000</pubDate>
        <dc:creator>Woojung Huh &lt;Woojung.Huh@microchip.com&gt;</dc:creator>
    </item>
</channel>
</rss>
