€•£«Œ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ŒPortuguese (Brazilian)”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ$/translations/pt_BR/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&]”Œrefid”Œid1”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Œtopic”“”)”}”(hŒ Contents ”h]”(h»)”}”(hŒContents”h]”hŒContents”…””}”(hhÿh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhhûh³hÌh´KubhŒ bullet_list”“”)”}”(hhh]”hŒ list_item”“”)”}”(hhh]”(hÎ)”}”(hhh]”hŒ reference”“”)”}”(hhh]”hŒ Introduction”…””}”(hjh²hh³Nh´Nubah}”(h]”hËah ]”h"]”h$]”h&]”Œrefid”Œ introduction”uh1jhjubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjubj)”}”(hhh]”(j)”}”(hhh]”(hÎ)”}”(hhh]”j)”}”(hhh]”hŒStyle Guidelines”…””}”(hj:h²hh³Nh´Nubah}”(h]”Œid2”ah ]”h"]”h$]”h&]”Œrefid”Œstyle-guidelines”uh1jhj7ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj4ubj)”}”(hhh]”j)”}”(hhh]”hÎ)”}”(hhh]”j)”}”(hhh]”hŒ#Documentation Requirements for kAPI”…””}”(hjYh²hh³Nh´Nubah}”(h]”Œid3”ah ]”h"]”h$]”h&]”Œrefid”Œ#documentation-requirements-for-kapi”uh1jhjVubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjSubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjPubah}”(h]”h ]”h"]”h$]”h&]”uh1j hj4ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jhj1ubj)”}”(hhh]”hÎ)”}”(hhh]”j)”}”(hhh]”hŒGetting Started”…””}”(hj‡h²hh³Nh´Nubah}”(h]”Œid4”ah ]”h"]”h$]”h&]”Œrefid”Œgetting-started”uh1jhj„ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj1ubj)”}”(hhh]”(hÎ)”}”(hhh]”j)”}”(hhh]”hŒContribution Process”…””}”(hj©h²hh³Nh´Nubah}”(h]”Œid5”ah ]”h"]”h$]”h&]”Œrefid”Œcontribution-process”uh1jhj¦ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj£ubj)”}”(hhh]”(j)”}”(hhh]”hÎ)”}”(hhh]”j)”}”(hhh]”hŒFeature Merge Deadlines”…””}”(hjÈh²hh³Nh´Nubah}”(h]”Œid6”ah ]”h"]”h$]”h&]”Œrefid”Œfeature-merge-deadlines”uh1jhjÅubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjÂubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj¿ubj)”}”(hhh]”hÎ)”}”(hhh]”j)”}”(hhh]”hŒCode of Conduct”…””}”(hjêh²hh³Nh´Nubah}”(h]”Œid7”ah ]”h"]”h$]”h&]”Œrefid”Œcode-of-conduct”uh1jhjçubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjäubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj¿ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j hj£ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jhj1ubj)”}”(hhh]”hÎ)”}”(hhh]”j)”}”(hhh]”hŒ%Simple DRM drivers to use as examples”…””}”(hjh²hh³Nh´Nubah}”(h]”Œid8”ah ]”h"]”h$]”h&]”Œrefid”Œ%simple-drm-drivers-to-use-as-examples”uh1jhjubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj1ubj)”}”(hhh]”(hÎ)”}”(hhh]”j)”}”(hhh]”hŒExternal References”…””}”(hj:h²hh³Nh´Nubah}”(h]”Œid9”ah ]”h"]”h$]”h&]”Œrefid”Œexternal-references”uh1jhj7ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj4ubj)”}”(hhh]”(j)”}”(hhh]”hÎ)”}”(hhh]”j)”}”(hhh]”hŒConference talks”…””}”(hjYh²hh³Nh´Nubah}”(h]”Œid10”ah ]”h"]”h$]”h&]”Œrefid”Œconference-talks”uh1jhjVubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjSubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjPubj)”}”(hhh]”hÎ)”}”(hhh]”j)”}”(hhh]”hŒSlides and articles”…””}”(hj{h²hh³Nh´Nubah}”(h]”Œid11”ah ]”h"]”h$]”h&]”Œrefid”Œslides-and-articles”uh1jhjxubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjuubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjPubeh}”(h]”h ]”h"]”h$]”h&]”uh1j hj4ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jhj1ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j hjubeh}”(h]”h ]”h"]”h$]”h&]”uh1jhjubah}”(h]”h ]”h"]”h$]”h&]”uh1j hhûh²hh³Nh´Nubeh}”(h]”Œcontents”ah ]”Œcontents”ah"]”Œcontents”ah$]”h&]”uh1hùh³hÌh´Khh·h²hubh¶)”}”(hhh]”(h»)”}”(hŒStyle Guidelines”h]”hŒStyle Guidelines”…””}”(hjÁh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”hÊjCuh1hºhj¾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.”…””}”(hjÏh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍh³hÌh´Khj¾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. ”…””}”(hjÝh²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åhjÝubhXÄ. 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.”…””}”(hjÝh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÍh³hÌh´K#hj¾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”…””}”(hjh²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.hj¾h²hubhÎ)”}”(hŒRAlso read the :ref:`guidelines for the kernel documentation at large `.”h]”(hŒAlso read the ”…””}”(hjh²hh³Nh´Nubh)”}”(hŒC:ref:`guidelines for the kernel documentation at large `”h]”hŒinline”“”)”}”(hj)h]”hŒ0guidelines for the kernel documentation at large”…””}”(hj-h²hh³Nh´Nubah}”(h]”h ]”(Œxref”Œstd”Œstd-ref”eh"]”h$]”h&]”uh1j+hj'ubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”Œgpu/introduction”Œ refdomain”j8Œreftype”Œref”Œ refexplicit”ˆŒrefwarn”ˆŒ reftarget”Œ doc_guide”uh1hh³hÌh´K6hjubhŒ.”…””}”(hjh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÍh³hÌh´K6hj¾h²hubh¶)”}”(hhh]”(h»)”}”(hŒ#Documentation Requirements for kAPI”h]”hŒ#Documentation Requirements for kAPI”…””}”(hjYh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”hÊjbuh1hºhjVh²hh³hÌh´K9ubhÎ)”}”(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.”…””}”(hjgh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍh³hÌh´K;hjVh²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 ”…””}”(hjuh²hh³Nh´Nubjæ)”}”(hŒ``/* private: */``”h]”hŒ/* private: */”…””}”(hj}h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jåhjuubhŒ) comments as per the documentation guide.”…””}”(hjuh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÍh³hÌh´K@hjVh²hubeh}”(h]”jhah ]”h"]”Œ#documentation requirements for kapi”ah$]”h&]”uh1hµhj¾h²hh³hÌh´K9ubeh}”(h]”jIah ]”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&]”hÊjuh1hºhj£h²hh³hÌh´KIubhÎ)”}”(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´KKhj£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]”j,)”}”(hjÌh]”hŒ TODO list”…””}”(hjÎh²hh³Nh´Nubah}”(h]”h ]”(j7Œstd”Œstd-ref”eh"]”h$]”h&]”uh1j+hjÊubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”jDŒ refdomain”jØŒreftype”Œref”Œ refexplicit”ˆŒrefwarn”ˆjJŒtodo”uh1hh³hÌh´KOhjÂubhŒ.”…””}”(hjÂh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÍh³hÌh´KOhj£h²hubeh}”(h]”j–ah ]”h"]”Œgetting started”ah$]”h&]”uh1hµhh·h²hh³hÌh´KIubh¶)”}”(hhh]”(h»)”}”(hŒContribution Process”h]”hŒContribution Process”…””}”(hjþh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”hÊj²uh1hºhjûh²hh³hÌh´KSubhÎ)”}”(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 ”…””}”(hj h²hh³Nh´Nubh)”}”(hŒD:ref:`the main process guidelines and documentation `”h]”j,)”}”(hjh]”hŒ-the main process guidelines and documentation”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”(j7Œstd”Œstd-ref”eh"]”h$]”h&]”uh1j+hjubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”jDŒ refdomain”j"Œreftype”Œref”Œ refexplicit”ˆŒrefwarn”ˆjJŒ process_index”uh1hh³hÌh´KUhj ubhŒZ for how things work. Here we just document some of the specialities of the GPU subsystem.”…””}”(hj h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÍh³hÌh´KUhjûh²hubh¶)”}”(hhh]”(h»)”}”(hŒFeature Merge Deadlines”h]”hŒFeature Merge Deadlines”…””}”(hjAh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”hÊjÑuh1hºhj>h²hh³hÌh´KZubhÎ)”}”(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.”…””}”(hjOh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍh³hÌh´K\hj>h²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´Kbhj>h²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.”…””}”(hjkh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍh³hÌh´Kfhj>h²hubeh}”(h]”j×ah ]”h"]”Œfeature merge deadlines”ah$]”h&]”uh1hµhjûh²hh³hÌh´KZubh¶)”}”(hhh]”(h»)”}”(hŒCode of Conduct”h]”hŒCode of Conduct”…””}”(hjƒh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”hÊjóuh1hºhj€h²hh³hÌh´KlubhÎ)”}”(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´Nubj)”}”(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›uh1jhj‘ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÍh³hÌh´Knhj€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´Kqhj€h²hubeh}”(h]”jùah ]”h"]”Œcode of conduct”ah$]”h&]”uh1hµhjûh²hh³hÌh´Klubeh}”(h]”j¸ah ]”h"]”Œcontribution process”ah$]”h&]”uh1hµhh·h²hh³hÌh´KSubh¶)”}”(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&]”hÊj!uh1hºhjÊh²hh³hÌh´KwubhÎ)”}”(hX“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. 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ŒzThe DRM subsystem contains a lot of helper functions to ease writing drivers for simple graphic devices. For example, the ”…””}”(hjÛh²hh³Nh´NubhŒtitle_reference”“”)”}”(hŒ`drivers/gpu/drm/tiny/`”h]”hŒdrivers/gpu/drm/tiny/”…””}”(hjåh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jãhjÛubhX directory has a set of drivers that are simple enough to be implemented in a single source file. 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.”…””}”(hjÛh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÍh³hÌh´KyhjÊh²hubeh}”(h]”j'ah ]”h"]”Œ%simple drm drivers to use as examples”ah$]”h&]”uh1hµhh·h²hh³hÌh´Kwubh¶)”}”(hhh]”(h»)”}”(hŒExternal References”h]”hŒExternal References”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”hÊjCuh1hºhjh²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.”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍh³hÌh´K‚hjh²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.”…””}”(hj#h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍh³hÌh´K†hjh²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.”…””}”(hj1h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍh³hÌh´K‰hjh²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´Khjh²hubh¶)”}”(hhh]”(h»)”}”(hŒConference talks”h]”hŒConference talks”…””}”(hjPh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”hÊjbuh1hºhjMh²hh³hÌh´K•ubj)”}”(hhh]”(j)”}”(hŒ`An Overview of the Linux and Userspace Graphics Stack `_ - Paul Kocialkowski (2020)”h]”hÎ)”}”(hjch]”(j)”}”(hŒf`An Overview of the Linux and Userspace Graphics Stack `_”h]”hŒ5An Overview of the Linux and Userspace Graphics Stack”…””}”(hjhh²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”uh1jhjeubhŒ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”jyuh1jzŒ referenced”KhjeubhŒ - Paul Kocialkowski (2020)”…””}”(hjeh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÍh³hÌh´K—hjaubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj^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”…””}”(hj¡h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”ŒFGetting pixels on screen on Linux: introduction to Kernel Mode Setting”jxŒ+https://www.youtube.com/watch?v=haes4_Xnc5Q”uh1jhjž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”j±uh1jzj‰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&]”uh1jhj^h²hh³hÌh´Nubj)”}”(hŒp`Everything Great about Upstream Graphics `_ - Simona Vetter (2019)”h]”hÎ)”}”(hjÑh]”(j)”}”(hŒY`Everything Great about Upstream Graphics `_”h]”hŒ(Everything Great about Upstream Graphics”…””}”(hjÖh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œ(Everything Great about Upstream Graphics”jxŒ+https://www.youtube.com/watch?v=kVzHOgt6WGE”uh1jhjÓubj{)”}”(hŒ. ”h]”h}”(h]”Œ(everything-great-about-upstream-graphics”ah ]”h"]”Œ(everything great about upstream graphics”ah$]”h&]”Œrefuri”jæuh1jzj‰KhjÓubhŒ - Simona Vetter (2019)”…””}”(hjÓh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÍh³hÌh´K™hjÏubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj^h²hh³hÌh´Nubj)”}”(hŒr`An introduction to the Linux DRM subsystem `_ - Maxime Ripard (2017)”h]”hÎ)”}”(hjh]”(j)”}”(hŒ[`An introduction to the Linux DRM subsystem `_”h]”hŒ*An introduction to the Linux DRM subsystem”…””}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œ*An introduction to the Linux DRM subsystem”jxŒ+https://www.youtube.com/watch?v=LbDOCJcDRoo”uh1jhjubj{)”}”(hŒ. ”h]”h}”(h]”Œ*an-introduction-to-the-linux-drm-subsystem”ah ]”h"]”Œ*an introduction to the linux drm subsystem”ah$]”h&]”Œrefuri”juh1jzj‰KhjubhŒ - Maxime Ripard (2017)”…””}”(hjh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÍh³hÌh´Kšhjubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj^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”jxŒ+https://www.youtube.com/watch?v=LjiB_JeDn2M”uh1jhj=ubj{)”}”(hŒ. ”h]”h}”(h]”Œembrace-the-atomic-display-age”ah ]”h"]”Œ embrace the atomic (display) age”ah$]”h&]”Œrefuri”jPuh1jzj‰Khj=ubhŒ - Simona Vetter (2016)”…””}”(hj=h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÍh³hÌh´K›hj9ubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj^h²hh³hÌh´Nubj)”}”(hŒj`Anatomy of an Atomic KMS Driver `_ - Laurent Pinchart (2015)”h]”hÎ)”}”(hjph]”(j)”}”(hŒP`Anatomy of an Atomic KMS Driver `_”h]”hŒAnatomy of an Atomic KMS Driver”…””}”(hjuh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”ŒAnatomy of an Atomic KMS Driver”jxŒ+https://www.youtube.com/watch?v=lihqR9sENpc”uh1jhjrubj{)”}”(hŒ. ”h]”h}”(h]”Œanatomy-of-an-atomic-kms-driver”ah ]”h"]”Œanatomy of an atomic kms driver”ah$]”h&]”Œrefuri”j…uh1jzj‰KhjrubhŒ - Laurent Pinchart (2015)”…””}”(hjrh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÍh³hÌh´Kœhjnubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj^h²hh³hÌh´Nubj)”}”(hŒf`Atomic Modesetting for Drivers `_ - Simona Vetter (2015)”h]”hÎ)”}”(hj¥h]”(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”jxŒ+https://www.youtube.com/watch?v=kl9suFgbTc8”uh1jhj§ubj{)”}”(hŒ. ”h]”h}”(h]”Œatomic-modesetting-for-drivers”ah ]”h"]”Œatomic modesetting for drivers”ah$]”h&]”Œrefuri”jºuh1jzj‰Khj§ubhŒ - Simona Vetter (2015)”…””}”(hj§h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÍh³hÌh´Khj£ubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj^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”jxŒ+https://www.youtube.com/watch?v=Ja8fM7rTae4”uh1jhjÜubj{)”}”(hŒ. ”h]”h}”(h]”Œ!anatomy-of-an-embedded-kms-driver”ah ]”h"]”Œ!anatomy of an embedded kms driver”ah$]”h&]”Œrefuri”jðuh1jzj‰KhjÜubhŒ - Laurent Pinchart (2013)”…””}”(hjÜh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÍh³hÌh´KžhjØubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj^h²hh³hÌh´Nubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ*”uh1j h³hÌh´K—hjMh²hubeh}”(h]”jhah ]”h"]”Œconference talks”ah$]”h&]”uh1hµhjh²hh³hÌh´K•ubh¶)”}”(hhh]”(h»)”}”(hŒSlides and articles”h]”hŒSlides and articles”…””}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”hÊj„uh1hºhjh²hh³hÌh´K¡ubj)”}”(hhh]”(j)”}”(hŒo`The Linux graphics stack in a nutshell, part 1 `_ - Thomas Zimmermann (2023)”h]”hÎ)”}”(hj3h]”(j)”}”(hŒT`The Linux graphics stack in a nutshell, part 1 `_”h]”hŒ.The Linux graphics stack in a nutshell, part 1”…””}”(hj8h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œ.The Linux graphics stack in a nutshell, part 1”jxŒ https://lwn.net/Articles/955376/”uh1jhj5ubj{)”}”(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”jHuh1jzj‰Khj5ubhŒ - Thomas Zimmermann (2023)”…””}”(hj5h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÍh³hÌh´K£hj1ubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj.h²hh³hÌh´Nubj)”}”(hŒo`The Linux graphics stack in a nutshell, part 2 `_ - Thomas Zimmermann (2023)”h]”hÎ)”}”(hjhh]”(j)”}”(hŒT`The Linux graphics stack in a nutshell, part 2 `_”h]”hŒ.The Linux graphics stack in a nutshell, part 2”…””}”(hjmh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œ.The Linux graphics stack in a nutshell, part 2”jxŒ https://lwn.net/Articles/955708/”uh1jhjjubj{)”}”(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}uh1jzj‰KhjjubhŒ - Thomas Zimmermann (2023)”…””}”(hjjh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÍh³hÌh´K¤hjfubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj.h²hh³hÌh´Nubj)”}”(hŒz`Understanding the Linux Graphics Stack `_ - Bootlin (2022)”h]”hÎ)”}”(hjh]”(j)”}”(hŒi`Understanding the Linux Graphics Stack `_”h]”hŒ&Understanding the Linux Graphics Stack”…””}”(hj¢h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œ&Understanding the Linux Graphics Stack”jxŒ=https://bootlin.com/doc/training/graphics/graphics-slides.pdf”uh1jhjŸubj{)”}”(hŒ@ ”h]”h}”(h]”Œ&understanding-the-linux-graphics-stack”ah ]”h"]”Œ&understanding the linux graphics stack”ah$]”h&]”Œrefuri”j²uh1jzj‰KhjŸubhŒ - Bootlin (2022)”…””}”(hjŸh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÍh³hÌh´K¥hj›ubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj.h²hh³hÌh´Nubj)”}”(hŒd`DRM KMS overview `_ - STMicroelectronics (2021)”h]”hÎ)”}”(hjÒh]”(j)”}”(hŒH`DRM KMS overview `_”h]”hŒDRM KMS overview”…””}”(hj×h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”ŒDRM KMS overview”jxŒ2https://wiki.st.com/stm32mpu/wiki/DRM_KMS_overview”uh1jhjÔubj{)”}”(hŒ5 ”h]”h}”(h]”Œdrm-kms-overview”ah ]”h"]”Œdrm kms overview”ah$]”h&]”Œrefuri”jçuh1jzj‰KhjÔubhŒ - STMicroelectronics (2021)”…””}”(hjÔh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÍh³hÌh´K¦hjÐubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj.h²hh³hÌh´Nubj)”}”(hŒq`Linux graphic stack `_ - Nathan Gauër (2017)”h]”hÎ)”}”(hjh]”(j)”}”(hŒZ`Linux graphic stack `_”h]”hŒLinux graphic stack”…””}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”ŒLinux graphic stack”jxŒAhttps://studiopixl.com/2017-05-13/linux-graphic-stack-an-overview”uh1jhj ubj{)”}”(hŒD ”h]”h}”(h]”Œlinux-graphic-stack”ah ]”h"]”Œlinux graphic stack”ah$]”h&]”Œrefuri”juh1jzj‰Khj ubhŒ - Nathan Gauër (2017)”…””}”(hj h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÍh³hÌh´K§hjubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj.h²hh³hÌh´Nubj)”}”(hŒh`Atomic mode setting design overview, part 1 `_ - Simona Vetter (2015)”h]”hÎ)”}”(hj<h]”(j)”}”(hŒQ`Atomic mode setting design overview, part 1 `_”h]”hŒ+Atomic mode setting design overview, part 1”…””}”(hjAh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œ+Atomic mode setting design overview, part 1”jxŒ https://lwn.net/Articles/653071/”uh1jhj>ubj{)”}”(hŒ# ”h]”h}”(h]”Œ*atomic-mode-setting-design-overview-part-1”ah ]”h"]”Œ+atomic mode setting design overview, part 1”ah$]”h&]”Œrefuri”jQuh1jzj‰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&]”uh1jhj.h²hh³hÌh´Nubj)”}”(hŒh`Atomic mode setting design overview, part 2 `_ - Simona Vetter (2015)”h]”hÎ)”}”(hjqh]”(j)”}”(hŒQ`Atomic mode setting design overview, part 2 `_”h]”hŒ+Atomic mode setting design overview, part 2”…””}”(hjvh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œ+Atomic mode setting design overview, part 2”jxŒ https://lwn.net/Articles/653466/”uh1jhjsubj{)”}”(hŒ# ”h]”h}”(h]”Œ*atomic-mode-setting-design-overview-part-2”ah ]”h"]”Œ+atomic mode setting design overview, part 2”ah$]”h&]”Œrefuri”j†uh1jzj‰KhjsubhŒ - Simona Vetter (2015)”…””}”(hjsh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÍh³hÌh´K©hjoubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj.h²hh³hÌh´Nubj)”}”(hŒ©`The DRM/KMS subsystem from a newbie’s point of view `_ - Boris Brezillon (2014)”h]”hÎ)”}”(hj¦h]”(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”jxŒUhttps://bootlin.com/pub/conferences/2014/elce/brezillon-drm-kms/brezillon-drm-kms.pdf”uh1jhj¨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”j»uh1jzj‰Khj¨ubhŒ - Boris Brezillon (2014)”…””}”(hj¨h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÍh³hÌh´Kªhj¤ubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj.h²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”…””}”(hjàh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œ0A brief introduction to the Linux graphics stack”jxŒ\https://blogs.igalia.com/itoral/2014/07/29/a-brief-introduction-to-the-linux-graphics-stack/”uh1jhjÝ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”jðuh1jzj‰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&]”uh1jhj.h²hh³hÌh´Nubj)”}”(hŒs`The Linux Graphics Stack `_ - Jasper St. Pierre (2012)”h]”hÎ)”}”(hj h]”(j)”}”(hŒX`The Linux Graphics Stack `_”h]”hŒThe Linux Graphics Stack”…””}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”ŒThe Linux Graphics Stack”jxŒ:https://blog.mecheye.net/2012/06/the-linux-graphics-stack/”uh1jhj ubj{)”}”(hŒ= ”h]”h}”(h]”Œthe-linux-graphics-stack”ah ]”h"]”Œthe linux graphics stack”ah$]”h&]”Œrefuri”j% uh1jzj‰Khj ubhŒ - Jasper St. Pierre (2012)”…””}”(hj h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÍh³hÌh´K¬hj ubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj.h²hh³hÌh´Nubeh}”(h]”h ]”h"]”h$]”h&]”jjuh1j h³hÌh´K£hjh²hubeh}”(h]”jŠah ]”h"]”Œslides and articles”ah$]”h&]”uh1hµhjh²hh³hÌh´K¡ubeh}”(h]”jIah ]”h"]”Œexternal references”ah$]”h&]”uh1hµhh·h²hh³hÌh´K€ubeh}”(h]”j*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 jIj™jhjøj–jÇj¸j}j×jÀjùjj'jT jIjjhj…j‚j»j¸jðjíj%j"jZjWjjŒjÄjÁjúj÷jM jŠjRjOj‡j„j¼j¹jñjîj&j#j[jXjjjÅjÂjúj÷j/ j, uŒ nametypes”}”(j[ ‰j»‰j ‰j™‰jø‰jljj}‰jÀ‰j‰jT ‰j‰j…ˆj»ˆjðˆj%ˆjZˆjˆjĈjúˆjM ‰jRˆj‡ˆj¼ˆjñˆj&ˆj[ˆjˆjňjúˆj/ ˆuh}”(j*h·j·hûjIj¾jhjVj–j£j¸jûj×j>jùj€j'jÊjIjjhjMj‚j|j¸j²jíjçj"jjWjQjŒj†jÁj»j÷jñjŠjjOjIj„j~j¹j³jîjèj#jjXjRjj‡jÂj¼j÷jñj, j& hËjjCj:jbjYjj‡j²j©jÑjÈjójêj!jjCj:jbjYj„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”“”}”j K s…”R”Œparse_messages”]”Œtransform_messages”]”Œ transformer”NŒ include_log”]”Œ decoration”Nh²hub.