Uthedris
Uthedris
I’ll make the changes. > On 12 Nov 24, at 16:16, Alex Rønne Petersen ***@***.***> wrote: > > > @curuvar do you think you'll be able to address my review...
I made the requested changes and added: sched_getcpu sched_getattr sched_setattr sched_rr_get_interval and "getcpu" as it was needed for sched_getcpu.
Throwing in my two cents -- one of the strengths of a HAL is that you don't have to remember all the fiddly-bits of multiple different processors to do simple...
I have a test suit that I used. ~~Is there someplace where I should put it in the microzig directory?~~ I'll move it into the test directory.
Looking closer, I'm not sure how to proceed with adding tests. ~~I'm adding a zig test case to the allocator itself. That would run on the machine doing the compilation,...
OK. I'm planning on using it for some stuff I'm doing, but I can just use my fork of microzig for that. I'll keep the PR open, and when there...
There is an example program in `examples/raspberrypi/rp2xxx/src/allocator.zig` that tests the allocator.
If by "run on a host," you mean to run on the machine where the code is compiled, the problem is that the mutex code suspends interrupts and, since that...
This error still exists as of the date of this comment. 23 May 2025 The patch mentioned above fixes the error. Thank You! BTW, to apply patch after download, from...
I'd think the default should be platform dependent. Putting the stack first does not solve the overflow problem on all platforms. The ATmega328 for example starts internal SRAM at 0x0100...