€•·ZŒ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”Œ0/translations/zh_CN/driver-api/men-chameleon-bus”Œmodname”NŒ classname”NŒ refexplicit”ˆuŒtagname”hhh ubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ0/translations/zh_TW/driver-api/men-chameleon-bus”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ0/translations/it_IT/driver-api/men-chameleon-bus”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ0/translations/ja_JP/driver-api/men-chameleon-bus”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ0/translations/ko_KR/driver-api/men-chameleon-bus”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒPortuguese (Brazilian)”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ0/translations/pt_BR/driver-api/men-chameleon-bus”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒSpanish”…””}”hh–sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ0/translations/sp_SP/driver-api/men-chameleon-bus”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h hhŒ _document”hŒsource”NŒline”NubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒMEN Chameleon Bus”h]”hŒMEN Chameleon Bus”…””}”(hh¼h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhh·h²hh³ŒJ/var/lib/git/docbuild/linux/Documentation/driver-api/men-chameleon-bus.rst”h´KubhŒcomment”“”)”}”(hX’Table of Contents ================= 1 Introduction 1.1 Scope of this Document 1.2 Limitations of the current implementation 2 Architecture 2.1 MEN Chameleon Bus 2.2 Carrier Devices 2.3 Parser 3 Resource handling 3.1 Memory Resources 3.2 IRQs 4 Writing an MCB driver 4.1 The driver structure 4.2 Probing and attaching 4.3 Initializing the driver 4.4 Using DMA”h]”hX’Table of Contents ================= 1 Introduction 1.1 Scope of this Document 1.2 Limitations of the current implementation 2 Architecture 2.1 MEN Chameleon Bus 2.2 Carrier Devices 2.3 Parser 3 Resource handling 3.1 Memory Resources 3.2 IRQs 4 Writing an MCB driver 4.1 The driver structure 4.2 Probing and attaching 4.3 Initializing the driver 4.4 Using DMA”…””}”hhÍsbah}”(h]”h ]”h"]”h$]”h&]”Œ xml:space”Œpreserve”uh1hËhh·h²hh³hÊh´Kubh¶)”}”(hhh]”(h»)”}”(hŒ Introduction”h]”hŒ Introduction”…””}”(hhàh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhhÝh²hh³hÊh´KubhŒ paragraph”“”)”}”(hŒ{This document describes the architecture and implementation of the MEN Chameleon Bus (called MCB throughout this document).”h]”hŒ{This document describes the architecture and implementation of the MEN Chameleon Bus (called MCB throughout this document).”…””}”(hhðh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÊh´KhhÝh²hubh¶)”}”(hhh]”(h»)”}”(hŒScope of this Document”h]”hŒScope of this Document”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhhþh²hh³hÊh´Kubhï)”}”(hŒThis document is intended to be a short overview of the current implementation and does by no means describe the complete possibilities of MCB based devices.”h]”hŒThis document is intended to be a short overview of the current implementation and does by no means describe the complete possibilities of MCB based devices.”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÊh´K!hhþh²hubeh}”(h]”Œscope-of-this-document”ah ]”h"]”Œscope of this document”ah$]”h&]”uh1hµhhÝh²hh³hÊh´Kubh¶)”}”(hhh]”(h»)”}”(hŒ)Limitations of the current implementation”h]”hŒ)Limitations of the current implementation”…””}”(hj(h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj%h²hh³hÊh´K&ubhï)”}”(hŒ¦The current implementation is limited to PCI and PCIe based carrier devices that only use a single memory resource and share the PCI legacy IRQ. Not implemented are:”h]”hŒ¦The current implementation is limited to PCI and PCIe based carrier devices that only use a single memory resource and share the PCI legacy IRQ. Not implemented are:”…””}”(hj6h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÊh´K(hj%h²hubhŒ bullet_list”“”)”}”(hhh]”(hŒ list_item”“”)”}”(hŒGMulti-resource MCB devices like the VME Controller or M-Module carrier.”h]”hï)”}”(hjMh]”hŒGMulti-resource MCB devices like the VME Controller or M-Module carrier.”…””}”(hjOh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÊh´K,hjKubah}”(h]”h ]”h"]”h$]”h&]”uh1jIhjFh²hh³hÊh´NubjJ)”}”(hŒƒMCB devices that need another MCB device, like SRAM for a DMA Controller's buffer descriptors or a video controller's video memory.”h]”hï)”}”(hŒƒMCB devices that need another MCB device, like SRAM for a DMA Controller's buffer descriptors or a video controller's video memory.”h]”hŒ‡MCB devices that need another MCB device, like SRAM for a DMA Controller’s buffer descriptors or a video controller’s video memory.”…””}”(hjfh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÊh´K-hjbubah}”(h]”h ]”h"]”h$]”h&]”uh1jIhjFh²hh³hÊh´NubjJ)”}”(hŒA per-carrier IRQ domain for carrier devices that have one (or more) IRQs per MCB device like PCIe based carriers with MSI or MSI-X support. ”h]”hï)”}”(hŒŒA per-carrier IRQ domain for carrier devices that have one (or more) IRQs per MCB device like PCIe based carriers with MSI or MSI-X support.”h]”hŒŒA per-carrier IRQ domain for carrier devices that have one (or more) IRQs per MCB device like PCIe based carriers with MSI or MSI-X support.”…””}”(hj~h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÊh´K/hjzubah}”(h]”h ]”h"]”h$]”h&]”uh1jIhjFh²hh³hÊh´Nubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ-”uh1jDh³hÊh´K,hj%h²hubeh}”(h]”Œ)limitations-of-the-current-implementation”ah ]”h"]”Œ)limitations of the current implementation”ah$]”h&]”uh1hµhhÝh²hh³hÊh´K&ubeh}”(h]”Œ introduction”ah ]”h"]”Œ introduction”ah$]”h&]”uh1hµhh·h²hh³hÊh´Kubh¶)”}”(hhh]”(h»)”}”(hŒ Architecture”h]”hŒ Architecture”…””}”(hj­h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjªh²hh³hÊh´K3ubhï)”}”(hŒ(MCB is divided into 3 functional blocks:”h]”hŒ(MCB is divided into 3 functional blocks:”…””}”(hj»h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÊh´K5hjªh²hubjE)”}”(hhh]”(jJ)”}”(hŒThe MEN Chameleon Bus itself,”h]”hï)”}”(hjÎh]”hŒThe MEN Chameleon Bus itself,”…””}”(hjÐh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÊh´K7hjÌubah}”(h]”h ]”h"]”h$]”h&]”uh1jIhjÉh²hh³hÊh´NubjJ)”}”(hŒ#drivers for MCB Carrier Devices and”h]”hï)”}”(hjåh]”hŒ#drivers for MCB Carrier Devices and”…””}”(hjçh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÊh´K8hjãubah}”(h]”h ]”h"]”h$]”h&]”uh1jIhjÉh²hh³hÊh´NubjJ)”}”(hŒ$the parser for the Chameleon table. ”h]”hï)”}”(hŒ#the parser for the Chameleon table.”h]”hŒ#the parser for the Chameleon table.”…””}”(hjþh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÊh´K9hjúubah}”(h]”h ]”h"]”h$]”h&]”uh1jIhjÉh²hh³hÊh´Nubeh}”(h]”h ]”h"]”h$]”h&]”j˜j™uh1jDh³hÊh´K7hjªh²hubh¶)”}”(hhh]”(h»)”}”(hŒMEN Chameleon Bus”h]”hŒMEN Chameleon Bus”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjh²hh³hÊh´Khjh²hubeh}”(h]”Œid1”ah ]”h"]”h$]”Œmen chameleon bus”ah&]”uh1hµhjªh²hh³hÊh´K<Œ referenced”Kubh¶)”}”(hhh]”(h»)”}”(hŒCarrier Devices”h]”hŒCarrier Devices”…””}”(hjCh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj@h²hh³hÊh´KHubhï)”}”(hX:A carrier device is just an abstraction for the real world physical bus the Chameleon FPGA is attached to. Some IP Core drivers may need to interact with properties of the carrier device (like querying the IRQ number of a PCI device). To provide abstraction from the real hardware bus, an MCB carrier device provides callback methods to translate the driver's MCB function calls to hardware related function calls. For example a carrier device may implement the get_irq() method which can be translated into a hardware bus query for the IRQ number the device should use.”h]”hX<A carrier device is just an abstraction for the real world physical bus the Chameleon FPGA is attached to. Some IP Core drivers may need to interact with properties of the carrier device (like querying the IRQ number of a PCI device). To provide abstraction from the real hardware bus, an MCB carrier device provides callback methods to translate the driver’s MCB function calls to hardware related function calls. For example a carrier device may implement the get_irq() method which can be translated into a hardware bus query for the IRQ number the device should use.”…””}”(hjQh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÊh´KJhj@h²hubeh}”(h]”Œcarrier-devices”ah ]”h"]”Œcarrier devices”ah$]”h&]”uh1hµhjªh²hh³hÊh´KHubh¶)”}”(hhh]”(h»)”}”(hŒParser”h]”hŒParser”…””}”(hjjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjgh²hh³hÊh´KTubhï)”}”(hXThe parser reads the first 512 bytes of a Chameleon device and parses the Chameleon table. Currently the parser only supports the Chameleon v2 variant of the Chameleon table but can easily be adopted to support an older or possible future variant. While parsing the table's entries new MCB devices are allocated and their resources are assigned according to the resource assignment in the Chameleon table. After resource assignment is finished, the MCB devices are registered at the MCB and thus at the driver core of the Linux kernel.”h]”hXThe parser reads the first 512 bytes of a Chameleon device and parses the Chameleon table. Currently the parser only supports the Chameleon v2 variant of the Chameleon table but can easily be adopted to support an older or possible future variant. While parsing the table’s entries new MCB devices are allocated and their resources are assigned according to the resource assignment in the Chameleon table. After resource assignment is finished, the MCB devices are registered at the MCB and thus at the driver core of the Linux kernel.”…””}”(hjxh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÊh´KVhjgh²hubeh}”(h]”Œparser”ah ]”h"]”Œparser”ah$]”h&]”uh1hµhjªh²hh³hÊh´KTubeh}”(h]”Œ architecture”ah ]”h"]”Œ architecture”ah$]”h&]”uh1hµhh·h²hh³hÊh´K3ubh¶)”}”(hhh]”(h»)”}”(hŒResource handling”h]”hŒResource handling”…””}”(hj™h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj–h²hh³hÊh´K`ubhï)”}”(hŒŒThe current implementation assigns exactly one memory and one IRQ resource per MCB device. But this is likely going to change in the future.”h]”hŒŒThe current implementation assigns exactly one memory and one IRQ resource per MCB device. But this is likely going to change in the future.”…””}”(hj§h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÊh´Kbhj–h²hubh¶)”}”(hhh]”(h»)”}”(hŒMemory Resources”h]”hŒMemory Resources”…””}”(hj¸h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjµh²hh³hÊh´Kfubhï)”}”(hX+Each MCB device has exactly one memory resource, which can be requested from the MCB bus. This memory resource is the physical address of the MCB device inside the carrier and is intended to be passed to ioremap() and friends. It is already requested from the kernel by calling request_mem_region().”h]”hX+Each MCB device has exactly one memory resource, which can be requested from the MCB bus. This memory resource is the physical address of the MCB device inside the carrier and is intended to be passed to ioremap() and friends. It is already requested from the kernel by calling request_mem_region().”…””}”(hjÆh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÊh´Khhjµh²hubeh}”(h]”Œmemory-resources”ah ]”h"]”Œmemory resources”ah$]”h&]”uh1hµhj–h²hh³hÊh´Kfubh¶)”}”(hhh]”(h»)”}”(hŒIRQs”h]”hŒIRQs”…””}”(hjßh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjÜh²hh³hÊh´Knubhï)”}”(hXZEach MCB device has exactly one IRQ resource, which can be requested from the MCB bus. If a carrier device driver implements the ->get_irq() callback method, the IRQ number assigned by the carrier device will be returned, otherwise the IRQ number inside the Chameleon table will be returned. This number is suitable to be passed to request_irq().”h]”hXZEach MCB device has exactly one IRQ resource, which can be requested from the MCB bus. If a carrier device driver implements the ->get_irq() callback method, the IRQ number assigned by the carrier device will be returned, otherwise the IRQ number inside the Chameleon table will be returned. This number is suitable to be passed to request_irq().”…””}”(hjíh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÊh´KphjÜh²hubeh}”(h]”Œirqs”ah ]”h"]”Œirqs”ah$]”h&]”uh1hµhj–h²hh³hÊh´Knubeh}”(h]”Œresource-handling”ah ]”h"]”Œresource handling”ah$]”h&]”uh1hµhh·h²hh³hÊh´K`ubh¶)”}”(hhh]”(h»)”}”(hŒWriting an MCB driver”h]”hŒWriting an MCB driver”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj h²hh³hÊh´Kwubh¶)”}”(hhh]”(h»)”}”(hŒThe driver structure”h]”hŒThe driver structure”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjh²hh³hÊh´Kzubhï)”}”(hŒôEach MCB driver has a structure to identify the device driver as well as device ids which identify the IP Core inside the FPGA. The driver structure also contains callback methods which get executed on driver probe and removal from the system::”h]”hŒóEach MCB driver has a structure to identify the device driver as well as device ids which identify the IP Core inside the FPGA. The driver structure also contains callback methods which get executed on driver probe and removal from the system:”…””}”(hj-h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÊh´K|hjh²hubhŒ literal_block”“”)”}”(hXHstatic const struct mcb_device_id foo_ids[] = { { .device = 0x123 }, { } }; MODULE_DEVICE_TABLE(mcb, foo_ids); static struct mcb_driver foo_driver = { driver = { .name = "foo-bar", .owner = THIS_MODULE, }, .probe = foo_probe, .remove = foo_remove, .id_table = foo_ids, };”h]”hXHstatic const struct mcb_device_id foo_ids[] = { { .device = 0x123 }, { } }; MODULE_DEVICE_TABLE(mcb, foo_ids); static struct mcb_driver foo_driver = { driver = { .name = "foo-bar", .owner = THIS_MODULE, }, .probe = foo_probe, .remove = foo_remove, .id_table = foo_ids, };”…””}”hj=sbah}”(h]”h ]”h"]”h$]”h&]”hÛhÜuh1j;h³hÊh´Khjh²hubeh}”(h]”Œthe-driver-structure”ah ]”h"]”Œthe driver structure”ah$]”h&]”uh1hµhj h²hh³hÊh´Kzubh¶)”}”(hhh]”(h»)”}”(hŒProbing and attaching”h]”hŒProbing and attaching”…””}”(hjVh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjSh²hh³hÊh´K’ubhï)”}”(hŒæWhen a driver is loaded and the MCB devices it services are found, the MCB core will call the driver's probe callback method. When the driver is removed from the system, the MCB core will call the driver's remove callback method::”h]”hŒéWhen a driver is loaded and the MCB devices it services are found, the MCB core will call the driver’s probe callback method. When the driver is removed from the system, the MCB core will call the driver’s remove callback method:”…””}”(hjdh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÊh´K”hjSh²hubj<)”}”(hŒ€static init foo_probe(struct mcb_device *mdev, const struct mcb_device_id *id); static void foo_remove(struct mcb_device *mdev);”h]”hŒ€static init foo_probe(struct mcb_device *mdev, const struct mcb_device_id *id); static void foo_remove(struct mcb_device *mdev);”…””}”hjrsbah}”(h]”h ]”h"]”h$]”h&]”hÛhÜuh1j;h³hÊh´K˜hjSh²hubeh}”(h]”Œprobing-and-attaching”ah ]”h"]”Œprobing and attaching”ah$]”h&]”uh1hµhj h²hh³hÊh´K’ubh¶)”}”(hhh]”(h»)”}”(hŒInitializing the driver”h]”hŒInitializing the driver”…””}”(hj‹h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjˆh²hh³hÊh´Kœubhï)”}”(hŒ±When the kernel is booted or your foo driver module is inserted, you have to perform driver initialization. Usually it is enough to register your driver module at the MCB core::”h]”hŒ°When the kernel is booted or your foo driver module is inserted, you have to perform driver initialization. Usually it is enough to register your driver module at the MCB core:”…””}”(hj™h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÊh´Kžhjˆh²hubj<)”}”(hŒÖstatic int __init foo_init(void) { return mcb_register_driver(&foo_driver); } module_init(foo_init); static void __exit foo_exit(void) { mcb_unregister_driver(&foo_driver); } module_exit(foo_exit);”h]”hŒÖstatic int __init foo_init(void) { return mcb_register_driver(&foo_driver); } module_init(foo_init); static void __exit foo_exit(void) { mcb_unregister_driver(&foo_driver); } module_exit(foo_exit);”…””}”hj§sbah}”(h]”h ]”h"]”h$]”h&]”hÛhÜuh1j;h³hÊh´K¢hjˆh²hubhï)”}”(hŒDThe module_mcb_driver() macro can be used to reduce the above code::”h]”hŒCThe module_mcb_driver() macro can be used to reduce the above code:”…””}”(hjµh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÊh´K®hjˆh²hubj<)”}”(hŒmodule_mcb_driver(foo_driver);”h]”hŒmodule_mcb_driver(foo_driver);”…””}”hjÃsbah}”(h]”h ]”h"]”h$]”h&]”hÛhÜuh1j;h³hÊh´K°hjˆh²hubeh}”(h]”Œinitializing-the-driver”ah ]”h"]”Œinitializing the driver”ah$]”h&]”uh1hµhj h²hh³hÊh´Kœubh¶)”}”(hhh]”(h»)”}”(hŒ Using DMA”h]”hŒ Using DMA”…””}”(hjÜh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjÙh²hh³hÊh´K³ubhï)”}”(hŒÒTo make use of the kernel's DMA-API's function, you will need to use the carrier device's 'struct device'. Fortunately 'struct mcb_device' embeds a pointer (->dma_dev) to the carrier's device for DMA purposes::”h]”hŒáTo make use of the kernel’s DMA-API’s function, you will need to use the carrier device’s ‘struct device’. Fortunately ‘struct mcb_device’ embeds a pointer (->dma_dev) to the carrier’s device for DMA purposes:”…””}”(hjêh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÊh´KµhjÙh²hubj<)”}”(hŒlret = dma_set_mask_and_coherent(&mdev->dma_dev, DMA_BIT_MASK(dma_bits)); if (rc) /* Handle errors */”h]”hŒlret = dma_set_mask_and_coherent(&mdev->dma_dev, DMA_BIT_MASK(dma_bits)); if (rc) /* Handle errors */”…””}”hjøsbah}”(h]”h ]”h"]”h$]”h&]”hÛhÜuh1j;h³hÊh´K¹hjÙh²hubeh}”(h]”Œ using-dma”ah ]”h"]”Œ using dma”ah$]”h&]”uh1hµhj h²hh³hÊh´K³ubeh}”(h]”Œwriting-an-mcb-driver”ah ]”h"]”Œwriting an mcb driver”ah$]”h&]”uh1hµhh·h²hh³hÊh´Kwubeh}”(h]”Œmen-chameleon-bus”ah ]”h"]”h$]”j=ah&]”uh1hµhhh²hh³hÊh´Kj?Kubeh}”(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”j@Œ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”}”(Œmen chameleon bus”Nj§j¤j"jjŸjœj“jjdjaj‹jˆjjjÙjÖjjýjjjPjMj…j‚jÖjÓj juŒ nametypes”}”(j„‰j§‰j"‰jŸ‰j“‰jd‰j‹‰j‰jÙ‰j‰j‰jP‰j…‰jÖ‰j ‰uh}”(jh·j¤hÝjhþjœj%jjªj9jjaj@jˆjgjj–jÖjµjýjÜjj jMjj‚jSjÓjˆjjÙ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”“”}”jNKs…”R”Œparse_messages”]”hŒsystem_message”“”)”}”(hhh]”hï)”}”(hŒ4Duplicate implicit target name: "men chameleon bus".”h]”hŒ8Duplicate implicit target name: “men chameleon busâ€.”…””}”(hj¨h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîhj¥ubah}”(h]”h ]”h"]”h$]”h&]”j9aŒlevel”KŒtype”ŒINFO”Œsource”hÊŒline”K