Searched refs:wants (Results 1 – 25 of 36) sorted by relevance
12
22 application wants to collect statistics for further processing. The network
51 before continuing. This means in practice that the application wants to wait
210 802.15.4 L2 is the technology one wants to listen to events.
160 option. A network driver that wants to register a new socket implementation
41 bool "This application wants IPv6 support"49 bool "This application wants IPv6 router to exists"53 What this means that the application wants to wait until it receives57 bool "This application wants IPv4 support"
73 # happens. The libc heap normally wants to steal all of it, when in
154 * specific) stuff that wants to go to a IDT_LIST memory area. We
31 A thread that wants to wait on multiple conditions must define an array of39 Each event must specify what **kernel object** it wants the condition to be146 can wait in it as the app wants.
51 * This makes life easier for software that wants to deal with
38 Solicitation UUID, encrypted with the network key of the subnet that the legacy device wants to
92 If the application wants to support public key exchange via OOB, it needs to151 If Provisionee wants to mandate OOB authentication, it is mandatory to use
232 to any consuming thread that wants one. The message "info" field is262 from a producing thread to any consuming thread that wants it.305 characterizes the message it wants to receive. It then calls one of the418 wants to retrieve the data, the thread must call :c:func:`k_mbox_data_get`
50 If the default configuration wants to be overwritten via the command line and not via a options
128 if the code wants to check that the link address is not set.
37 If one wants to include a new backend it needs to create a new wrapper for that library or backend.
16 To lock a set, the client must connect to each of the set members it wants to
66 If this is disabled, it means the app wants to be give the opportunity
118 Each network interface that wants to act as a DHCPv4 server requires
355 Root cell wants to use the **UART** which let's say has its registers mapped in356 the **[0x0 - 0x42000000]** region. If the inmate wants to use the same **UART** for
128 Each core shall be build with that snippet. If any core wants to use it then application core is190 Each core shall be build with that snippet. If any core wants to use it then application core is
375 * wants to use the cache
64 application wants a particular device to be always active.
400 # level multiprocessor API that wants an auxiliary CPU but doesn't
91 useful when one wants to select a specific testcase from a test suite. For instance, one can use
446 * wants to use the cache
