Kaspar Schleiser
Kaspar Schleiser
> Probably we should also add an arch-independent wrapper around `thread_yield*()` to assert interrupts are enabled. That would also make sense. Currently, core code does `irq_restore(...); thread_yield_higher()`. depending on the...
Why not a bit field for the pids that want to be group members?
Simple but useful. I like. :+1:
Thanks for the report! Yeah there's probably more spots where unix slashes are used. I'm on leave this week, will try to come up with a fix next week.
Ok, I actually see two issues here: 1. laze itself sometimes uses `/` separators, understands both, but then mixes them by using `push()` on unix paths on windows. This leads...
> Needs #799 for the CI, and I have to take a look where the nightly test is failing exactly #799 is optional, though it would be nice to briefly...
> A number of `println!`s have a "laze:" at the start of the output. Do you want to retain that, and should that be in the main log `write!` template...
> I was just thinking whether RIOT makes sense to be working on a slave. I would say yes. The use case would be an intellegent sensor. +1 It might...
> Is there an actual use case for running laze without any subcommand? Printing the help is certainly better than the current state. I'd rather have some descriptive message, maybe...
> MO the solution is to use `setcontext` instead of `swapcontext` in the trampoline function. But this would require to keep the state of the last thread somewhere. is there...