)]}' { "log": [ { "commit": "e84665c9cb4db963393fafad6fefe5efdd7e4a09", "tree": "545c4a2a63a77b853e3f34609d86b346fe61baf4", "parents": [ "076d3e10a54caa2c148de5732c126c7a31381d48" ], "author": { "name": "Lennert Buytenhek", "email": "buytenh@wantstofly.org", "time": "Fri Mar 20 09:52:09 2009 +0000" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Sat Mar 21 19:06:54 2009 -0700" }, "message": "dsa: add switch chip cascading support\n\nThe initial version of the DSA driver only supported a single switch\nchip per network interface, while DSA-capable switch chips can be\ninterconnected to form a tree of switch chips. This patch adds support\nfor multiple switch chips on a network interface.\n\nAn example topology for a 16-port device with an embedded CPU is as\nfollows:\n\n\t+-----+ +--------+ +--------+\n\t| |eth0 10| switch |9 10| switch |\n\t| CPU +----------+ +-------+ |\n\t| | | chip 0 | | chip 1 |\n\t+-----+ +---++---+ +---++---+\n\t || ||\n\t || ||\n\t ||1000baseT ||1000baseT\n\t ||ports 1-8 ||ports 9-16\n\nThis requires a couple of interdependent changes in the DSA layer:\n\n- The dsa platform driver data needs to be extended: there is still\n only one netdevice per DSA driver instance (eth0 in the example\n above), but each of the switch chips in the tree needs its own\n mii_bus device pointer, MII management bus address, and port name\n array. (include/net/dsa.h) The existing in-tree dsa users need\n some small changes to deal with this. (arch/arm)\n\n- The DSA and Ethertype DSA tagging modules need to be extended to\n use the DSA device ID field on receive and demultiplex the packet\n accordingly, and fill in the DSA device ID field on transmit\n according to which switch chip the packet is heading to.\n (net/dsa/tag_{dsa,edsa}.c)\n\n- The concept of \"CPU port\", which is the switch chip port that the\n CPU is connected to (port 10 on switch chip 0 in the example), needs\n to be extended with the concept of \"upstream port\", which is the\n port on the switch chip that will bring us one hop closer to the CPU\n (port 10 for both switch chips in the example above).\n\n- The dsa platform data needs to specify which ports on which switch\n chips are links to other switch chips, so that we can enable DSA\n tagging mode on them. (For inter-switch links, we always use\n non-EtherType DSA tagging, since it has lower overhead. The CPU\n link uses dsa or edsa tagging depending on what the \u0027root\u0027 switch\n chip supports.) This is done by specifying \"dsa\" for the given\n port in the port array.\n\n- The dsa platform data needs to be extended with information on via\n which port to reach any given switch chip from any given switch chip.\n This info is specified via the per-switch chip data struct -\u003ertable[]\n array, which gives the nexthop ports for each of the other switches\n in the tree.\n\nFor the example topology above, the dsa platform data would look\nsomething like this:\n\n\tstatic struct dsa_chip_data sw[2] \u003d {\n\t\t{\n\t\t\t.mii_bus\t\u003d \u0026foo,\n\t\t\t.sw_addr\t\u003d 1,\n\t\t\t.port_names[0]\t\u003d \"p1\",\n\t\t\t.port_names[1]\t\u003d \"p2\",\n\t\t\t.port_names[2]\t\u003d \"p3\",\n\t\t\t.port_names[3]\t\u003d \"p4\",\n\t\t\t.port_names[4]\t\u003d \"p5\",\n\t\t\t.port_names[5]\t\u003d \"p6\",\n\t\t\t.port_names[6]\t\u003d \"p7\",\n\t\t\t.port_names[7]\t\u003d \"p8\",\n\t\t\t.port_names[9]\t\u003d \"dsa\",\n\t\t\t.port_names[10]\t\u003d \"cpu\",\n\t\t\t.rtable\t\t\u003d (s8 []){ -1, 9, },\n\t\t}, {\n\t\t\t.mii_bus\t\u003d \u0026foo,\n\t\t\t.sw_addr\t\u003d 2,\n\t\t\t.port_names[0]\t\u003d \"p9\",\n\t\t\t.port_names[1]\t\u003d \"p10\",\n\t\t\t.port_names[2]\t\u003d \"p11\",\n\t\t\t.port_names[3]\t\u003d \"p12\",\n\t\t\t.port_names[4]\t\u003d \"p13\",\n\t\t\t.port_names[5]\t\u003d \"p14\",\n\t\t\t.port_names[6]\t\u003d \"p15\",\n\t\t\t.port_names[7]\t\u003d \"p16\",\n\t\t\t.port_names[10]\t\u003d \"dsa\",\n\t\t\t.rtable\t\t\u003d (s8 []){ 10, -1, },\n\t\t},\n\t},\n\n\tstatic struct dsa_platform_data pd \u003d {\n\t\t.netdev\t\t\u003d \u0026foo,\n\t\t.nr_switches\t\u003d 2,\n\t\t.sw\t\t\u003d sw,\n\t};\n\nSigned-off-by: Lennert Buytenhek \u003cbuytenh@marvell.com\u003e\nTested-by: Gary Thomas \u003cgary@mlbassoc.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "076d3e10a54caa2c148de5732c126c7a31381d48", "tree": "8c9686248d46c803a994ab51ddee306ad4e4f4bc", "parents": [ "c084080151e1de92159f8437fde34b6e5bebe35e" ], "author": { "name": "Lennert Buytenhek", "email": "buytenh@wantstofly.org", "time": "Fri Mar 20 09:50:39 2009 +0000" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Sat Mar 21 19:06:54 2009 -0700" }, "message": "dsa: add support for the Marvell 88E6095/6095F switch chips\n\nAdd support for the Marvell 88E6095/6095F switch chips. These\nchips are similar to the 88e6131, so we can add the support to\nmv88e6131.c easily.\n\nThanks to Gary Thomas \u003cgary@mlbassoc.com\u003e and Jesper Dangaard\nBrouer \u003chawk@diku.dk\u003e for testing various patches.\n\nSigned-off-by: Lennert Buytenhek \u003cbuytenh@marvell.com\u003e\nTested-by: Gary Thomas \u003cgary@mlbassoc.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "09640e6365c679b5642b1c41b6d7078f51689ddf", "tree": "a2b80c153bd23fe59db8c6994fda29923819fcea", "parents": [ "ee437770c42088b9b653e8b3bf28a61fa647f84e" ], "author": { "name": "Harvey Harrison", "email": "harvey.harrison@gmail.com", "time": "Sun Feb 01 00:45:17 2009 -0800" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Sun Feb 01 00:45:17 2009 -0800" }, "message": "net: replace uses of __constant_{endian}\n\nBase versions handle constant folding now.\n\nSigned-off-by: Harvey Harrison \u003charvey.harrison@gmail.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "5eaa65b240c5eb7bf2235eb9dd177c83e6e3832c", "tree": "1a6b217cfc5b241b298a8765f68fcb5f711f9bc3", "parents": [ "2107fb8b5bf018be691afdd4c6ffaecf0c3307be" ], "author": { "name": "Roel Kluin", "email": "roel.kluin@gmail.com", "time": "Wed Dec 10 15:18:31 2008 -0800" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Wed Dec 10 15:18:31 2008 -0800" }, "message": "net: Make static\n\nSparse asked whether these could be static.\n\nSigned-off-by: Roel Kluin \u003croel.kluin@gmail.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "2e5f032095ff101274dfb03d5fd5e06d9aeb83cd", "tree": "eeb61cf6665452288a25434c54bc8d4ff8031cef", "parents": [ "cf85d08fdf4548ee46657ccfb7f9949a85145db5" ], "author": { "name": "Lennert Buytenhek", "email": "buytenh@wantstofly.org", "time": "Tue Oct 07 13:45:18 2008 +0000" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Wed Oct 08 17:24:09 2008 -0700" }, "message": "dsa: add support for the Marvell 88E6131 switch chip\n\nAdd support for the Marvell 88E6131 switch chip. This chip only\nsupports the original (ethertype-less) DSA tagging format.\n\nOn the 88E6131, there is a PHY Polling Unit (PPU) which has exclusive\naccess to each of the PHYs\u0027s MII management registers. If we want to\ntalk to the PHYs from software, we have to disable the PPU and wait\nfor it to complete its current transaction before we can do so, and we\nneed to re-enable the PPU afterwards to make sure that the switch will\nnotice changes in link state and speed on the individual ports as they\noccur.\n\nSince disabling the PPU is rather slow, and since MII management\naccesses are typically done in bursts, this patch keeps the PPU disabled\nfor 10ms after a software access completes. This makes handling the\nPPU slightly more complex, but speeds up something like running ethtool\non one of the switch slave interfaces from ~300ms to ~30ms on typical\nhardware.\n\nSigned-off-by: Lennert Buytenhek \u003cbuytenh@marvell.com\u003e\nTested-by: Nicolas Pitre \u003cnico@marvell.com\u003e\nTested-by: Peter van Valderen \u003clinux@ddcrew.com\u003e\nTested-by: Dirk Teurlings \u003cdirk@upexia.nl\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" } ] }