Searched refs:remain (Results 1 - 5 of 5) sorted by relevance
| /seL4-refos-master/libs/libplatsupport/src/arch/arm/ |
| H A D | i2c.c | 218 int remain = count; local
226 while (remain > 0) {
227 this = _do_kvread(kvs, reg, data, remain);
233 remain -= this;
235 return count - remain;
248 int remain = count; local
256 while (remain > 0) {
257 this = _do_kvwrite(kvs, reg, data, remain);
262 remain -= this;
265 return count - remain;
[all...] |
| /seL4-refos-master/projects/util_libs/libplatsupport/src/arch/arm/ |
| H A D | i2c.c | 218 int remain = count; local
226 while (remain > 0) {
227 this = _do_kvread(kvs, reg, data, remain);
233 remain -= this;
235 return count - remain;
248 int remain = count; local
256 while (remain > 0) {
257 this = _do_kvwrite(kvs, reg, data, remain);
262 remain -= this;
265 return count - remain;
[all...] |
| /seL4-refos-master/kernel/manual/parts/ |
| H A D | threads.tex | 189 will remain in the queue and can still recieve messages and signals. However, the unbound thread
224 scheduling context will remain where it is. If the receiver does not provide a reply object to
230 scheduling context, B's reply cap to A is revoked, then the scheduling context will remain with C.
231 However, a call chain will remain between A and C, such that if C's reply cap is revoked, or
|
| /seL4-refos-master/projects/refos/impl/apps/nethack/src/nethack-3.4.3/doc/ |
| H A D | Guidebook.tex | 1077 Walls and corridors remain on the map as you explore them.
|
| /seL4-refos-master/apps/nethack/src/nethack-3.4.3/doc/ |
| H A D | Guidebook.tex | 1077 Walls and corridors remain on the map as you explore them.
|
Completed in 49 milliseconds