€•Ì Œ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/gpu/introduction”Œ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/gpu/introduction”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ$/translations/it_IT/gpu/introduction”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ$/translations/ja_JP/gpu/introduction”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ$/translations/ko_KR/gpu/introduction”Œ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/gpu/introduction”Œ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Œ Introduction”h]”hŒ Introduction”…””}”(hh¨hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hh£hžhhŸŒ>/var/lib/git/docbuild/linux/Documentation/gpu/introduction.rst”h KubhŒ paragraph”“”)”}”(hXfThe Linux DRM layer contains code intended to support the needs of complex graphics devices, usually containing programmable pipelines well suited to 3D graphics acceleration. Graphics drivers in the kernel may make use of DRM functions to make tasks like memory management, interrupt handling and DMA easier, and provide a uniform interface to applications.”h]”hXfThe Linux DRM layer contains code intended to support the needs of complex graphics devices, usually containing programmable pipelines well suited to 3D graphics acceleration. Graphics drivers in the kernel may make use of DRM functions to make tasks like memory management, interrupt handling and DMA easier, and provide a uniform interface to applications.”…””}”(hh¹hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khh£hžhubh¸)”}”(hŒîA note on versions: this guide covers features found in the DRM tree, including the TTM memory manager, output configuration and mode setting, and the new vblank internals, in addition to all the regular features found in current kernels.”h]”hŒîA note on versions: this guide covers features found in the DRM tree, including the TTM memory manager, output configuration and mode setting, and the new vblank internals, in addition to all the regular features found in current kernels.”…””}”(hhÇhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K hh£hžhubh¸)”}”(hŒ*[Insert diagram of typical DRM stack here]”h]”hŒ*[Insert diagram of typical DRM stack here]”…””}”(hhÕhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khh£hžhubh¢)”}”(hhh]”(h§)”}”(hŒStyle Guidelines”h]”hŒStyle Guidelines”…””}”(hhæhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hhãhžhhŸh¶h Kubh¸)”}”(hX¶For consistency this documentation uses American English. Abbreviations are written as all-uppercase, for example: DRM, KMS, IOCTL, CRTC, and so on. To aid in reading, documentations make full use of the markup characters kerneldoc provides: @parameter for function parameters, @member for structure members (within the same structure), &struct structure to reference structures and function() for functions. These all get automatically hyperlinked if kerneldoc for the referenced objects exists. When referencing entries in function vtables (and structure members in general) please use &vtable_name.vfunc. Unfortunately this does not yet yield a direct link to the member, only the structure.”h]”hX¶For consistency this documentation uses American English. Abbreviations are written as all-uppercase, for example: DRM, KMS, IOCTL, CRTC, and so on. To aid in reading, documentations make full use of the markup characters kerneldoc provides: @parameter for function parameters, @member for structure members (within the same structure), &struct structure to reference structures and function() for functions. These all get automatically hyperlinked if kerneldoc for the referenced objects exists. When referencing entries in function vtables (and structure members in general) please use &vtable_name.vfunc. Unfortunately this does not yet yield a direct link to the member, only the structure.”…””}”(hhôhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khhãhžhubh¸)”}”(hX©Except in special situations (to separate locked from unlocked variants) locking requirements for functions aren't documented in the kerneldoc. Instead locking should be check at runtime using e.g. ``WARN_ON(!mutex_is_locked(...));``. Since it's much easier to ignore documentation than runtime noise this provides more value. And on top of that runtime checks do need to be updated when the locking rules change, increasing the chances that they're correct. Within the documentation the locking rules should be explained in the relevant structures: Either in the comment for the lock explaining what it protects, or data fields need a note about which lock protects them, or both.”h]”(hŒÈExcept in special situations (to separate locked from unlocked variants) locking requirements for functions aren’t documented in the kerneldoc. Instead locking should be check at runtime using e.g. ”…””}”(hjhžhhŸNh NubhŒliteral”“”)”}”(hŒ#``WARN_ON(!mutex_is_locked(...));``”h]”hŒWARN_ON(!mutex_is_locked(...));”…””}”(hj hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j hjubhXÄ. Since it’s much easier to ignore documentation than runtime noise this provides more value. And on top of that runtime checks do need to be updated when the locking rules change, increasing the chances that they’re correct. Within the documentation the locking rules should be explained in the relevant structures: Either in the comment for the lock explaining what it protects, or data fields need a note about which lock protects them, or both.”…””}”(hjhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K!hhãhžhubh¸)”}”(hXÞFunctions which have a non-\ ``void`` return value should have a section called "Returns" explaining the expected return values in different cases and their meanings. Currently there's no consensus whether that section name should be all upper-case or not, and whether it should end in a colon or not. Go with the file-local style. Other common section names are "Notes" with information for dangerous or tricky corner cases, and "FIXME" where the interface could be cleaned up.”h]”(hŒFunctions which have a non- ”…””}”(hj$hžhhŸNh Nubj )”}”(hŒ``void``”h]”hŒvoid”…””}”(hj,hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j hj$ubhXÇ return value should have a section called “Returns†explaining the expected return values in different cases and their meanings. Currently there’s no consensus whether that section name should be all upper-case or not, and whether it should end in a colon or not. Go with the file-local style. Other common section names are “Notes†with information for dangerous or tricky corner cases, and “FIXME†where the interface could be cleaned up.”…””}”(hj$hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K,hhãhžhubh¸)”}”(hŒRAlso read the :ref:`guidelines for the kernel documentation at large `.”h]”(hŒAlso read the ”…””}”(hjDhžhhŸNh Nubh)”}”(hŒC:ref:`guidelines for the kernel documentation at large `”h]”hŒinline”“”)”}”(hjNh]”hŒ0guidelines for the kernel documentation at large”…””}”(hjRhžhhŸNh Nubah}”(h]”h ]”(Œxref”Œstd”Œstd-ref”eh"]”h$]”h&]”uh1jPhjLubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”Œgpu/introduction”Œ refdomain”j]Œreftype”Œref”Œ refexplicit”ˆŒrefwarn”ˆŒ reftarget”Œ doc_guide”uh1hhŸh¶h K4hjDubhŒ.”…””}”(hjDhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K4hhãhžhubh¢)”}”(hhh]”(h§)”}”(hŒ#Documentation Requirements for kAPI”h]”hŒ#Documentation Requirements for kAPI”…””}”(hj~hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj{hžhhŸh¶h K7ubh¸)”}”(hXAll kernel APIs exported to other modules must be documented, including their datastructures and at least a short introductory section explaining the overall concepts. Documentation should be put into the code itself as kerneldoc comments as much as reasonable.”h]”hXAll kernel APIs exported to other modules must be documented, including their datastructures and at least a short introductory section explaining the overall concepts. Documentation should be put into the code itself as kerneldoc comments as much as reasonable.”…””}”(hjŒhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K9hj{hžhubh¸)”}”(hXâDo not blindly document everything, but document only what's relevant for driver authors: Internal functions of drm.ko and definitely static functions should not have formal kerneldoc comments. Use normal C comments if you feel like a comment is warranted. You may use kerneldoc syntax in the comment, but it shall not start with a /** kerneldoc marker. Similar for data structures, annotate anything entirely private with ``/* private: */`` comments as per the documentation guide.”h]”(hX©Do not blindly document everything, but document only what’s relevant for driver authors: Internal functions of drm.ko and definitely static functions should not have formal kerneldoc comments. Use normal C comments if you feel like a comment is warranted. You may use kerneldoc syntax in the comment, but it shall not start with a /** kerneldoc marker. Similar for data structures, annotate anything entirely private with ”…””}”(hjšhžhhŸNh Nubj )”}”(hŒ``/* private: */``”h]”hŒ/* private: */”…””}”(hj¢hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j hjšubhŒ) comments as per the documentation guide.”…””}”(hjšhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K>hj{hžhubeh}”(h]”Œ#documentation-requirements-for-kapi”ah ]”h"]”Œ#documentation requirements for kapi”ah$]”h&]”uh1h¡hhãhžhhŸh¶h K7ubeh}”(h]”Œstyle-guidelines”ah ]”h"]”Œstyle guidelines”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Kubh¢)”}”(hhh]”(h§)”}”(hŒGetting Started”h]”hŒGetting Started”…””}”(hjÍhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjÊhžhhŸh¶h KGubh¸)”}”(hŒÐDevelopers interested in helping out with the DRM subsystem are very welcome. Often people will resort to sending in patches for various issues reported by checkpatch or sparse. We welcome such contributions.”h]”hŒÐDevelopers interested in helping out with the DRM subsystem are very welcome. Often people will resort to sending in patches for various issues reported by checkpatch or sparse. We welcome such contributions.”…””}”(hjÛhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KIhjÊhžhubh¸)”}”(hŒhAnyone looking to kick it up a notch can find a list of janitorial tasks on the :ref:`TODO list `.”h]”(hŒPAnyone looking to kick it up a notch can find a list of janitorial tasks on the ”…””}”(hjéhžhhŸNh Nubh)”}”(hŒ:ref:`TODO list `”h]”jQ)”}”(hjóh]”hŒ TODO list”…””}”(hjõhžhhŸNh Nubah}”(h]”h ]”(j\Œstd”Œstd-ref”eh"]”h$]”h&]”uh1jPhjñubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”jiŒ refdomain”jÿŒreftype”Œref”Œ refexplicit”ˆŒrefwarn”ˆjoŒtodo”uh1hhŸh¶h KMhjéubhŒ.”…””}”(hjéhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KMhjÊhžhubeh}”(h]”Œgetting-started”ah ]”h"]”Œgetting started”ah$]”h&]”uh1h¡hh£hžhhŸh¶h KGubh¢)”}”(hhh]”(h§)”}”(hŒContribution Process”h]”hŒContribution Process”…””}”(hj&hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj#hžhhŸh¶h KQubh¸)”}”(hŒâMostly the DRM subsystem works like any other kernel subsystem, see :ref:`the main process guidelines and documentation ` for how things work. Here we just document some of the specialities of the GPU subsystem.”h]”(hŒDMostly the DRM subsystem works like any other kernel subsystem, see ”…””}”(hj4hžhhŸNh Nubh)”}”(hŒD:ref:`the main process guidelines and documentation `”h]”jQ)”}”(hj>h]”hŒ-the main process guidelines and documentation”…””}”(hj@hžhhŸNh Nubah}”(h]”h ]”(j\Œstd”Œstd-ref”eh"]”h$]”h&]”uh1jPhj<ubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”jiŒ refdomain”jJŒreftype”Œref”Œ refexplicit”ˆŒrefwarn”ˆjoŒ process_index”uh1hhŸh¶h KShj4ubhŒZ for how things work. Here we just document some of the specialities of the GPU subsystem.”…””}”(hj4hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KShj#hžhubh¢)”}”(hhh]”(h§)”}”(hŒFeature Merge Deadlines”h]”hŒFeature Merge Deadlines”…””}”(hjihžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjfhžhhŸh¶h KXubh¸)”}”(hXAAll feature work must be in the linux-next tree by the -rc6 release of the current release cycle, otherwise they must be postponed and can't reach the next merge window. All patches must have landed in the drm-next tree by latest -rc7, but if your branch is not in linux-next then this must have happened by -rc6 already.”h]”hXCAll feature work must be in the linux-next tree by the -rc6 release of the current release cycle, otherwise they must be postponed and can’t reach the next merge window. All patches must have landed in the drm-next tree by latest -rc7, but if your branch is not in linux-next then this must have happened by -rc6 already.”…””}”(hjwhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KZhjfhžhubh¸)”}”(hŒ¨After that point only bugfixes (like after the upstream merge window has closed with the -rc1 release) are allowed. No new platform enabling or new drivers are allowed.”h]”hŒ¨After that point only bugfixes (like after the upstream merge window has closed with the -rc1 release) are allowed. No new platform enabling or new drivers are allowed.”…””}”(hj…hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K`hjfhžhubh¸)”}”(hX%This means that there's a blackout-period of about one month where feature work can't be merged. The recommended way to deal with that is having a -next tree that's always open, but making sure to not feed it into linux-next during the blackout period. As an example, drm-misc works like that.”h]”hX+This means that there’s a blackout-period of about one month where feature work can’t be merged. The recommended way to deal with that is having a -next tree that’s always open, but making sure to not feed it into linux-next during the blackout period. As an example, drm-misc works like that.”…””}”(hj“hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kdhjfhžhubeh}”(h]”Œfeature-merge-deadlines”ah ]”h"]”Œfeature merge deadlines”ah$]”h&]”uh1h¡hj#hžhhŸh¶h KXubh¢)”}”(hhh]”(h§)”}”(hŒCode of Conduct”h]”hŒCode of Conduct”…””}”(hj¬hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj©hžhhŸh¶h Kjubh¸)”}”(hŒšAs a freedesktop.org project, dri-devel, and the DRM community, follows the Contributor Covenant, found at: https://www.freedesktop.org/wiki/CodeOfConduct”h]”(hŒlAs a freedesktop.org project, dri-devel, and the DRM community, follows the Contributor Covenant, found at: ”…””}”(hjºhžhhŸNh NubhŒ reference”“”)”}”(hŒ.https://www.freedesktop.org/wiki/CodeOfConduct”h]”hŒ.https://www.freedesktop.org/wiki/CodeOfConduct”…””}”(hjÄhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”jÆuh1jÂhjºubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Klhj©hžhubh¸)”}”(hXPlease conduct yourself in a respectful and civilised manner when interacting with community members on mailing lists, IRC, or bug trackers. The community represents the project as a whole, and abusive or bullying behaviour is not tolerated by the project.”h]”hXPlease conduct yourself in a respectful and civilised manner when interacting with community members on mailing lists, IRC, or bug trackers. The community represents the project as a whole, and abusive or bullying behaviour is not tolerated by the project.”…””}”(hjÙhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kohj©hžhubeh}”(h]”Œcode-of-conduct”ah ]”h"]”Œcode of conduct”ah$]”h&]”uh1h¡hj#hžhhŸh¶h Kjubeh}”(h]”Œcontribution-process”ah ]”h"]”Œcontribution process”ah$]”h&]”uh1h¡hh£hžhhŸh¶h KQubh¢)”}”(hhh]”(h§)”}”(hŒ%Simple DRM drivers to use as examples”h]”hŒ%Simple DRM drivers to use as examples”…””}”(hjúhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj÷hžhhŸh¶h Kuubh¸)”}”(hŒòThe DRM subsystem contains a lot of helper functions to ease writing drivers for simple graphic devices. For example, the `drivers/gpu/drm/tiny/` directory has a set of drivers that are simple enough to be implemented in a single source file.”h]”(hŒzThe DRM subsystem contains a lot of helper functions to ease writing drivers for simple graphic devices. For example, the ”…””}”(hjhžhhŸNh NubhŒtitle_reference”“”)”}”(hŒ`drivers/gpu/drm/tiny/`”h]”hŒdrivers/gpu/drm/tiny/”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjubhŒa directory has a set of drivers that are simple enough to be implemented in a single source file.”…””}”(hjhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kwhj÷hžhubh¸)”}”(hXBThese drivers make use of the `struct drm_simple_display_pipe_funcs`, that hides any complexity of the DRM subsystem and just requires drivers to implement a few functions needed to operate the device. This could be used for devices that just need a display pipeline with one full-screen scanout buffer feeding one output.”h]”(hŒThese drivers make use of the ”…””}”(hj*hžhhŸNh Nubj)”}”(hŒ&`struct drm_simple_display_pipe_funcs`”h]”hŒ$struct drm_simple_display_pipe_funcs”…””}”(hj2hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj*ubhŒþ, that hides any complexity of the DRM subsystem and just requires drivers to implement a few functions needed to operate the device. This could be used for devices that just need a display pipeline with one full-screen scanout buffer feeding one output.”…””}”(hj*hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K{hj÷hžhubh¸)”}”(hŒ The tiny DRM drivers are good examples to understand how DRM drivers should look like. Since are just a few hundreds lines of code, they are quite easy to read.”h]”hŒ The tiny DRM drivers are good examples to understand how DRM drivers should look like. Since are just a few hundreds lines of code, they are quite easy to read.”…””}”(hjJhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K€hj÷hžhubeh}”(h]”Œ%simple-drm-drivers-to-use-as-examples”ah ]”h"]”Œ%simple drm drivers to use as examples”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Kuubh¢)”}”(hhh]”(h§)”}”(hŒExternal References”h]”hŒExternal References”…””}”(hjchžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj`hžhhŸh¶h K„ubh¸)”}”(hŒËDelving into a Linux kernel subsystem for the first time can be an overwhelming experience, one needs to get familiar with all the concepts and learn about the subsystem's internals, among other details.”h]”hŒÍDelving into a Linux kernel subsystem for the first time can be an overwhelming experience, one needs to get familiar with all the concepts and learn about the subsystem’s internals, among other details.”…””}”(hjqhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K†hj`hžhubh¸)”}”(hŒ›To shallow the learning curve, this section contains a list of presentations and documents that can be used to learn about DRM/KMS and graphics in general.”h]”hŒ›To shallow the learning curve, this section contains a list of presentations and documents that can be used to learn about DRM/KMS and graphics in general.”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KŠhj`hžhubh¸)”}”(hX‚There are different reasons why someone might want to get into DRM: porting an existing fbdev driver, write a DRM driver for a new hardware, fixing bugs that could face when working on the graphics user-space stack, etc. For this reason, the learning material covers many aspects of the Linux graphics stack. From an overview of the kernel and user-space stacks to very specific topics.”h]”hX‚There are different reasons why someone might want to get into DRM: porting an existing fbdev driver, write a DRM driver for a new hardware, fixing bugs that could face when working on the graphics user-space stack, etc. For this reason, the learning material covers many aspects of the Linux graphics stack. From an overview of the kernel and user-space stacks to very specific topics.”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khj`hžhubh¸)”}”(hX The list is sorted in reverse chronological order, to keep the most up-to-date material at the top. But all of them contain useful information, and it can be valuable to go through older material to understand the rationale and context in which the changes to the DRM subsystem were made.”h]”hX The list is sorted in reverse chronological order, to keep the most up-to-date material at the top. But all of them contain useful information, and it can be valuable to go through older material to understand the rationale and context in which the changes to the DRM subsystem were made.”…””}”(hj›hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K“hj`hžhubh¢)”}”(hhh]”(h§)”}”(hŒConference talks”h]”hŒConference talks”…””}”(hj¬hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj©hžhhŸh¶h K™ubhŒ bullet_list”“”)”}”(hhh]”(hŒ list_item”“”)”}”(hŒ`An Overview of the Linux and Userspace Graphics Stack `_ - Paul Kocialkowski (2020)”h]”h¸)”}”(hjÃh]”(jÃ)”}”(hŒf`An Overview of the Linux and Userspace Graphics Stack `_”h]”hŒ5An Overview of the Linux and Userspace Graphics Stack”…””}”(hjÈhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œ5An Overview of the Linux and Userspace Graphics Stack”Œrefuri”Œ+https://www.youtube.com/watch?v=wjAJmqwg47k”uh1jÂhjÅubhŒtarget”“”)”}”(hŒ. ”h]”h}”(h]”Œ5an-overview-of-the-linux-and-userspace-graphics-stack”ah ]”h"]”Œ5an overview of the linux and userspace graphics stack”ah$]”h&]”Œrefuri”jÙuh1jÚŒ referenced”KhjÅubhŒ - Paul Kocialkowski (2020)”…””}”(hjÅhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K›hjÁubah}”(h]”h ]”h"]”h$]”h&]”uh1j¿hj¼hžhhŸh¶h NubjÀ)”}”(hŒŠ`Getting pixels on screen on Linux: introduction to Kernel Mode Setting `_ - Simon Ser (2020)”h]”h¸)”}”(hjüh]”(jÃ)”}”(hŒw`Getting pixels on screen on Linux: introduction to Kernel Mode Setting `_”h]”hŒFGetting pixels on screen on Linux: introduction to Kernel Mode Setting”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”ŒFGetting pixels on screen on Linux: introduction to Kernel Mode Setting”jØŒ+https://www.youtube.com/watch?v=haes4_Xnc5Q”uh1jÂhjþubjÛ)”}”(hŒ. ”h]”h}”(h]”ŒEgetting-pixels-on-screen-on-linux-introduction-to-kernel-mode-setting”ah ]”h"]”ŒFgetting pixels on screen on linux: introduction to kernel mode setting”ah$]”h&]”Œrefuri”juh1jÚjéKhjþubhŒ - Simon Ser (2020)”…””}”(hjþhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kœhjúubah}”(h]”h ]”h"]”h$]”h&]”uh1j¿hj¼hžhhŸh¶h NubjÀ)”}”(hŒp`Everything Great about Upstream Graphics `_ - Simona Vetter (2019)”h]”h¸)”}”(hj1h]”(jÃ)”}”(hŒY`Everything Great about Upstream Graphics `_”h]”hŒ(Everything Great about Upstream Graphics”…””}”(hj6hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œ(Everything Great about Upstream Graphics”jØŒ+https://www.youtube.com/watch?v=kVzHOgt6WGE”uh1jÂhj3ubjÛ)”}”(hŒ. ”h]”h}”(h]”Œ(everything-great-about-upstream-graphics”ah ]”h"]”Œ(everything great about upstream graphics”ah$]”h&]”Œrefuri”jFuh1jÚjéKhj3ubhŒ - Simona Vetter (2019)”…””}”(hj3hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khj/ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¿hj¼hžhhŸh¶h NubjÀ)”}”(hŒr`An introduction to the Linux DRM subsystem `_ - Maxime Ripard (2017)”h]”h¸)”}”(hjfh]”(jÃ)”}”(hŒ[`An introduction to the Linux DRM subsystem `_”h]”hŒ*An introduction to the Linux DRM subsystem”…””}”(hjkhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œ*An introduction to the Linux DRM subsystem”jØŒ+https://www.youtube.com/watch?v=LbDOCJcDRoo”uh1jÂhjhubjÛ)”}”(hŒ. ”h]”h}”(h]”Œ*an-introduction-to-the-linux-drm-subsystem”ah ]”h"]”Œ*an introduction to the linux drm subsystem”ah$]”h&]”Œrefuri”j{uh1jÚjéKhjhubhŒ - Maxime Ripard (2017)”…””}”(hjhhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kžhjdubah}”(h]”h ]”h"]”h$]”h&]”uh1j¿hj¼hžhhŸh¶h NubjÀ)”}”(hŒh`Embrace the Atomic (Display) Age `_ - Simona Vetter (2016)”h]”h¸)”}”(hj›h]”(jÃ)”}”(hŒQ`Embrace the Atomic (Display) Age `_”h]”hŒ Embrace the Atomic (Display) Age”…””}”(hj hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œ Embrace the Atomic (Display) Age”jØŒ+https://www.youtube.com/watch?v=LjiB_JeDn2M”uh1jÂhjubjÛ)”}”(hŒ. ”h]”h}”(h]”Œembrace-the-atomic-display-age”ah ]”h"]”Œ embrace the atomic (display) age”ah$]”h&]”Œrefuri”j°uh1jÚjéKhjubhŒ - Simona Vetter (2016)”…””}”(hjhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KŸhj™ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¿hj¼hžhhŸh¶h NubjÀ)”}”(hŒj`Anatomy of an Atomic KMS Driver `_ - Laurent Pinchart (2015)”h]”h¸)”}”(hjÐh]”(jÃ)”}”(hŒP`Anatomy of an Atomic KMS Driver `_”h]”hŒAnatomy of an Atomic KMS Driver”…””}”(hjÕhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”ŒAnatomy of an Atomic KMS Driver”jØŒ+https://www.youtube.com/watch?v=lihqR9sENpc”uh1jÂhjÒubjÛ)”}”(hŒ. ”h]”h}”(h]”Œanatomy-of-an-atomic-kms-driver”ah ]”h"]”Œanatomy of an atomic kms driver”ah$]”h&]”Œrefuri”jåuh1jÚjéKhjÒubhŒ - Laurent Pinchart (2015)”…””}”(hjÒhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K hjÎubah}”(h]”h ]”h"]”h$]”h&]”uh1j¿hj¼hžhhŸh¶h NubjÀ)”}”(hŒf`Atomic Modesetting for Drivers `_ - Simona Vetter (2015)”h]”h¸)”}”(hjh]”(jÃ)”}”(hŒO`Atomic Modesetting for Drivers `_”h]”hŒAtomic Modesetting for Drivers”…””}”(hj hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”ŒAtomic Modesetting for Drivers”jØŒ+https://www.youtube.com/watch?v=kl9suFgbTc8”uh1jÂhjubjÛ)”}”(hŒ. ”h]”h}”(h]”Œatomic-modesetting-for-drivers”ah ]”h"]”Œatomic modesetting for drivers”ah$]”h&]”Œrefuri”juh1jÚjéKhjubhŒ - Simona Vetter (2015)”…””}”(hjhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K¡hjubah}”(h]”h ]”h"]”h$]”h&]”uh1j¿hj¼hžhhŸh¶h NubjÀ)”}”(hŒm`Anatomy of an Embedded KMS Driver `_ - Laurent Pinchart (2013) ”h]”h¸)”}”(hŒl`Anatomy of an Embedded KMS Driver `_ - Laurent Pinchart (2013)”h]”(jÃ)”}”(hŒR`Anatomy of an Embedded KMS Driver `_”h]”hŒ!Anatomy of an Embedded KMS Driver”…””}”(hj@hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œ!Anatomy of an Embedded KMS Driver”jØŒ+https://www.youtube.com/watch?v=Ja8fM7rTae4”uh1jÂhj<ubjÛ)”}”(hŒ. ”h]”h}”(h]”Œ!anatomy-of-an-embedded-kms-driver”ah ]”h"]”Œ!anatomy of an embedded kms driver”ah$]”h&]”Œrefuri”jPuh1jÚjéKhj<ubhŒ - Laurent Pinchart (2013)”…””}”(hj<hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K¢hj8ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¿hj¼hžhhŸh¶h Nubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ*”uh1jºhŸh¶h K›hj©hžhubeh}”(h]”Œconference-talks”ah ]”h"]”Œconference talks”ah$]”h&]”uh1h¡hj`hžhhŸh¶h K™ubh¢)”}”(hhh]”(h§)”}”(hŒSlides and articles”h]”hŒSlides and articles”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj~hžhhŸh¶h K¥ubj»)”}”(hhh]”(jÀ)”}”(hŒo`The Linux graphics stack in a nutshell, part 1 `_ - Thomas Zimmermann (2023)”h]”h¸)”}”(hj”h]”(jÃ)”}”(hŒT`The Linux graphics stack in a nutshell, part 1 `_”h]”hŒ.The Linux graphics stack in a nutshell, part 1”…””}”(hj™hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œ.The Linux graphics stack in a nutshell, part 1”jØŒ https://lwn.net/Articles/955376/”uh1jÂhj–ubjÛ)”}”(hŒ# ”h]”h}”(h]”Œ-the-linux-graphics-stack-in-a-nutshell-part-1”ah ]”h"]”Œ.the linux graphics stack in a nutshell, part 1”ah$]”h&]”Œrefuri”j©uh1jÚjéKhj–ubhŒ - Thomas Zimmermann (2023)”…””}”(hj–hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K§hj’ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¿hjhžhhŸh¶h NubjÀ)”}”(hŒo`The Linux graphics stack in a nutshell, part 2 `_ - Thomas Zimmermann (2023)”h]”h¸)”}”(hjÉh]”(jÃ)”}”(hŒT`The Linux graphics stack in a nutshell, part 2 `_”h]”hŒ.The Linux graphics stack in a nutshell, part 2”…””}”(hjÎhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œ.The Linux graphics stack in a nutshell, part 2”jØŒ https://lwn.net/Articles/955708/”uh1jÂhjËubjÛ)”}”(hŒ# ”h]”h}”(h]”Œ-the-linux-graphics-stack-in-a-nutshell-part-2”ah ]”h"]”Œ.the linux graphics stack in a nutshell, part 2”ah$]”h&]”Œrefuri”jÞuh1jÚjéKhjËubhŒ - Thomas Zimmermann (2023)”…””}”(hjËhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K¨hjÇubah}”(h]”h ]”h"]”h$]”h&]”uh1j¿hjhžhhŸh¶h NubjÀ)”}”(hŒz`Understanding the Linux Graphics Stack `_ - Bootlin (2022)”h]”h¸)”}”(hjþh]”(jÃ)”}”(hŒi`Understanding the Linux Graphics Stack `_”h]”hŒ&Understanding the Linux Graphics Stack”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œ&Understanding the Linux Graphics Stack”jØŒ=https://bootlin.com/doc/training/graphics/graphics-slides.pdf”uh1jÂhjubjÛ)”}”(hŒ@ ”h]”h}”(h]”Œ&understanding-the-linux-graphics-stack”ah ]”h"]”Œ&understanding the linux graphics stack”ah$]”h&]”Œrefuri”juh1jÚjéKhjubhŒ - Bootlin (2022)”…””}”(hjhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K©hjüubah}”(h]”h ]”h"]”h$]”h&]”uh1j¿hjhžhhŸh¶h NubjÀ)”}”(hŒd`DRM KMS overview `_ - STMicroelectronics (2021)”h]”h¸)”}”(hj3h]”(jÃ)”}”(hŒH`DRM KMS overview `_”h]”hŒDRM KMS overview”…””}”(hj8hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”ŒDRM KMS overview”jØŒ2https://wiki.st.com/stm32mpu/wiki/DRM_KMS_overview”uh1jÂhj5ubjÛ)”}”(hŒ5 ”h]”h}”(h]”Œdrm-kms-overview”ah ]”h"]”Œdrm kms overview”ah$]”h&]”Œrefuri”jHuh1jÚjéKhj5ubhŒ - STMicroelectronics (2021)”…””}”(hj5hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kªhj1ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¿hjhžhhŸh¶h NubjÀ)”}”(hŒq`Linux graphic stack `_ - Nathan Gauër (2017)”h]”h¸)”}”(hjhh]”(jÃ)”}”(hŒZ`Linux graphic stack `_”h]”hŒLinux graphic stack”…””}”(hjmhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”ŒLinux graphic stack”jØŒAhttps://studiopixl.com/2017-05-13/linux-graphic-stack-an-overview”uh1jÂhjjubjÛ)”}”(hŒD ”h]”h}”(h]”Œlinux-graphic-stack”ah ]”h"]”Œlinux graphic stack”ah$]”h&]”Œrefuri”j}uh1jÚjéKhjjubhŒ - Nathan Gauër (2017)”…””}”(hjjhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K«hjfubah}”(h]”h ]”h"]”h$]”h&]”uh1j¿hjhžhhŸh¶h NubjÀ)”}”(hŒh`Atomic mode setting design overview, part 1 `_ - Simona Vetter (2015)”h]”h¸)”}”(hjh]”(jÃ)”}”(hŒQ`Atomic mode setting design overview, part 1 `_”h]”hŒ+Atomic mode setting design overview, part 1”…””}”(hj¢hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œ+Atomic mode setting design overview, part 1”jØŒ https://lwn.net/Articles/653071/”uh1jÂhjŸubjÛ)”}”(hŒ# ”h]”h}”(h]”Œ*atomic-mode-setting-design-overview-part-1”ah ]”h"]”Œ+atomic mode setting design overview, part 1”ah$]”h&]”Œrefuri”j²uh1jÚjéKhjŸubhŒ - Simona Vetter (2015)”…””}”(hjŸhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K¬hj›ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¿hjhžhhŸh¶h NubjÀ)”}”(hŒh`Atomic mode setting design overview, part 2 `_ - Simona Vetter (2015)”h]”h¸)”}”(hjÒh]”(jÃ)”}”(hŒQ`Atomic mode setting design overview, part 2 `_”h]”hŒ+Atomic mode setting design overview, part 2”…””}”(hj×hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œ+Atomic mode setting design overview, part 2”jØŒ https://lwn.net/Articles/653466/”uh1jÂhjÔubjÛ)”}”(hŒ# ”h]”h}”(h]”Œ*atomic-mode-setting-design-overview-part-2”ah ]”h"]”Œ+atomic mode setting design overview, part 2”ah$]”h&]”Œrefuri”jçuh1jÚjéKhjÔubhŒ - Simona Vetter (2015)”…””}”(hjÔhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K­hjÐubah}”(h]”h ]”h"]”h$]”h&]”uh1j¿hjhžhhŸh¶h NubjÀ)”}”(hŒ©`The DRM/KMS subsystem from a newbie’s point of view `_ - Boris Brezillon (2014)”h]”h¸)”}”(hjh]”(jÃ)”}”(hŒ`The DRM/KMS subsystem from a newbie’s point of view `_”h]”hŒ5The DRM/KMS subsystem from a newbie’s point of view”…””}”(hj hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œ5The DRM/KMS subsystem from a newbie’s point of view”jØŒUhttps://bootlin.com/pub/conferences/2014/elce/brezillon-drm-kms/brezillon-drm-kms.pdf”uh1jÂhj ubjÛ)”}”(hŒX ”h]”h}”(h]”Œ2the-drm-kms-subsystem-from-a-newbies-point-of-view”ah ]”h"]”Œ5the drm/kms subsystem from a newbie’s point of view”ah$]”h&]”Œrefuri”juh1jÚjéKhj ubhŒ - Boris Brezillon (2014)”…””}”(hj hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K®hjubah}”(h]”h ]”h"]”h$]”h&]”uh1j¿hjhžhhŸh¶h NubjÀ)”}”(hŒ¦`A brief introduction to the Linux graphics stack `_ - Iago Toral (2014)”h]”h¸)”}”(hj<h]”(jÃ)”}”(hŒ’`A brief introduction to the Linux graphics stack `_”h]”hŒ0A brief introduction to the Linux graphics stack”…””}”(hjAhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œ0A brief introduction to the Linux graphics stack”jØŒ\https://blogs.igalia.com/itoral/2014/07/29/a-brief-introduction-to-the-linux-graphics-stack/”uh1jÂhj>ubjÛ)”}”(hŒ_ ”h]”h}”(h]”Œ0a-brief-introduction-to-the-linux-graphics-stack”ah ]”h"]”Œ0a brief introduction to the linux graphics stack”ah$]”h&]”Œrefuri”jQuh1jÚjéKhj>ubhŒ - Iago Toral (2014)”…””}”(hj>hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K¯hj:ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¿hjhžhhŸh¶h NubjÀ)”}”(hŒs`The Linux Graphics Stack `_ - Jasper St. Pierre (2012)”h]”h¸)”}”(hjqh]”(jÃ)”}”(hŒX`The Linux Graphics Stack `_”h]”hŒThe Linux Graphics Stack”…””}”(hjvhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”ŒThe Linux Graphics Stack”jØŒ:https://blog.mecheye.net/2012/06/the-linux-graphics-stack/”uh1jÂhjsubjÛ)”}”(hŒ= ”h]”h}”(h]”Œthe-linux-graphics-stack”ah ]”h"]”Œthe linux graphics stack”ah$]”h&]”Œrefuri”j†uh1jÚjéKhjsubhŒ - Jasper St. Pierre (2012)”…””}”(hjshžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K°hjoubah}”(h]”h ]”h"]”h$]”h&]”uh1j¿hjhžhhŸh¶h Nubeh}”(h]”h ]”h"]”h$]”h&]”jtjuuh1jºhŸh¶h K§hj~hžhubeh}”(h]”Œslides-and-articles”ah ]”h"]”Œslides and articles”ah$]”h&]”uh1h¡hj`hžhhŸh¶h K¥ubeh}”(h]”Œexternal-references”ah ]”h"]”Œexternal references”ah$]”h&]”uh1h¡hh£hžhhŸh¶h K„ubeh}”(h]”Œ introduction”ah ]”h"]”Œ introduction”ah$]”h&]”uh1h¡hhhžhhŸh¶h 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”}”(j¿j¼jÇjÄj¿j¼j jjôjñj¦j£jìjéj]jZj·j´j{jxjåjâjjjPjMj…j‚jºj·jïjìj$j!jZjWj¯j¬j³j°jèjåjjjRjOj‡j„j¼j¹jñjîj&j#j[jXjjuŒ nametypes”}”(j¿‰jljj¿‰j ‰jô‰j¦‰jì‰j]‰j·‰j{‰jåˆjˆjPˆj…ˆjºˆjïˆj$ˆjZˆj¯‰j³ˆjèˆjˆjRˆj‡ˆj¼ˆjñˆj&ˆj[ˆjˆuh}”(j¼h£jÄhãj¼j{jjÊjñj#j£jfjéj©jZj÷j´j`jxj©jâjÜjjjMjGj‚j|j·j±jìjæj!jjWjQj¬j~j°jªjåjßjjjOjIj„j~j¹j³jîjèj#jjXjRjj‡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.