Home
last modified time | relevance | path

Searched refs:fields (Results 1 – 4 of 4) sorted by relevance

/mipi-sys-t-3.7.0/library/doxygen/
DProtocol.md19 The SyS-T Data Protocol includes various optional fields for ensuring data
21 protocol, these SyS-T Message fields may be redundant and so be omitted to
27 All numeric data fields of the SyS-T Data Protocol follow little-endian byte
30 follows RFC 4122 which defines Guid fields following big-endian ordering.
67 of a SyS-T Message with all fields present.
72 The message fields are:
109 The meaning of the individual fields is explained in the table below.
260 appears after the optional message fields, but before the optional checksum.
DApiOverview.md127 - __Type and Subtype__ fields identifying the Message Type.<BR>
128 These fields are set internally by the API call.
131 These fields identify the software module that originated the message. They
134 example how the origin fields are used.
DDoxyfile.in314 # unions with only public data fields will be shown inline in the documentation
1435 # will contain hyperlink fields. The RTF file will
1438 # programs which support those fields.
1758 # If the UML_LOOK tag is enabled, the fields and methods are shown inside
1759 # the class node. If there are many fields or methods and many nodes the
/mipi-sys-t-3.7.0/printer/include/
Dmipi_syst_message.h69 struct fields { struct