Home
last modified time | relevance | path

Searched refs:OS (Results 1 – 5 of 5) sorted by relevance

/lib/liblwip/doc/
Dsys_arch.txt20 the OS emulation layer must provide several header files defining
38 allows both using pointers or actual OS structures to be used. This way, memory
51 points to (which can be both a pointer or the actual OS structure).
87 When directly using OS structures, implementing this may be more complex.
157 When directly using OS structures, implementing this may be more complex.
218 Additional files required for the "OS support" emulation layer:
Dcontrib.txt60 1. If you have ported lwIP to a platform (an OS, a uC/processor or a combination of these) and
/sys/amd64/
Ddisasm.c104 #define OS 30 /* immediate offset/segment */ macro
813 /*9a*/ { "lcall", FALSE, NONE, op1(OS), 0 },
903 /*ea*/ { "ljmp", FALSE, NONE, op1(OS), 0 },
1617 case OS: in db_disasm()
/lib/liblwip/
DCHANGELOG1738 in your sys_arch.c file, and but it's not mandatory, use them in your OS
2372 some macro names collision with some OS macros.
2678 initialized before tcpip_thread is running (e.g. before OS is started)
/docs/
DDoxyfile1809 # (what the <access key> is depends on the OS and browser, but it is typically