Lines Matching full:be
14 lwIP functionality, multiple threads support can be implemented in the
16 functionality. Timer scheduling is implemented in lwIP, but can be implemented
24 Semaphores can be either counting or binary - lwIP works with both
25 kinds. Mailboxes should be implemented as a queue which allows multiple messages
26 to be posted (implementing as a rendez-vous point where only one message can be
37 allows both using pointers or actual OS structures to be used. This way, memory
38 required for such types can be either allocated in place (globally or on the
41 The following functions must be implemented by the sys_arch:
50 points to (which can be both a pointer or the actual OS structure).
53 If the semaphore has been created, ERR_OK should be returned. Returning any
67 Blocks the thread while waiting for the semaphore to be
69 only be blocked for the specified time (measured in
70 milliseconds). If the "timeout" argument is zero, the thread should be
74 milliseconds spent waiting for the semaphore to be signaled. If the
86 When directly using OS structures, implementing this may be more complex.
87 This may also be a define, in which case the function is not prototyped.
92 ATTENTION: This does NOT mean that the semaphore shall be deallocated:
94 This may also be a define, in which case the function is not prototyped.
99 points to (which can be both a pointer or the actual OS structure).
100 If the mutex has been created, ERR_OK should be returned. Returning any
110 Blocks the thread until the mutex can be grabbed.
120 When directly using OS structures, implementing this may be more complex.
121 This may also be a define, in which case the function is not prototyped.
126 ATTENTION: This does NOT mean that the mutex shall be deallocated:
128 This may also be a define, in which case the function is not prototyped.
136 If the mailbox has been created, ERR_OK should be returned. Returning any
144 programming error in lwIP and the developer should be notified.
161 be blocked until a message arrives. The "msg" argument is a result
164 should be dropped.
179 To allow for efficient implementations, this can be defined as a
181 example, a naive implementation could be:
190 When directly using OS structures, implementing this may be more complex.
191 This may also be a define, in which case the function is not prototyped.
196 ATTENTION: This does NOT mean that the mailbox shall be deallocated:
198 This may also be a define, in which case the function is not prototyped.
202 to be implemented as well:
207 execution in the function "thread()". The "arg" argument will be passed as an
213 main-loop and from interrupts), the SYS_LIGHTWEIGHT_PROT protection SHOULD be enabled!
223 other words, sys_arch_protect() could be called while already protected. In
248 Be careful with using mem_malloc() in sys_arch. When malloc() refers to
251 can't be performed when sys_arch uses mem_malloc.
290 Measurement calls made throughout lwip, these can be defined to nothing.