Home
last modified time | relevance | path

Searched full:implemented (Results 1 – 25 of 215) sorted by relevance

123456789

/nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/doc/
H A Dsys_arch.txt14 lwIP functionality, multiple threads support can be implemented in the
16 functionality. Timer scheduling is implemented in lwIP, but can be implemented
25 kinds. Mailboxes should be implemented as a queue which allows multiple messages
41 The following functions must be implemented by the sys_arch:
55 no real error handling is implemented.
102 no real error handling is implemented.
138 no real error handling is implemented.
171 implemented by lwIP.
202 to be implemented as well:
/nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/src/core/
H A Dsys.c46 * The OS-specific code should be implemented in arch/sys_arch.h
57 * lwIP functionality, multiple threads support can be implemented in the
59 * functionality. Timer scheduling is implemented in lwIP, but can be implemented
96 * Mailboxes should be implemented as a queue which allows multiple messages
123 /* Most of the functions defined in sys.h must be implemented in the
/nrf52832-nimble/rt-thread/components/net/lwip-1.4.1/doc/
H A Dsys_arch.txt13 lwIP functionality, multiple threads support can be implemented in the
17 implemented in a higher layer.
25 kinds. Mailboxes are used for message passing and can be implemented
42 The following functions must be implemented by the sys_arch:
56 no real error handling is implemented.
105 no real error handling is implemented.
138 implemented by lwIP.
169 to be implemented as well:
/nrf52832-nimble/nordic/nrfx/
H A DCHANGELOG.md70 - Implemented workaround for nRF52832 and nRF52840 anomaly 194 in the I2S driver.
71 - Implemented workaround for nRF52840 anomaly 195 in the SPIM driver.
93 - Implemented workarounds for nRF52 anomalies 192 and 201 in the CLOCK driver.
94 - Implemented workaround for nRF52840 anomaly 122 in the QSPI driver.
95 - Implemented workaround for nRF52840 anomaly 198 in the SPIM driver.
115 - Implemented Errata 132 in the CLOCK driver.
/nrf52832-nimble/rt-thread/components/net/uip/doc/
H A Dpt-doc.txt7 event-driven systems implemented in C. Protothreads can be used with
20 implemented by manually breaking the function into two pieces - one
100 memory per protothread. Moreover, protothreads are implemented in pure
136 Protothreads are implemented using \ref lc "local continuations". A
145 Local continuations can be implemented in a variety of ways:
H A Duip-doc.txt71 application". Lower layer protocols are often implemented in hardware
107 are implemented. However, in order to reduce code size, we have
140 uIP requires a few functions to be implemented specifically for the
167 uIP leaves the 32-bit additions to be implemented by the architecture
259 of uIP is implemented as a C function that is called by uIP in
302 The application must be implemented as a C function, UIP_APPCALL(),
305 events. The functions are implemented as C macros that will evaluate
522 the application is implemented. The reason for the increase in
754 the protocol that is being implemented.
878 implemented as empty functions.
[all …]
/nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/src/include/lwip/
H A Dsys.h100 /* Function prototypes for functions to be implemented by platform ports
132 * no real error handling is implemented.
189 * no real error handling is implemented.
279 * no real error handling is implemented.
329 * implemented by lwIP.
449 /* These functions must be implemented in the sys_arch.c file.
472 * Perform a "fast" protect. This could be implemented by
477 * which should be implemented in sys_arch.c. If a particular port needs a
485 * implemented by setting the interrupt level to "lev" within the MACRO or by
487 * sys_arch_unprotect() function which should be implemented in
H A Dsio.h32 * It needs to be implemented by those platforms which need SLIP or PPP
52 or be implemented in your custom sio.c file. */
/nrf52832-nimble/rt-thread/components/net/uip/apps/webclient/
H A Dwebclient.h79 * This function must be implemented by the module that uses the
96 * This function must be implemented by the module that uses the
105 * This function must be implemented by the module that uses the
115 * This function must be implemented by the module that uses the
124 * This function must be implemented by the module that uses the
/nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/src/apps/httpd/
H A Dhttpd_structs.h22 "HTTP/1.0 501 Not Implemented\r\n",
26 "HTTP/1.1 501 Not Implemented\r\n",
42 #define HTTP_HDR_NOT_IMPL 3 /* 501 Not Implemented */
46 #define HTTP_HDR_NOT_IMPL_11 7 /* 501 Not Implemented */
/nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/src/apps/http/
H A Dhttpd_structs.h20 "HTTP/1.0 501 Not Implemented\r\n",
24 "HTTP/1.1 501 Not Implemented\r\n",
40 #define HTTP_HDR_NOT_IMPL 3 /* 501 Not Implemented */
44 #define HTTP_HDR_NOT_IMPL_11 7 /* 501 Not Implemented */
/nrf52832-nimble/rt-thread/components/net/lwip-1.4.1/
H A DUPGRADING39 * correctly implemented SO(F)_REUSEADDR
126 * Implemented tcp_shutdown() to only shut down one end of a connection
127 * Implemented shutdown() at socket- and netconn-level
132 * Implemented many nonblocking socket/netconn functions
/nrf52832-nimble/rt-thread/components/net/lwip-1.4.1/src/include/lwip/
H A Dsys.h91 /* Function prototypes for functions to be implemented by platform ports
241 /* These functions must be implemented in the sys_arch.c file.
260 * Perform a "fast" protect. This could be implemented by
265 * which should be implemented in sys_arch.c. If a particular port needs a
271 * implemented by setting the interrupt level to "lev" within the MACRO or by
273 * sys_arch_unprotect() function which should be implemented in
H A Dsio.h32 * It needs to be implemented by those platforms which need SLIP or PPP
51 or be implemented in your custom sio.c file. */
/nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/src/include/lwip/
H A Dsys.h100 /* Function prototypes for functions to be implemented by platform ports
353 /* These functions must be implemented in the sys_arch.c file.
376 * Perform a "fast" protect. This could be implemented by
381 * which should be implemented in sys_arch.c. If a particular port needs a
389 * implemented by setting the interrupt level to "lev" within the MACRO or by
391 * sys_arch_unprotect() function which should be implemented in
H A Dsio.h32 * It needs to be implemented by those platforms which need SLIP or PPP
52 or be implemented in your custom sio.c file. */
/nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/
H A DUPGRADING130 * correctly implemented SO(F)_REUSEADDR
217 * Implemented tcp_shutdown() to only shut down one end of a connection
218 * Implemented shutdown() at socket- and netconn-level
223 * Implemented many nonblocking socket/netconn functions
/nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/
H A DUPGRADING173 * correctly implemented SO(F)_REUSEADDR
260 * Implemented tcp_shutdown() to only shut down one end of a connection
261 * Implemented shutdown() at socket- and netconn-level
266 * Implemented many nonblocking socket/netconn functions
/nrf52832-nimble/rt-thread/components/net/uip/apps/telnetd/
H A Duip_shell.h6 * Some of the functions declared in this file must be implemented as
84 * This function is implemented by the shell GUI / telnet server and
/nrf52832-nimble/packages/NimBLE-latest/nimble/controller/
H A Dsyscfg.yml213 procedure. This is implemented in the controller but is disabled
220 procedure. This feature is implemented but currently has no impact
227 Currently, this feature is not implemented by the controller so
/nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/src/include/lwip/prot/
H A Ddhcp.h109 DHCP_STATE_PERMANENT = 9, /* not yet implemented */
111 DHCP_STATE_RELEASING = 11, /* not yet implemented */
/nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/src/include/lwip/prot/
H A Ddhcp.h111 DHCP_STATE_PERMANENT = 9, /* not yet implemented */
113 DHCP_STATE_RELEASING = 11, /* not yet implemented */
/nrf52832-nimble/rt-thread/components/CMSIS/
H A DKconfig9 Enable CMSIS RTOS API, which is implemented above RT-Thread.
/nrf52832-nimble/rt-thread/documentation/doxygen/
H A Dmodule.h10 * Application Module is implemented as dynamic object loader, but it can handle
/nrf52832-nimble/rt-thread/components/net/uip/doc/html/
H A Dmain.html34 …l be referred to as "the application". Lower layer protocols are often implemented in hardware or …
38 In uIP, all RFC requirements that affect host-to-host communication are implemented. However, in or…
47 uIP requires a few functions to be implemented specifically for the architecture on which uIP is in…
52 …forms for which uIP is intended, uIP leaves the 32-bit additions to be implemented by the architec…
66 …in response to certain events. An application running on top of uIP is implemented as a C function…
70implemented as a C function, <a class="el" href="a00153.html#g41aa744caa46913b3b3aedb2a4e78546">UI…
130 …l change of operation makes a big difference in how the application is implemented. The reason for…
273 …and timedout(), and needs to be written specifically for the protocol that is being implemented.<p>
365 …ts, and therefore the aborted(), timedout() and closed() functions are implemented as empty functi…
377 IP fragment reassembly is implemented using a separate buffer that holds the packet to be reassembl…
[all …]

123456789