Searched full:terminology (Results 1 – 25 of 118) sorted by relevance
12345
7 #define MSG_TASK_COMPLETE 0x00 /* M/M */ /* SPI3 Terminology */14 #define MSG_ABORT_TASK_SET 0x06 /* O/M */ /* SPI3 Terminology */21 #define MSG_TARGET_RESET 0x0c /* O/M */ /* SPI3 Terminology */23 #define MSG_ABORT_TASK 0x0d /* O/O */ /* SPI3 Terminology */25 #define MSG_CLEAR_TASK_SET 0x0e /* O/O */ /* SPI3 Terminology */35 #define MSG_SIMPLE_TASK 0x20 /* O/O */ /* SPI3 Terminology */37 #define MSG_HEAD_OF_QUEUE_TASK 0x21 /* O/O */ /* SPI3 Terminology */39 #define MSG_ORDERED_TASK 0x22 /* O/O */ /* SPI3 Terminology */
6 The implementation follows the terminology used in the Maxim AN92711 stack terminology used by AN927. The 1-wire bus is implemented in the ow(4)
13 …gained by reading the <a href="HTML/Kerberos_Terminology.htm">Kerberos terminology</a> page. You d…18 <li><a href="HTML/Kerberos_Terminology.htm">Kerberos terminology</a></li>
15 …ins. <br><a href="HTML/Kerberos_Terminology.htm#realm">About: Kerberos Terminology (Realms)</a></d…39 …e. <br><a href="HTML/Kerberos_Terminology.htm#ticket">About: Kerberos Terminology (Tickets)</a> <…47 <br><a href="HTML/Kerberos_Terminology.htm#realm">About: Kerberos Terminology (Realms)</a>
5 <title>Kerberos Terminology</title></head>8 <h1><a name="top"> Kerberos Terminology</a></h1>
62 <li><a href="HTML/Kerberos_Terminology.htm">Kerberos terminology</a></li>
99 <param name="Name" value="Kerberos Terminology">210 <param name="Name" value="key terminology">211 <param name="Name" value="Kerberos Terminology">279 <param name="Name" value="Kerberos Terminology">310 <param name="Name" value="Kerberos Terminology">
15 This document uses some terminology common to the RISC-V community20 terminology is designed to disambiguate software's view of execution
15 - Terminology30 attempts to include terminology used by both major FPGA manufacturers. This35 Terminology
7 - Terminology23 attempts to include terminology used by both major FPGA manufacturers. This28 Terminology
408 and derives its terminology accordingly.455 and derives its terminology accordingly.
5 CPU core (HART in RISC-V terminology) and can be read or written by software.
11 each CPU core (HART in RISC-V terminology) and can be read or written by
83 terminology).
6 .Ss Terminology
67 .Ss Terminology
120 .Sh "TERMINOLOGY AND TOPOLOGY"122 is quite object oriented and consequently the terminology
162 other platforms, and adopt their terminology.
160 other platforms, and adopt their terminology.
65 terminology:
36 * and terminology slightly differ.
13 // Terminology:
32 * present them as vendor and device IDs (a terminology we understand for
36 # vm_map_split() for the orig/new objects terminology). This can happen
63 // The original value type of a byte in app memory. Uses LLVM terminology: