TaiJuWu

> In the single core, spinlock map to disable/enable irq Oh, I made a mistake. If I want to replace mutex with spinlock, I should use `spinlock_irqsave()` and `spinlock_irqrestore()`. In...

> > Hi @xiaoxiang781216, > > Do you know why some platform not config spinlock? Even in 1cpu, in multi-threading environment spinlock is also needed. > > How do you...

> @TaiJuWu Which configuration does the CI use to check this PR? You can see the related log of CI. https://github.com/apache/nuttx/pull/11769#discussion_r1526280639

> > > @TaiJuWu Which configuration does the CI use to check this PR? > > > > > > You can see the related log of CI. [#11769 (comment)](https://github.com/apache/nuttx/pull/11769#discussion_r1526280639)...

> @TaiJuWu the initial support to Raspberry Pi board (the first board) was removed by Greg some years ago because nobody was interested to still working in the port: https://bitbucket.org/patacongo/obsoleted/src/master/Patches/Remove-arch-bcm2708-2019-01-02.patch...

> Checking if this is in development at all? I am interested in contributing to get support for this board. No, I am not working on it. Welcome to take...

If I am not wrong. This is not issue about nuttx, just the different version of python package. Maybe you can try this PR #10879

I found taking spinlock will disable interrupt and enable interrupt when releasing spinlock in zephyr project. It can avoid the spinlock holder be blocked. Maybe we could follow them? reference:...

Current [mm_delay_list](https://github.com/apache/nuttx/blob/b6e09955ddae3484251c632501375ce6e5006295/mm/mm_heap/mm_free.c#L48) is protected by spinlock and only one CPU can operate mm_delay_list. But there is a mm_delay_list for each CPU, it will make this issue and delay_list for each...

> > I found taking spinlock will disable interrupt and enable interrupt when releasing spinlock in zephyr project. > > It can avoid the spinlock holder be blocked. Maybe we...