€•pH      Œsphinx.addnodes”Œdocument”“”)”}”(Œ	rawsource”Œ ”Œchildren”]”(Œtranslations”ŒLanguagesNode”“”)”}”(hhh]”(h Œpending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ
attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ	refdomain”Œstd”Œreftype”Œdoc”Œ	reftarget”Œ&/translations/zh_CN/networking/dsa/b53”Œmodname”NŒ	classname”NŒrefexplicit”ˆuŒtagname”hhhubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ&/translations/zh_TW/networking/dsa/b53”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ&/translations/it_IT/networking/dsa/b53”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ&/translations/ja_JP/networking/dsa/b53”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ&/translations/ko_KR/networking/dsa/b53”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒSpanish”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ&/translations/sp_SP/networking/dsa/b53”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h
hhŒ	_document”hŒsource”NŒline”NubhŒcomment”“”)”}”(hŒ SPDX-License-Identifier: GPL-2.0”h]”hŒ SPDX-License-Identifier: GPL-2.0”…””}”hh£sbah}”(h]”h ]”h"]”h$]”h&]”Œ	xml:space”Œpreserve”uh1h¡hhhžhhŸŒ@/var/lib/git/docbuild/linux/Documentation/networking/dsa/b53.rst”h KubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒ*Broadcom RoboSwitch Ethernet switch driver”h]”hŒ*Broadcom RoboSwitch Ethernet switch driver”…””}”(hh»hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hh¶hžhhŸh³h KubhŒ	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.”…””}”(hhËhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khh¶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.”…””}”(hhÙhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K
hh¶hžhubhµ)”}”(hhh]”(hº)”}”(hŒImplementation details”h]”hŒImplementation details”…””}”(hhêhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hhçhžhhŸh³h KubhÊ)”}”(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 ”…””}”(hhøhžhhŸNh NubhŒliteral”“”)”}”(hŒ``drivers/net/dsa/b53/``”h]”hŒdrivers/net/dsa/b53/”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j   hhøubhŒ) and is implemented as a
DSA driver; see ”…””}”(hhøhžhhŸNh Nubj  )”}”(hŒ(``Documentation/networking/dsa/dsa.rst``”h]”hŒ$Documentation/networking/dsa/dsa.rst”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j   hhøubhŒ3 for details on the
subsystem and what it provides.”…””}”(hhøhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KhhçhžhubhÊ)”}”(hXF  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
``net/dsa/tag_brcm.c``.”h]”(hX/  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
”…””}”(hj,  hžhhŸNh Nubj  )”}”(hŒ``net/dsa/tag_brcm.c``”h]”hŒnet/dsa/tag_brcm.c”…””}”(hj4  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j   hj,  ubhŒ.”…””}”(hj,  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khhç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.”…””}”(hjL  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khhç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 ”…””}”(hjZ  hžhhŸNh Nubh)”}”(hŒ:ref:`dsa-config-showcases`”h]”hŒinline”“”)”}”(hjd  h]”hŒdsa-config-showcases”…””}”(hjh  hžhhŸNh Nubah}”(h]”h ]”(Œxref”Œstd”Œstd-ref”eh"]”h$]”h&]”uh1jf  hjb  ubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”Œnetworking/dsa/b53”Œ	refdomain”js  Œreftype”Œref”Œrefexplicit”‰Œrefwarn”ˆŒ	reftarget”Œdsa-config-showcases”uh1hhŸh³h KhjZ  ubhŒ.”…””}”(hjZ  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khhçhžhubhµ)”}”(hhh]”(hº)”}”(hŒ"Configuration with tagging support”h]”hŒ"Configuration with tagging support”…””}”(hj”  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj‘  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.”…””}”(hj¢  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K#hj‘  hžhubhÊ)”}”(hŒ$See :ref:`dsa-tagged-configuration`.”h]”(hŒSee ”…””}”(hj°  hžhhŸNh Nubh)”}”(hŒ:ref:`dsa-tagged-configuration`”h]”jg  )”}”(hjº  h]”hŒdsa-tagged-configuration”…””}”(hj¼  hžhhŸNh Nubah}”(h]”h ]”(jr  Œstd”Œstd-ref”eh"]”h$]”h&]”uh1jf  hj¸  ubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”j  Œ	refdomain”jÆ  Œreftype”Œref”Œrefexplicit”‰Œrefwarn”ˆj…  Œdsa-tagged-configuration”uh1hhŸh³h K&hj°  ubhŒ.”…””}”(hj°  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K&hj‘  hžhubeh}”(h]”Œ"configuration-with-tagging-support”ah ]”h"]”Œ"configuration with tagging support”ah$]”h&]”uh1h´hhçhžhhŸh³h K!ubhµ)”}”(hhh]”(hº)”}”(hŒ%Configuration without tagging support”h]”hŒ%Configuration without tagging support”…””}”(hjí  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjê  hžhhŸh³h K)ubhÊ)”}”(hX  Older 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]”hX  Older 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jû  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K+hjê  hžhubhÊ)”}”(hŒIThe configuration slightly differ from the :ref:`dsa-vlan-configuration`.”h]”(hŒ+The configuration slightly differ from the ”…””}”(hj	  hžhhŸNh Nubh)”}”(hŒ:ref:`dsa-vlan-configuration`”h]”jg  )”}”(hj  h]”hŒdsa-vlan-configuration”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”(jr  Œstd”Œstd-ref”eh"]”h$]”h&]”uh1jf  hj  ubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”j  Œ	refdomain”j  Œreftype”Œref”Œrefexplicit”‰Œrefwarn”ˆj…  Œdsa-vlan-configuration”uh1hhŸh³h K0hj	  ubhŒ.”…””}”(hj	  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K0hjê  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.”…””}”(hj;  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K2hjê  hžhubhÊ)”}”(hX  In 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 ”…””}”(hjI  hžhhŸNh Nubh)”}”(hŒ:ref:`dsa-vlan-configuration`”h]”jg  )”}”(hjS  h]”hŒdsa-vlan-configuration”…””}”(hjU  hžhhŸNh Nubah}”(h]”h ]”(jr  Œstd”Œstd-ref”eh"]”h$]”h&]”uh1jf  hjQ  ubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”j  Œ	refdomain”j_  Œreftype”Œref”Œrefexplicit”‰Œrefwarn”ˆj…  Œdsa-vlan-configuration”uh1hhŸh³h K6hjI  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.”…””}”(hjI  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K6hjê  hžhubhµ)”}”(hhh]”(hº)”}”(hŒsingle port”h]”hŒsingle port”…””}”(hj~  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj{  hžhhŸh³h K<ubhÊ)”}”(hŒrThe configuration can only be set up via VLAN tagging and bridge setup.
By default packages are tagged with vid 1:”h]”hŒrThe configuration can only be set up via VLAN tagging and bridge setup.
By default packages are tagged with vid 1:”…””}”(hjŒ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K=hj{  hžhubhŒliteral_block”“”)”}”(hXþ  # tag traffic on CPU port
ip link add link eth0 name eth0.1 type vlan id 1
ip link add link eth0 name eth0.2 type vlan id 2
ip link add link eth0 name eth0.3 type vlan id 3

# The conduit interface needs to be brought up before the user ports.
ip link set eth0 up
ip link set eth0.1 up
ip link set eth0.2 up
ip link set eth0.3 up

# bring up the user interfaces
ip link set wan up
ip link set lan1 up
ip link set lan2 up

# create bridge
ip link add name br0 type bridge

# activate VLAN filtering
ip link set dev br0 type bridge vlan_filtering 1

# add ports to bridges
ip link set dev wan master br0
ip link set dev lan1 master br0
ip link set dev lan2 master br0

# tag traffic on ports
bridge vlan add dev lan1 vid 2 pvid untagged
bridge vlan del dev lan1 vid 1
bridge vlan add dev lan2 vid 3 pvid untagged
bridge vlan del dev lan2 vid 1

# configure the VLANs
ip addr add 192.0.2.1/30 dev eth0.1
ip addr add 192.0.2.5/30 dev eth0.2
ip addr add 192.0.2.9/30 dev eth0.3

# bring up the bridge devices
ip link set br0 up”h]”hXþ  # tag traffic on CPU port
ip link add link eth0 name eth0.1 type vlan id 1
ip link add link eth0 name eth0.2 type vlan id 2
ip link add link eth0 name eth0.3 type vlan id 3

# The conduit interface needs to be brought up before the user ports.
ip link set eth0 up
ip link set eth0.1 up
ip link set eth0.2 up
ip link set eth0.3 up

# bring up the user interfaces
ip link set wan up
ip link set lan1 up
ip link set lan2 up

# create bridge
ip link add name br0 type bridge

# activate VLAN filtering
ip link set dev br0 type bridge vlan_filtering 1

# add ports to bridges
ip link set dev wan master br0
ip link set dev lan1 master br0
ip link set dev lan2 master br0

# tag traffic on ports
bridge vlan add dev lan1 vid 2 pvid untagged
bridge vlan del dev lan1 vid 1
bridge vlan add dev lan2 vid 3 pvid untagged
bridge vlan del dev lan2 vid 1

# configure the VLANs
ip addr add 192.0.2.1/30 dev eth0.1
ip addr add 192.0.2.5/30 dev eth0.2
ip addr add 192.0.2.9/30 dev eth0.3

# bring up the bridge devices
ip link set br0 up”…””}”hjœ  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²Œforce”‰Œlanguage”Œsh”Œhighlight_args”}”uh1jš  hŸh³h K@hj{  hžhubeh}”(h]”Œsingle-port”ah ]”h"]”Œsingle port”ah$]”h&]”uh1h´hjê  hžhhŸh³h K<ubhµ)”}”(hhh]”(hº)”}”(hŒbridge”h]”hŒbridge”…””}”(hjº  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj·  hžhhŸh³h Kmubj›  )”}”(hX‘  # tag traffic on CPU port
ip link add link eth0 name eth0.1 type vlan id 1

# The conduit interface needs to be brought up before the user ports.
ip link set eth0 up
ip link set eth0.1 up

# bring up the user interfaces
ip link set wan up
ip link set lan1 up
ip link set lan2 up

# create bridge
ip link add name br0 type bridge

# activate VLAN filtering
ip link set dev br0 type bridge vlan_filtering 1

# add ports to bridge
ip link set dev wan master br0
ip link set dev lan1 master br0
ip link set dev lan2 master br0
ip link set eth0.1 master br0

# configure the bridge
ip addr add 192.0.2.129/25 dev br0

# bring up the bridge
ip link set dev br0 up”h]”hX‘  # tag traffic on CPU port
ip link add link eth0 name eth0.1 type vlan id 1

# The conduit interface needs to be brought up before the user ports.
ip link set eth0 up
ip link set eth0.1 up

# bring up the user interfaces
ip link set wan up
ip link set lan1 up
ip link set lan2 up

# create bridge
ip link add name br0 type bridge

# activate VLAN filtering
ip link set dev br0 type bridge vlan_filtering 1

# add ports to bridge
ip link set dev wan master br0
ip link set dev lan1 master br0
ip link set dev lan2 master br0
ip link set eth0.1 master br0

# configure the bridge
ip addr add 192.0.2.129/25 dev br0

# bring up the bridge
ip link set dev br0 up”…””}”hjÈ  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²jª  ‰j«  Œsh”j­  }”uh1jš  hŸh³h Kohj·  hžhubeh}”(h]”Œbridge”ah ]”h"]”Œbridge”ah$]”h&]”uh1h´hjê  hžhhŸh³h Kmubhµ)”}”(hhh]”(hº)”}”(hŒgateway”h]”hŒgateway”…””}”(hjã  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjà  hžhhŸh³h Kubj›  )”}”(hXb  # tag traffic on CPU port
ip link add link eth0 name eth0.1 type vlan id 1
ip link add link eth0 name eth0.2 type vlan id 2

# The conduit interface needs to be brought up before the user ports.
ip link set eth0 up
ip link set eth0.1 up
ip link set eth0.2 up

# bring up the user interfaces
ip link set wan up
ip link set lan1 up
ip link set lan2 up

# create bridge
ip link add name br0 type bridge

# activate VLAN filtering
ip link set dev br0 type bridge vlan_filtering 1

# add ports to bridges
ip link set dev wan master br0
ip link set eth0.1 master br0
ip link set dev lan1 master br0
ip link set dev lan2 master br0

# tag traffic on ports
bridge vlan add dev wan vid 2 pvid untagged
bridge vlan del dev wan vid 1

# configure the VLANs
ip addr add 192.0.2.1/30 dev eth0.2
ip addr add 192.0.2.129/25 dev br0

# bring up the bridge devices
ip link set br0 up”h]”hXb  # tag traffic on CPU port
ip link add link eth0 name eth0.1 type vlan id 1
ip link add link eth0 name eth0.2 type vlan id 2

# The conduit interface needs to be brought up before the user ports.
ip link set eth0 up
ip link set eth0.1 up
ip link set eth0.2 up

# bring up the user interfaces
ip link set wan up
ip link set lan1 up
ip link set lan2 up

# create bridge
ip link add name br0 type bridge

# activate VLAN filtering
ip link set dev br0 type bridge vlan_filtering 1

# add ports to bridges
ip link set dev wan master br0
ip link set eth0.1 master br0
ip link set dev lan1 master br0
ip link set dev lan2 master br0

# tag traffic on ports
bridge vlan add dev wan vid 2 pvid untagged
bridge vlan del dev wan vid 1

# configure the VLANs
ip addr add 192.0.2.1/30 dev eth0.2
ip addr add 192.0.2.129/25 dev br0

# bring up the bridge devices
ip link set br0 up”…””}”hjñ  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²jª  ‰j«  Œsh”j­  }”uh1jš  hŸh³h K’hjà  hžhubeh}”(h]”Œgateway”ah ]”h"]”Œgateway”ah$]”h&]”uh1h´hjê  hžhhŸh³h Kubeh}”(h]”Œ%configuration-without-tagging-support”ah ]”h"]”Œ%configuration without tagging support”ah$]”h&]”uh1h´hhçhžhhŸh³h K)ubeh}”(h]”Œimplementation-details”ah ]”h"]”Œimplementation details”ah$]”h&]”uh1h´hh¶hžhhŸh³h Kubeh}”(h]”Œ*broadcom-roboswitch-ethernet-switch-driver”ah ]”h"]”Œ*broadcom roboswitch ethernet switch driver”ah$]”h&]”uh1h´hhhžhhŸh³h Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”h³uh1hŒcurrent_source”NŒcurrent_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(h¹NŒ	generator”NŒ	datestamp”NŒsource_link”NŒ
source_url”NŒtoc_backlinks”Œentry”Œfootnote_backlinks”KŒsectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒstrip_classes”NŒreport_level”KŒ
halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ	traceback”ˆŒinput_encoding”Œ	utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”jD  Œerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œlanguage_code”Œen”Œrecord_dependencies”NŒconfig”NŒ	id_prefix”hŒauto_id_prefix”Œid”Œdump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”h³Œ_destination”NŒ_config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒraw_enabled”KŒline_length_limit”M'Œpep_references”NŒpep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒrfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ	tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œsmart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œdocinfo_xform”KŒsectsubtitle_xform”‰Œimage_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”(j  j  j  j  jç  jä  j  j  j´  j±  jÝ  jÚ  j  j  uŒ	nametypes”}”(j  ‰j  ‰jç  ‰j  ‰j´  ‰jÝ  ‰j  ‰uh}”(j  h¶j  hçjä  j‘  j  jê  j±  j{  jÚ  j·  j  jà  uŒfootnote_refs”}”Œcitation_refs”}”Œautofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ	footnotes”]”Œ	citations”]”Œautofootnote_start”KŒsymbol_footnote_start”K Œ
id_counter”Œcollections”ŒCounter”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”Œtransformer”NŒinclude_log”]”Œ
decoration”Nhžhub.