Closed dreamliner787-9 closed 1 month ago
If you are adding a dependency on libmicrokitco and libmicrokitco contains a copy of libco, why update the libco in the Lions OS repository instead of just removing it?
If you are adding a dependency on libmicrokitco and libmicrokitco contains a copy of libco, why update the libco in the Lions OS repository instead of just removing it?
Just in case someone still need it, but I'm happy to remove it.
lionsos/libco
should be removed. Whether libmicrokitco
lives in Microkit, LionsOS, or as its own repo we can discuss later.
Before reviewing this PR I'll first look at design/code for libmicrokitco in more detail.
This pull request:
lib/libco
libco
tolibmicrokitco
:MICROKIT_MAX_CHANNELS
) event sources are now possible. We are no longer limited by the 32-bitsint
bitfield, consequently, the event source abstraction is no longer needed.libco
primitives' memory layout has been updated. The registers region now comes after the stack top. If Micropython or other clients usinglibmicrokitco
overflow the stack, it won't overwrite the registers region.