Psphinx.addnodesdocument)}( rawsourcechildren]( translations LanguagesNode)}(hhh](h pending_xref)}(hhh]docutils.nodesTextChinese (Simplified)}parenthsba attributes}(ids]classes]names]dupnames]backrefs] refdomainstdreftypedoc reftarget&/translations/zh_CN/wmi/acpi-interfacemodnameN classnameN refexplicitutagnamehhh ubh)}(hhh]hChinese (Traditional)}hh2sbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget&/translations/zh_TW/wmi/acpi-interfacemodnameN classnameN refexplicituh1hhh ubh)}(hhh]hItalian}hhFsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget&/translations/it_IT/wmi/acpi-interfacemodnameN classnameN refexplicituh1hhh ubh)}(hhh]hJapanese}hhZsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget&/translations/ja_JP/wmi/acpi-interfacemodnameN classnameN refexplicituh1hhh ubh)}(hhh]hKorean}hhnsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget&/translations/ko_KR/wmi/acpi-interfacemodnameN classnameN refexplicituh1hhh ubh)}(hhh]hPortuguese (Brazilian)}hhsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget&/translations/pt_BR/wmi/acpi-interfacemodnameN classnameN refexplicituh1hhh ubh)}(hhh]hSpanish}hhsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget&/translations/sp_SP/wmi/acpi-interfacemodnameN classnameN refexplicituh1hhh ubeh}(h]h ]h"]h$]h&]current_languageEnglishuh1h hh _documenthsourceNlineNubhcomment)}(h)SPDX-License-Identifier: GPL-2.0-or-laterh]h)SPDX-License-Identifier: GPL-2.0-or-later}hhsbah}(h]h ]h"]h$]h&] xml:spacepreserveuh1hhhhhh@/var/lib/git/docbuild/linux/Documentation/wmi/acpi-interface.rsthKubhsection)}(hhh](htitle)}(hACPI WMI interfaceh]hACPI WMI interface}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhhhhhKubh paragraph)}(hXBThe ACPI WMI interface is a proprietary extension of the ACPI specification made by Microsoft to allow hardware vendors to embed WMI (Windows Management Instrumentation) objects inside their ACPI firmware. Typical functions implemented over ACPI WMI are hotkey events on modern notebooks and configuration of BIOS options.h]hXBThe ACPI WMI interface is a proprietary extension of the ACPI specification made by Microsoft to allow hardware vendors to embed WMI (Windows Management Instrumentation) objects inside their ACPI firmware. Typical functions implemented over ACPI WMI are hotkey events on modern notebooks and configuration of BIOS options.}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhhhhubh)}(hhh](h)}(hPNP0C14 ACPI deviceh]hPNP0C14 ACPI device}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhhhhhK ubh)}(hX6Discovery of WMI objects is handled by defining ACPI devices with a PNP ID of ``PNP0C14``. These devices will contain a set of ACPI buffers and methods used for mapping and execution of WMI methods and/or queries. If there exist multiple of such devices, then each device is required to have a unique ACPI UID.h](hNDiscovery of WMI objects is handled by defining ACPI devices with a PNP ID of }(hhhhhNhNubhliteral)}(h ``PNP0C14``h]hPNP0C14}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhubh. These devices will contain a set of ACPI buffers and methods used for mapping and execution of WMI methods and/or queries. If there exist multiple of such devices, then each device is required to have a unique ACPI UID.}(hhhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKhhhhubeh}(h]pnp0c14-acpi-deviceah ]h"]pnp0c14 acpi deviceah$]h&]uh1hhhhhhhhK ubh)}(hhh](h)}(h _WDG bufferh]h _WDG buffer}(hj+hhhNhNubah}(h]h ]h"]h$]h&]uh1hhj(hhhhhKubh)}(hThe ``_WDG`` buffer is used to discover WMI objects and is required to be static. Its internal structure consists of data blocks with a size of 20 bytes, containing the following data:h](hThe }(hj9hhhNhNubj)}(h``_WDG``h]h_WDG}(hjAhhhNhNubah}(h]h ]h"]h$]h&]uh1jhj9ubh buffer is used to discover WMI objects and is required to be static. Its internal structure consists of data blocks with a size of 20 bytes, containing the following data:}(hj9hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKhj(hhubhtable)}(hhh]htgroup)}(hhh](hcolspec)}(hhh]h}(h]h ]h"]h$]h&]colwidthKuh1jchj`ubjd)}(hhh]h}(h]h ]h"]h$]h&]colwidthKuh1jchj`ubjd)}(hhh]h}(h]h ]h"]h$]h&]colwidthK5uh1jchj`ubhthead)}(hhh]hrow)}(hhh](hentry)}(hhh]h)}(hOffseth]hOffset}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(hSize (in bytes)h]hSize (in bytes)}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(hContenth]hContent}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhjubah}(h]h ]h"]h$]h&]uh1jhj`ubhtbody)}(hhh](j)}(hhh](j)}(hhh]h)}(h0x00h]h0x00}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(h16h]h16}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(h128 bit Variant 2 object GUID.h]h128 bit Variant 2 object GUID.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(h0x10h]h0x10}(hj9hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK hj6ubah}(h]h ]h"]h$]h&]uh1jhj3ubj)}(hhh]h)}(h2h]h2}(hjPhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK hjMubah}(h]h ]h"]h$]h&]uh1jhj3ubj)}(hhh]h)}(h52 character method ID or single byte notification ID.h]h52 character method ID or single byte notification ID.}(hjghhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK hjdubah}(h]h ]h"]h$]h&]uh1jhj3ubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(h0x12h]h0x12}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK!hjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(h1h]h1}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK!hjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(hObject instance count.h]hObject instance count.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK!hjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(h0x13h]h0x13}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK"hjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(hjh]h1}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK"hjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(h Object flags.h]h Object flags.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK"hjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhj`ubeh}(h]h ]h"]h$]h&]colsKuh1j^hj[ubah}(h]h ]h"]h$]h&]uh1jYhj(hhhhhNubh)}(hKThe WMI object flags control whether the method or notification ID is used:h]hKThe WMI object flags control whether the method or notification ID is used:}(hj/hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK%hj(hhubh bullet_list)}(hhh](h list_item)}(h(0x1: Data block is expensive to collect.h]h)}(hjFh]h(0x1: Data block is expensive to collect.}(hjHhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK'hjDubah}(h]h ]h"]h$]h&]uh1jBhj?hhhhhNubjC)}(h%0x2: Data block contains WMI methods.h]h)}(hj]h]h%0x2: Data block contains WMI methods.}(hj_hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK(hj[ubah}(h]h ]h"]h$]h&]uh1jBhj?hhhhhNubjC)}(h&0x4: Data block contains ASCIZ string.h]h)}(hjth]h&0x4: Data block contains ASCIZ string.}(hjvhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK)hjrubah}(h]h ]h"]h$]h&]uh1jBhj?hhhhhNubjC)}(hQ0x8: Data block describes a WMI event, use notification ID instead of method ID. h]h)}(hP0x8: Data block describes a WMI event, use notification ID instead of method ID.h]hP0x8: Data block describes a WMI event, use notification ID instead of method ID.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK*hjubah}(h]h ]h"]h$]h&]uh1jBhj?hhhhhNubeh}(h]h ]h"]h$]h&]bullet-uh1j=hhhK'hj(hhubh)}(hEach WMI object GUID can appear multiple times inside a system. The method/notification ID is used to construct the ACPI method names used for interacting with the WMI object.h]hEach WMI object GUID can appear multiple times inside a system. The method/notification ID is used to construct the ACPI method names used for interacting with the WMI object.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK-hj(hhubeh}(h] wdg-bufferah ]h"] _wdg bufferah$]h&]uh1hhhhhhhhKubh)}(hhh](h)}(hWQxx ACPI methodsh]hWQxx ACPI methods}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhK2ubh)}(hXrIf a data block does not contain WMI methods, then its content can be retrieved by this required ACPI method. The last two characters of the ACPI method name are the method ID of the data block to query. Their single parameter is an integer describing the instance which should be queried. This parameter can be omitted if the data block contains only a single instance.h]hXrIf a data block does not contain WMI methods, then its content can be retrieved by this required ACPI method. The last two characters of the ACPI method name are the method ID of the data block to query. Their single parameter is an integer describing the instance which should be queried. This parameter can be omitted if the data block contains only a single instance.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK4hjhhubeh}(h]wqxx-acpi-methodsah ]h"]wqxx acpi methodsah$]h&]uh1hhhhhhhhK2ubh)}(hhh](h)}(hWSxx ACPI methodsh]hWSxx ACPI methods}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhK;ubh)}(hSimilar to the ``WQxx`` ACPI methods, except that it is optional and takes an additional buffer as its second argument. The instance argument also cannot be omitted.h](hSimilar to the }(hjhhhNhNubj)}(h``WQxx``h]hWQxx}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubh ACPI methods, except that it is optional and takes an additional buffer as its second argument. The instance argument also cannot be omitted.}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhK=hjhhubeh}(h]wsxx-acpi-methodsah ]h"]wsxx acpi methodsah$]h&]uh1hhhhhhhhK;ubh)}(hhh](h)}(hWMxx ACPI methodsh]hWMxx ACPI methods}(hj"hhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhKBubh)}(hXNUsed for executing WMI methods associated with a data block. The last two characters of the ACPI method name are the method ID of the data block containing the WMI methods. Their first parameter is a integer describing the instance which methods should be executed. The second parameter is an integer describing the WMI method ID to execute, and the third parameter is a buffer containing the WMI method parameters. If the data block is marked as containing an ASCIZ string, then this buffer should contain an ASCIZ string. The ACPI method will return the result of the executed WMI method.h]hXNUsed for executing WMI methods associated with a data block. The last two characters of the ACPI method name are the method ID of the data block containing the WMI methods. Their first parameter is a integer describing the instance which methods should be executed. The second parameter is an integer describing the WMI method ID to execute, and the third parameter is a buffer containing the WMI method parameters. If the data block is marked as containing an ASCIZ string, then this buffer should contain an ASCIZ string. The ACPI method will return the result of the executed WMI method.}(hj0hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKDhjhhubeh}(h]wmxx-acpi-methodsah ]h"]wmxx acpi methodsah$]h&]uh1hhhhhhhhKBubh)}(hhh](h)}(hWExx ACPI methodsh]hWExx ACPI methods}(hjIhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjFhhhhhKNubh)}(hX9Used for optionally enabling/disabling WMI events, the last two characters of the ACPI method are the notification ID of the data block describing the WMI event as hexadecimal value. Their first parameter is an integer with a value of 0 if the WMI event should be disabled, other values will enable the WMI event.h]hX9Used for optionally enabling/disabling WMI events, the last two characters of the ACPI method are the notification ID of the data block describing the WMI event as hexadecimal value. Their first parameter is an integer with a value of 0 if the WMI event should be disabled, other values will enable the WMI event.}(hjWhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKPhjFhhubh)}(hThose ACPI methods are always called even for WMI events not registered as being expensive to collect to match the behavior of the Windows driver.h]hThose ACPI methods are always called even for WMI events not registered as being expensive to collect to match the behavior of the Windows driver.}(hjehhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKVhjFhhubeh}(h]wexx-acpi-methodsah ]h"]wexx acpi methodsah$]h&]uh1hhhhhhhhKNubh)}(hhh](h)}(hWCxx ACPI methodsh]hWCxx ACPI methods}(hj~hhhNhNubah}(h]h ]h"]h$]h&]uh1hhj{hhhhhKZubh)}(hXSimilar to the ``WExx`` ACPI methods, except that instead of WMI events it controls data collection of data blocks registered as being expensive to collect. Thus the last two characters of the ACPI method name are the method ID of the data block to enable/disable.h](hSimilar to the }(hjhhhNhNubj)}(h``WExx``h]hWExx}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubh ACPI methods, except that instead of WMI events it controls data collection of data blocks registered as being expensive to collect. Thus the last two characters of the ACPI method name are the method ID of the data block to enable/disable.}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhK[hj{hhubh)}(hjThose ACPI methods are also called before setting data blocks to match the behavior of the Windows driver.h]hjThose ACPI methods are also called before setting data blocks to match the behavior of the Windows driver.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK`hj{hhubeh}(h]wcxx-acpi-methodsah ]h"]wcxx acpi methodsah$]h&]uh1hhhhhhhhKZubh)}(hhh](h)}(h_WED ACPI methodh]h_WED ACPI method}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhKdubh)}(hXUsed to retrieve additional WMI event data, its single parameter is a integer holding the notification ID of the event. This method should be evaluated every time an ACPI notification is received, since some ACPI implementations use a queue to store WMI event data items. This queue will overflow after a couple of WMI events are received without retrieving the associated WMI event data.h]hXUsed to retrieve additional WMI event data, its single parameter is a integer holding the notification ID of the event. This method should be evaluated every time an ACPI notification is received, since some ACPI implementations use a queue to store WMI event data items. This queue will overflow after a couple of WMI events are received without retrieving the associated WMI event data.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKfhjhhubeh}(h]wed-acpi-methodah ]h"]_wed acpi methodah$]h&]uh1hhhhhhhhKdubh)}(hhh](h)}(h$Conversion rules for ACPI data typesh]h$Conversion rules for ACPI data types}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhKmubh)}(hXConsumers of the ACPI-WMI interface use binary buffers to exchange data with the WMI driver core, with the internal structure of the buffer being only know to the consumers. The WMI driver core is thus responsible for converting the data inside the buffer into an appropriate ACPI data type for consumption by the ACPI firmware. Additionally, any data returned by the various ACPI methods needs to be converted back into a binary buffer.h]hXConsumers of the ACPI-WMI interface use binary buffers to exchange data with the WMI driver core, with the internal structure of the buffer being only know to the consumers. The WMI driver core is thus responsible for converting the data inside the buffer into an appropriate ACPI data type for consumption by the ACPI firmware. Additionally, any data returned by the various ACPI methods needs to be converted back into a binary buffer.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKohjhhubh)}(hnThe layout of said buffers is defined by the MOF description of the WMI method or data block in question [1]_:h](hiThe layout of said buffers is defined by the MOF description of the WMI method or data block in question }(hjhhhNhNubhfootnote_reference)}(h[1]_h]h1}(hjhhhNhNubah}(h]id1ah ]h"]h$]h&]refidid2docnamewmi/acpi-interfaceuh1jhjresolvedKubh:}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKuhjhhubjZ)}(hhh]j_)}(hhh](jd)}(hhh]h}(h]h ]h"]h$]h&]colwidthKuh1jchj3ubjd)}(hhh]h}(h]h ]h"]h$]h&]colwidthKGuh1jchj3ubjd)}(hhh]h}(h]h ]h"]h$]h&]colwidthK uh1jchj3ubj)}(hhh]j)}(hhh](j)}(hhh]h)}(h Data Typeh]h Data Type}(hj]hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKyhjZubah}(h]h ]h"]h$]h&]uh1jhjWubj)}(hhh]h)}(hLayouth]hLayout}(hjthhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKyhjqubah}(h]h ]h"]h$]h&]uh1jhjWubj)}(hhh]h)}(h Alignmenth]h Alignment}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKyhjubah}(h]h ]h"]h$]h&]uh1jhjWubeh}(h]h ]h"]h$]h&]uh1jhjTubah}(h]h ]h"]h$]h&]uh1jhj3ubj)}(hhh](j)}(hhh](j)}(hhh]h)}(h ``string``h]j)}(hjh]hstring}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubah}(h]h ]h"]h$]h&]uh1hhhhK{hjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(hXwStarts with an unsigned 16-bit little endian integer specifying the length of the string data in bytes, followed by the string data encoded as UTF-16LE with **optional** NULL termination and padding. Keep in mind that some firmware implementations might depend on the terminating NULL character to be present. Also the padding should always be performed with NULL characters.h](hStarts with an unsigned 16-bit little endian integer specifying the length of the string data in bytes, followed by the string data encoded as UTF-16LE with }(hjhhhNhNubhstrong)}(h **optional**h]hoptional}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubh NULL termination and padding. Keep in mind that some firmware implementations might depend on the terminating NULL character to be present. Also the padding should always be performed with NULL characters.}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhK{hjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(h2 bytesh]h2 bytes}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK{hjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(h ``boolean``h]j)}(hj!h]hboolean}(hj#hhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(h?Single byte where 0 means ``false`` and nonzero means ``true``.h](hSingle byte where 0 means }(hj?hhhNhNubj)}(h ``false``h]hfalse}(hjGhhhNhNubah}(h]h ]h"]h$]h&]uh1jhj?ubh and nonzero means }(hj?hhhNhNubj)}(h``true``h]htrue}(hjYhhhNhNubah}(h]h ]h"]h$]h&]uh1jhj?ubh.}(hj?hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKhj<ubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(h1 byteh]h1 byte}(hjzhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjwubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(h ``sint8``h]j)}(hjh]hsint8}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(hSigned 8-bit integer.h]hSigned 8-bit integer.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(h1 byteh]h1 byte}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(h ``uint8``h]j)}(hjh]huint8}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(hUnsigned 8-bit integer.h]hUnsigned 8-bit integer.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(h1 byteh]h1 byte}(hj(hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj%ubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(h ``sint16``h]j)}(hjJh]hsint16}(hjLhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjHubah}(h]h ]h"]h$]h&]uh1hhhhKhjEubah}(h]h ]h"]h$]h&]uh1jhjBubj)}(hhh]h)}(h$Signed 16-bit little endian integer.h]h$Signed 16-bit little endian integer.}(hjhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjeubah}(h]h ]h"]h$]h&]uh1jhjBubj)}(hhh]h)}(h2 bytesh]h2 bytes}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj|ubah}(h]h ]h"]h$]h&]uh1jhjBubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(h ``uint16``h]j)}(hjh]huint16}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(h&Unsigned 16-bit little endian integer.h]h&Unsigned 16-bit little endian integer.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(h2 bytesh]h2 bytes}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(h ``sint32``h]j)}(hjh]hsint32}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(h$Signed 32-bit little endian integer.h]h$Signed 32-bit little endian integer.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(h4 bytesh]h4 bytes}(hj-hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj*ubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(h ``uint32``h]j)}(hjOh]huint32}(hjQhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjMubah}(h]h ]h"]h$]h&]uh1hhhhKhjJubah}(h]h ]h"]h$]h&]uh1jhjGubj)}(hhh]h)}(h&Unsigned 32-bit little endian integer.h]h&Unsigned 32-bit little endian integer.}(hjmhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjjubah}(h]h ]h"]h$]h&]uh1jhjGubj)}(hhh]h)}(h4 bytesh]h4 bytes}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjGubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(h ``sint64``h]j)}(hjh]hsint64}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(h$Signed 64-bit little endian integer.h]h$Signed 64-bit little endian integer.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(h8 bytesh]h8 bytes}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(h ``uint64``h]j)}(hjh]huint64}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(h&Unsigned 64-bit little endian integer.h]h&Unsigned 64-bit little endian integer.}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj ubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(h8 bytesh]h8 bytes}(hj2 hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj/ ubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(h ``datetime``h]j)}(hjT h]hdatetime}(hjV hhhNhNubah}(h]h ]h"]h$]h&]uh1jhjR ubah}(h]h ]h"]h$]h&]uh1hhhhKhjO ubah}(h]h ]h"]h$]h&]uh1jhjL ubj)}(hhh]h)}(hXA fixed-length 25-character UTF-16LE string with the format *yyyymmddhhmmss.mmmmmmsutc* where *yyyy* is the 4-digit year, *mm* is the 2-digit month, *dd* is the 2-digit day, *hh* is the 2-digit hour based on a 24-hour clock, *mm* is the 2-digit minute, *ss* is the 2-digit second, *mmmmmm* is the 6-digit microsecond, *s* is a plus or minus character depending on whether *utc* is a positive or negative offset from UTC (or a colon if the date is an interval). Unpopulated fields should be filled with asterisks.h](h