Scsphinx.addnodesdocument)}( rawsourcechildren]( translations LanguagesNode)}(hhh](h pending_xref)}(hhh]docutils.nodesTextChinese (Simplified)}parenthsba attributes}(ids]classes]names]dupnames]backrefs] refdomainstdreftypedoc reftarget/translations/zh_CN/fb/sisfbmodnameN classnameN refexplicitutagnamehhh ubh)}(hhh]hChinese (Traditional)}hh2sbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget/translations/zh_TW/fb/sisfbmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hItalian}hhFsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget/translations/it_IT/fb/sisfbmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hJapanese}hhZsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget/translations/ja_JP/fb/sisfbmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hKorean}hhnsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget/translations/ko_KR/fb/sisfbmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hSpanish}hhsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget/translations/sp_SP/fb/sisfbmodnameN classnameN refexplicituh1hhh ubeh}(h]h ]h"]h$]h&]current_languageEnglishuh1h hh _documenthsourceNlineNubhsection)}(hhh](htitle)}(hWhat is sisfb?h]hWhat is sisfb?}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhhh6/var/lib/git/docbuild/linux/Documentation/fb/sisfb.rsthKubh paragraph)}(hhsisfb is a framebuffer device driver for SiS (Silicon Integrated Systems) graphics chips. Supported are:h]hhsisfb is a framebuffer device driver for SiS (Silicon Integrated Systems) graphics chips. Supported are:}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhhhhubh bullet_list)}(hhh](h list_item)}(h0SiS 300 series: SiS 300/305, 540, 630(S), 730(S)h]h)}(hhh]h0SiS 300 series: SiS 300/305, 540, 630(S), 730(S)}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhhubah}(h]h ]h"]h$]h&]uh1hhhhhhhhNubh)}(hISiS 315 series: SiS 315/H/PRO, 55x, (M)65x, 740, (M)661(F/M)X, (M)741(GX)h]h)}(hhh]hISiS 315 series: SiS 315/H/PRO, 55x, (M)65x, 740, (M)661(F/M)X, (M)741(GX)}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK hhubah}(h]h ]h"]h$]h&]uh1hhhhhhhhNubh)}(h+SiS 330 series: SiS 330 ("Xabre"), (M)760 h]h)}(h)SiS 330 series: SiS 330 ("Xabre"), (M)760h]h-SiS 330 series: SiS 330 (“Xabre”), (M)760}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK hhubah}(h]h ]h"]h$]h&]uh1hhhhhhhhNubeh}(h]h ]h"]h$]h&]bullet-uh1hhhhKhhhhubh)}(hhh](h)}(h#Why do I need a framebuffer driver?h]h#Why do I need a framebuffer driver?}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhKubh)}(hsisfb is eg. useful if you want a high-resolution text console. Besides that, sisfb is required to run DirectFB (which comes with an additional, dedicated driver for the 315 series).h]hsisfb is eg. useful if you want a high-resolution text console. Besides that, sisfb is required to run DirectFB (which comes with an additional, dedicated driver for the 315 series).}(hj-hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubh)}(hOn the 300 series, sisfb on kernels older than 2.6.3 furthermore plays an important role in connection with DRM/DRI: Sisfb manages the memory heap used by DRM/DRI for 3D texture and other data. This memory management is required for using DRI/DRM.h]hOn the 300 series, sisfb on kernels older than 2.6.3 furthermore plays an important role in connection with DRM/DRI: Sisfb manages the memory heap used by DRM/DRI for 3D texture and other data. This memory management is required for using DRI/DRM.}(hj;hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubh)}(hX Kernels >= around 2.6.3 do not need sisfb any longer for DRI/DRM memory management. The SiS DRM driver has been updated and features a memory manager of its own (which will be used if sisfb is not compiled). So unless you want a graphical console, you don't need sisfb on kernels >=2.6.3.h]hX"Kernels >= around 2.6.3 do not need sisfb any longer for DRI/DRM memory management. The SiS DRM driver has been updated and features a memory manager of its own (which will be used if sisfb is not compiled). So unless you want a graphical console, you don’t need sisfb on kernels >=2.6.3.}(hjIhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubh)}(hSidenote: Since this seems to be a commonly made mistake: sisfb and vesafb cannot be active at the same time! Do only select one of them in your kernel configuration.h]hSidenote: Since this seems to be a commonly made mistake: sisfb and vesafb cannot be active at the same time! Do only select one of them in your kernel configuration.}(hjWhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubeh}(h]"why-do-i-need-a-framebuffer-driverah ]h"]#why do i need a framebuffer driver?ah$]h&]uh1hhhhhhhhKubh)}(hhh](h)}(h#How are parameters passed to sisfb?h]h#How are parameters passed to sisfb?}(hjphhhNhNubah}(h]h ]h"]h$]h&]uh1hhjmhhhhhK$ubh)}(hX"Well, it depends: If compiled statically into the kernel, use lilo's append statement to add the parameters to the kernel command line. Please see lilo's (or GRUB's) documentation for more information. If sisfb is a kernel module, parameters are given with the modprobe (or insmod) command.h]hX(Well, it depends: If compiled statically into the kernel, use lilo’s append statement to add the parameters to the kernel command line. Please see lilo’s (or GRUB’s) documentation for more information. If sisfb is a kernel module, parameters are given with the modprobe (or insmod) command.}(hj~hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK&hjmhhubh)}(hZExample for sisfb as part of the static kernel: Add the following line to your lilo.conf::h]hYExample for sisfb as part of the static kernel: Add the following line to your lilo.conf:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK+hjmhhubh literal_block)}(h7append="video=sisfb:mode:1024x768x16,mem:12288,rate:75"h]h7append="video=sisfb:mode:1024x768x16,mem:12288,rate:75"}hjsbah}(h]h ]h"]h$]h&] xml:spacepreserveuh1jhhhK.hjmhhubh)}(h6Example for sisfb as a module: Start sisfb by typing::h]h5Example for sisfb as a module: Start sisfb by typing:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK0hjmhhubj)}(h1modprobe sisfb mode=1024x768x16 rate=75 mem=12288h]h1modprobe sisfb mode=1024x768x16 rate=75 mem=12288}hjsbah}(h]h ]h"]h$]h&]jjuh1jhhhK2hjmhhubh)}(hXA common mistake is that folks use a wrong parameter format when using the driver compiled into the kernel. Please note: If compiled into the kernel, the parameter format is video=sisfb:mode:none or video=sisfb:mode:1024x768x16 (or whatever mode you want to use, alternatively using any other format described above or the vesa keyword instead of mode). If compiled as a module, the parameter format reads mode=none or mode=1024x768x16 (or whatever mode you want to use). Using a "=" for a ":" (and vice versa) is a huge difference! Additionally: If you give more than one argument to the in-kernel sisfb, the arguments are separated with ",". For example::h]hXA common mistake is that folks use a wrong parameter format when using the driver compiled into the kernel. Please note: If compiled into the kernel, the parameter format is video=sisfb:mode:none or video=sisfb:mode:1024x768x16 (or whatever mode you want to use, alternatively using any other format described above or the vesa keyword instead of mode). If compiled as a module, the parameter format reads mode=none or mode=1024x768x16 (or whatever mode you want to use). Using a “=” for a “:” (and vice versa) is a huge difference! Additionally: If you give more than one argument to the in-kernel sisfb, the arguments are separated with “,”. For example:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK4hjmhhubj)}(h.video=sisfb:mode:1024x768x16,rate:75,mem:12288h]h.video=sisfb:mode:1024x768x16,rate:75,mem:12288}hjsbah}(h]h ]h"]h$]h&]jjuh1jhhhK>hjmhhubeh}(h]"how-are-parameters-passed-to-sisfbah ]h"]#how are parameters passed to sisfb?ah$]h&]uh1hhhhhhhhK$ubh)}(hhh](h)}(hHow do I use it?h]hHow do I use it?}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhKBubh)}(hXCPreface statement: This file only covers very little of the driver's capabilities and features. Please refer to the author's and maintainer's website at http://www.winischhofer.net/linuxsisvga.shtml for more information. Additionally, "modinfo sisfb" gives an overview over all supported options including some explanation.h](hPreface statement: This file only covers very little of the driver’s capabilities and features. Please refer to the author’s and maintainer’s website at }(hjhhhNhNubh reference)}(h-http://www.winischhofer.net/linuxsisvga.shtmlh]h-http://www.winischhofer.net/linuxsisvga.shtml}(hjhhhNhNubah}(h]h ]h"]h$]h&]refurij uh1jhjubh for more information. Additionally, “modinfo sisfb” gives an overview over all supported options including some explanation.}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKDhjhhubh)}(htThe desired display mode can be specified using the keyword "mode" with a parameter in one of the following formats:h]hxThe desired display mode can be specified using the keyword “mode” with a parameter in one of the following formats:}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKJhjhhubh block_quote)}(hx- XxYxDepth or - XxY-Depth or - XxY-Depth@Rate or - XxY - or simply use the VESA mode number in hexadecimal or decimal. h]h)}(hhh](h)}(h XxYxDepth orh]h)}(hj9h]h XxYxDepth or}(hj;hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKMhj7ubah}(h]h ]h"]h$]h&]uh1hhj4ubh)}(h XxY-Depth orh]h)}(hjPh]h XxY-Depth or}(hjRhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKNhjNubah}(h]h ]h"]h$]h&]uh1hhj4ubh)}(hXxY-Depth@Rate orh]h)}(hjgh](j)}(hXxY-Depth@Rateh]hXxY-Depth@Rate}(hjlhhhNhNubah}(h]h ]h"]h$]h&]refurimailto:XxY-Depth@Rateuh1jhjiubh or}(hjihhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKOhjeubah}(h]h ]h"]h$]h&]uh1hhj4ubh)}(hXxYh]h)}(hjh]hXxY}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKPhjubah}(h]h ]h"]h$]h&]uh1hhj4ubh)}(h>or simply use the VESA mode number in hexadecimal or decimal. h]h)}(h=or simply use the VESA mode number in hexadecimal or decimal.h]h=or simply use the VESA mode number in hexadecimal or decimal.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKQhjubah}(h]h ]h"]h$]h&]uh1hhj4ubeh}(h]h ]h"]h$]h&]jjuh1hhhhKMhj0ubah}(h]h ]h"]h$]h&]uh1j.hhhKMhjhhubh)}(hFor example: 1024x768x16, 1024x768-16@75, 1280x1024-16. If no depth is specified, it defaults to 8. If no rate is given, it defaults to 60Hz. Depth 32 means 24bit color depth (but 32 bit framebuffer depth, which is not relevant to the user).h](hFor example: 1024x768x16, }(hjhhhNhNubj)}(h1024x768-16@75h]h1024x768-16@75}(hjhhhNhNubah}(h]h ]h"]h$]h&]refurimailto:1024x768-16@75uh1jhjubh, 1280x1024-16. If no depth is specified, it defaults to 8. If no rate is given, it defaults to 60Hz. Depth 32 means 24bit color depth (but 32 bit framebuffer depth, which is not relevant to the user).}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKShjhhubh)}(hAdditionally, sisfb understands the keyword "vesa" followed by a VESA mode number in decimal or hexadecimal. For example: vesa=791 or vesa=0x117. Please use either "mode" or "vesa" but not both.h]hAdditionally, sisfb understands the keyword “vesa” followed by a VESA mode number in decimal or hexadecimal. For example: vesa=791 or vesa=0x117. Please use either “mode” or “vesa” but not both.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKXhjhhubh)}(hXCLinux 2.4 only: If no mode is given, sisfb defaults to "no mode" (mode=none) if compiled as a module; if sisfb is statically compiled into the kernel, it defaults to 800x600x8 unless CRT2 type is LCD, in which case the LCD's native resolution is used. If you want to switch to a different mode, use the fbset shell command.h]hXILinux 2.4 only: If no mode is given, sisfb defaults to “no mode” (mode=none) if compiled as a module; if sisfb is statically compiled into the kernel, it defaults to 800x600x8 unless CRT2 type is LCD, in which case the LCD’s native resolution is used. If you want to switch to a different mode, use the fbset shell command.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK\hjhhubh)}(hLinux 2.6 only: If no mode is given, sisfb defaults to 800x600x8 unless CRT2 type is LCD, in which case it defaults to the LCD's native resolution. If you want to switch to another mode, use the stty shell command.h]hLinux 2.6 only: If no mode is given, sisfb defaults to 800x600x8 unless CRT2 type is LCD, in which case it defaults to the LCD’s native resolution. If you want to switch to another mode, use the stty shell command.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKbhjhhubh)}(hYou should compile in both vgacon (to boot if you remove you SiS card from your system) and sisfb (for graphics mode). Under Linux 2.6, also "Framebuffer console support" (fbcon) is needed for a graphical console.h]hYou should compile in both vgacon (to boot if you remove you SiS card from your system) and sisfb (for graphics mode). Under Linux 2.6, also “Framebuffer console support” (fbcon) is needed for a graphical console.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKfhjhhubh)}(hYou should *not* compile-in vesafb. And please do not use the "vga=" keyword in lilo's or grub's configuration file; mode selection is done using the "mode" or "vesa" keywords as a parameter. See above and below.h](h You should }(hj!hhhNhNubhemphasis)}(h*not*h]hnot}(hj+hhhNhNubah}(h]h ]h"]h$]h&]uh1j)hj!ubh compile-in vesafb. And please do not use the “vga=” keyword in lilo’s or grub’s configuration file; mode selection is done using the “mode” or “vesa” keywords as a parameter. See above and below.}(hj!hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKjhjhhubeh}(h]how-do-i-use-itah ]h"]how do i use it?ah$]h&]uh1hhhhhhhhKBubh)}(hhh](h)}(hX11h]hX11}(hjNhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjKhhhhhKpubh)}(hIf using XFree86 or X.org, it is recommended that you don't use the "fbdev" driver but the dedicated "sis" X driver. The "sis" X driver and sisfb are developed by the same person (Thomas Winischhofer) and cooperate well with each other.h]hIf using XFree86 or X.org, it is recommended that you don’t use the “fbdev” driver but the dedicated “sis” X driver. The “sis” X driver and sisfb are developed by the same person (Thomas Winischhofer) and cooperate well with each other.}(hj\hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKrhjKhhubeh}(h]x11ah ]h"]x11ah$]h&]uh1hhhhhhhhKpubh)}(hhh](h)}(hSVGALibh]hSVGALib}(hjuhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjrhhhhhKyubh)}(hX!SVGALib, if directly accessing the hardware, never restores the screen correctly, especially on laptops or if the output devices are LCD or TV. Therefore, use the chipset "FBDEV" in SVGALib configuration. This will make SVGALib use the framebuffer device for mode switches and restoration.h]hX%SVGALib, if directly accessing the hardware, never restores the screen correctly, especially on laptops or if the output devices are LCD or TV. Therefore, use the chipset “FBDEV” in SVGALib configuration. This will make SVGALib use the framebuffer device for mode switches and restoration.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK{hjrhhubeh}(h]svgalibah ]h"]svgalibah$]h&]uh1hhhhhhhhKyubh)}(hhh](h)}(h Configurationh]h Configuration}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhKubh)}(h(Some) accepted options:h]h(Some) accepted options:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubhtable)}(hhh]htgroup)}(hhh](hcolspec)}(hhh]h}(h]h ]h"]h$]h&]colwidthK uh1jhjubj)}(hhh]h}(h]h ]h"]h$]h&]colwidthKBuh1jhjubhtbody)}(hhh](hrow)}(hhh](hentry)}(hhh]h)}(hoffh]hoff}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(hRDisable sisfb. This option is only understood if sisfb is in-kernel, not a module.h]hRDisable sisfb. This option is only understood if sisfb is in-kernel, not a module.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(hmem:Xh]hmem:X}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(hX5size of memory for the console, rest will be used for DRI/DRM. X is in kilobytes. On 300 series, the default is 4096, 8192 or 16384 (each in kilobyte) depending on how much video ram the card has. On 315/330 series, the default is the maximum available ram (since DRI/DRM is not supported for these chipsets).h]hX5size of memory for the console, rest will be used for DRI/DRM. X is in kilobytes. On 300 series, the default is 4096, 8192 or 16384 (each in kilobyte) depending on how much video ram the card has. On 315/330 series, the default is the maximum available ram (since DRI/DRM is not supported for these chipsets).}(hj5hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj2ubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(hnoaccelh]hnoaccel}(hjUhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjRubah}(h]h ]h"]h$]h&]uh1jhjOubj)}(hhh]h)}(h>do not use 2D acceleration engine. (Default: use acceleration)h]h>do not use 2D acceleration engine. (Default: use acceleration)}(hjlhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjiubah}(h]h ]h"]h$]h&]uh1jhjOubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(hnoypanh]hnoypan}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(hydisable y-panning and scroll by redrawing the entire screen. This is much slower than y-panning. (Default: use y-panning)h]hydisable y-panning and scroll by redrawing the entire screen. This is much slower than y-panning. (Default: use y-panning)}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(hvesa:Xh]hvesa:X}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(hselects startup videomode. X is number from 0 to 0x1FF and represents the VESA mode number (can be given in decimal or hexadecimal form, the latter prefixed with "0x").h]hselects startup videomode. X is number from 0 to 0x1FF and represents the VESA mode number (can be given in decimal or hexadecimal form, the latter prefixed with “0x”).}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(hmode:Xh]hmode:X}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(hBselects startup videomode. Please see above for the format of "X".h]hFselects startup videomode. Please see above for the format of “X”.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]colsKuh1jhjubah}(h]h ]h"]h$]h&]uh1jhjhhhhhNubh)}(hBoolean options such as "noaccel" or "noypan" are to be given without a parameter if sisfb is in-kernel (for example "video=sisfb:noypan). If sisfb is a module, these are to be set to 1 (for example "modprobe sisfb noypan=1").h]hBoolean options such as “noaccel” or “noypan” are to be given without a parameter if sisfb is in-kernel (for example “video=sisfb:noypan). If sisfb is a module, these are to be set to 1 (for example “modprobe sisfb noypan=1”).}(hj>hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubh)}(h-Thomas Winischhofer h](hThomas Winischhofer <}(hjLhhhNhNubj)}(hthomas@winischhofer.neth]hthomas@winischhofer.net}(hjThhhNhNubah}(h]h ]h"]h$]h&]refurimailto:thomas@winischhofer.netuh1jhjLubh>}(hjLhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKhjhhubh)}(h May 27, 2004h]h May 27, 2004}(hjnhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubeh}(h] configurationah ]h"] configurationah$]h&]uh1hhhhhhhhKubeh}(h] what-is-sisfbah ]h"]what is sisfb?ah$]h&]uh1hhhhhhhhKubeh}(h]h ]h"]h$]h&]sourcehuh1hcurrent_sourceN current_lineNsettingsdocutils.frontendValues)}(hN generatorN datestampN source_linkN source_urlN toc_backlinksjfootnote_backlinksK sectnum_xformKstrip_commentsNstrip_elements_with_classesN strip_classesN report_levelK halt_levelKexit_status_levelKdebugNwarning_streamN tracebackinput_encoding utf-8-siginput_encoding_error_handlerstrictoutput_encodingutf-8output_encoding_error_handlerjerror_encodingutf-8error_encoding_error_handlerbackslashreplace language_codeenrecord_dependenciesNconfigN id_prefixhauto_id_prefixid dump_settingsNdump_internalsNdump_transformsNdump_pseudo_xmlNexpose_internalsNstrict_visitorN_disable_configN_sourceh _destinationN _config_files]7/var/lib/git/docbuild/linux/Documentation/docutils.confafile_insertion_enabled raw_enabledKline_length_limitM'pep_referencesN pep_base_urlhttps://peps.python.org/pep_file_url_templatepep-%04drfc_referencesN rfc_base_url&https://datatracker.ietf.org/doc/html/ tab_widthKtrim_footnote_reference_spacesyntax_highlightlong smart_quotessmartquotes_locales]character_level_inline_markupdoctitle_xform docinfo_xformKsectsubtitle_xform image_loadinglinkembed_stylesheetcloak_email_addressessection_self_linkenvNubreporterNindirect_targets]substitution_defs}substitution_names}refnames}refids}nameids}(jjjjjgjjjHjEjojljjjj~u nametypes}(jjjjjHjojjuh}(jhjgjjjmjEjjljKjjrj~ju footnote_refs} citation_refs} autofootnotes]autofootnote_refs]symbol_footnotes]symbol_footnote_refs] footnotes] citations]autofootnote_startKsymbol_footnote_startK id_counter collectionsCounter}Rparse_messages]transform_messages] transformerN include_log] decorationNhhub.