€•QIŒsphinx.addnodes”Œdocument”“”)”}”(Œ rawsource”Œ”Œchildren”]”(Œ translations”Œ LanguagesNode”“”)”}”(hhh]”(hŒ pending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ refdomain”Œstd”Œreftype”Œdoc”Œ reftarget”Œ&/translations/zh_CN/networking/dsa/b53”Œmodname”NŒ classname”NŒ refexplicit”ˆuŒtagname”hhh ubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ&/translations/zh_TW/networking/dsa/b53”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ&/translations/it_IT/networking/dsa/b53”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ&/translations/ja_JP/networking/dsa/b53”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ&/translations/ko_KR/networking/dsa/b53”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒPortuguese (Brazilian)”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ&/translations/pt_BR/networking/dsa/b53”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒSpanish”…””}”hh–sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ&/translations/sp_SP/networking/dsa/b53”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h hhŒ _document”hŒsource”NŒline”NubhŒcomment”“”)”}”(hŒ SPDX-License-Identifier: GPL-2.0”h]”hŒ SPDX-License-Identifier: GPL-2.0”…””}”hh·sbah}”(h]”h ]”h"]”h$]”h&]”Œ xml:space”Œpreserve”uh1hµhhh²hh³Œ@/var/lib/git/docbuild/linux/Documentation/networking/dsa/b53.rst”h´KubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒ*Broadcom RoboSwitch Ethernet switch driver”h]”hŒ*Broadcom RoboSwitch Ethernet switch driver”…””}”(hhÏh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhhÊh²hh³hÇh´KubhŒ paragraph”“”)”}”(hŒ‚The Broadcom RoboSwitch Ethernet switch family is used in quite a range of xDSL router, cable modems and other multimedia devices.”h]”hŒ‚The Broadcom RoboSwitch Ethernet switch family is used in quite a range of xDSL router, cable modems and other multimedia devices.”…””}”(hhßh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KhhÊh²hubhÞ)”}”(hŒtThe actual implementation supports the devices BCM5325E, BCM5365, BCM539x, BCM53115 and BCM53125 as well as BCM63XX.”h]”hŒtThe actual implementation supports the devices BCM5325E, BCM5365, BCM539x, BCM53115 and BCM53125 as well as BCM63XX.”…””}”(hhíh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K hhÊh²hubhÉ)”}”(hhh]”(hÎ)”}”(hŒImplementation details”h]”hŒImplementation details”…””}”(hhþh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhhûh²hh³hÇh´KubhÞ)”}”(hŒµThe driver is located in ``drivers/net/dsa/b53/`` and is implemented as a DSA driver; see ``Documentation/networking/dsa/dsa.rst`` for details on the subsystem and what it provides.”h]”(hŒThe driver is located in ”…””}”(hj h²hh³Nh´NubhŒliteral”“”)”}”(hŒ``drivers/net/dsa/b53/``”h]”hŒdrivers/net/dsa/b53/”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj ubhŒ) and is implemented as a DSA driver; see ”…””}”(hj h²hh³Nh´Nubj)”}”(hŒ(``Documentation/networking/dsa/dsa.rst``”h]”hŒ$Documentation/networking/dsa/dsa.rst”…””}”(hj(h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj ubhŒ3 for details on the subsystem and what it provides.”…””}”(hj h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Khhûh²hubhÞ)”}”(hXFThe switch is, if possible, configured to enable a Broadcom specific 4-bytes switch tag which gets inserted by the switch for every packet forwarded to the CPU interface, conversely, the CPU network interface should insert a similar tag for packets entering the CPU port. The tag format is described in ``net/dsa/tag_brcm.c``.”h]”(hX/The switch is, if possible, configured to enable a Broadcom specific 4-bytes switch tag which gets inserted by the switch for every packet forwarded to the CPU interface, conversely, the CPU network interface should insert a similar tag for packets entering the CPU port. The tag format is described in ”…””}”(hj@h²hh³Nh´Nubj)”}”(hŒ``net/dsa/tag_brcm.c``”h]”hŒnet/dsa/tag_brcm.c”…””}”(hjHh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj@ubhŒ.”…””}”(hj@h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Khhûh²hubhÞ)”}”(hŒOThe configuration of the device depends on whether or not tagging is supported.”h]”hŒOThe configuration of the device depends on whether or not tagging is supported.”…””}”(hj`h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Khhûh²hubhÞ)”}”(hŒˆThe interface names and example network configuration are used according the configuration described in the :ref:`dsa-config-showcases`.”h]”(hŒlThe interface names and example network configuration are used according the configuration described in the ”…””}”(hjnh²hh³Nh´Nubh)”}”(hŒ:ref:`dsa-config-showcases`”h]”hŒinline”“”)”}”(hjxh]”hŒdsa-config-showcases”…””}”(hj|h²hh³Nh´Nubah}”(h]”h ]”(Œxref”Œstd”Œstd-ref”eh"]”h$]”h&]”uh1jzhjvubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”Œnetworking/dsa/b53”Œ refdomain”j‡Œreftype”Œref”Œ refexplicit”‰Œrefwarn”ˆŒ reftarget”Œdsa-config-showcases”uh1hh³hÇh´KhjnubhŒ.”…””}”(hjnh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Khhûh²hubhÉ)”}”(hhh]”(hÎ)”}”(hŒ"Configuration with tagging support”h]”hŒ"Configuration with tagging support”…””}”(hj¨h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj¥h²hh³hÇh´K!ubhÞ)”}”(hŒThe tagging based configuration is desired. It is not specific to the b53 DSA driver and will work like all DSA drivers which supports tagging.”h]”hŒThe tagging based configuration is desired. It is not specific to the b53 DSA driver and will work like all DSA drivers which supports tagging.”…””}”(hj¶h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K#hj¥h²hubhÞ)”}”(hŒ$See :ref:`dsa-tagged-configuration`.”h]”(hŒSee ”…””}”(hjÄh²hh³Nh´Nubh)”}”(hŒ:ref:`dsa-tagged-configuration`”h]”j{)”}”(hjÎh]”hŒdsa-tagged-configuration”…””}”(hjÐh²hh³Nh´Nubah}”(h]”h ]”(j†Œstd”Œstd-ref”eh"]”h$]”h&]”uh1jzhjÌubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”j“Œ refdomain”jÚŒreftype”Œref”Œ refexplicit”‰Œrefwarn”ˆj™Œdsa-tagged-configuration”uh1hh³hÇh´K&hjÄubhŒ.”…””}”(hjÄh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K&hj¥h²hubeh}”(h]”Œ"configuration-with-tagging-support”ah ]”h"]”Œ"configuration with tagging support”ah$]”h&]”uh1hÈhhûh²hh³hÇh´K!ubhÉ)”}”(hhh]”(hÎ)”}”(hŒ%Configuration without tagging support”h]”hŒ%Configuration without tagging support”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjþh²hh³hÇh´K)ubhÞ)”}”(hXOlder models (5325, 5365) support a different tag format that is not supported yet. 539x and 531x5 require managed mode and some special handling, which is also not yet supported. The tagging support is disabled in these cases and the switch need a different configuration.”h]”hXOlder models (5325, 5365) support a different tag format that is not supported yet. 539x and 531x5 require managed mode and some special handling, which is also not yet supported. The tagging support is disabled in these cases and the switch need a different configuration.”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K+hjþh²hubhÞ)”}”(hŒIThe configuration slightly differ from the :ref:`dsa-vlan-configuration`.”h]”(hŒ+The configuration slightly differ from the ”…””}”(hjh²hh³Nh´Nubh)”}”(hŒ:ref:`dsa-vlan-configuration`”h]”j{)”}”(hj'h]”hŒdsa-vlan-configuration”…””}”(hj)h²hh³Nh´Nubah}”(h]”h ]”(j†Œstd”Œstd-ref”eh"]”h$]”h&]”uh1jzhj%ubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”j“Œ refdomain”j3Œreftype”Œref”Œ refexplicit”‰Œrefwarn”ˆj™Œdsa-vlan-configuration”uh1hh³hÇh´K0hjubhŒ.”…””}”(hjh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K0hjþh²hubhÞ)”}”(hŒ°The b53 tags the CPU port in all VLANs, since otherwise any PVID untagged VLAN programming would basically change the CPU port's default PVID and make it untagged, undesirable.”h]”hŒ²The b53 tags the CPU port in all VLANs, since otherwise any PVID untagged VLAN programming would basically change the CPU port’s default PVID and make it untagged, undesirable.”…””}”(hjOh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K2hjþh²hubhÞ)”}”(hXIn difference to the configuration described in :ref:`dsa-vlan-configuration` the default VLAN 1 has to be removed from the user interface configuration in single port and gateway configuration, while there is no need to add an extra VLAN configuration in the bridge showcase.”h]”(hŒ0In difference to the configuration described in ”…””}”(hj]h²hh³Nh´Nubh)”}”(hŒ:ref:`dsa-vlan-configuration`”h]”j{)”}”(hjgh]”hŒdsa-vlan-configuration”…””}”(hjih²hh³Nh´Nubah}”(h]”h ]”(j†Œstd”Œstd-ref”eh"]”h$]”h&]”uh1jzhjeubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”j“Œ refdomain”jsŒreftype”Œref”Œ refexplicit”‰Œrefwarn”ˆj™Œdsa-vlan-configuration”uh1hh³hÇh´K6hj]ubhŒÇ the default VLAN 1 has to be removed from the user interface configuration in single port and gateway configuration, while there is no need to add an extra VLAN configuration in the bridge showcase.”…””}”(hj]h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K6hjþh²hubhÉ)”}”(hhh]”(hÎ)”}”(hŒ single port”h]”hŒ single port”…””}”(hj’h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjh²hh³hÇh´K