Hi Katsuhiro and Andy, <katsuhiro@...> wrote: Ah, OK. I didn't answer your question at all. And I don't have the answer. Andy, would you mind telling us if you have any comments about the ra

Hi, <katsuhiro@...> wrote: The reason why we set _current to the new thread is that we can't set it after we switch to the new thread. The newly switched thread will just start running from

Hi, <katsuhiro@...> wrote: Does RISC-V support USE_SWITCH? AFAICS, even with v1.11, we are setting `_current` to `new_thread` in `_Swap()` before calling `_arch_switch()`. What version are y

Hi,

Hi, Can a regular contributor do this? Using a mention? I'd love to fix scripts/get_maintainer.py in order to find who to ask. If you don't have write permission, you can't add any label, right?

Hi, Do you mean by "apps" to create multiple images for multiple boards, or multiple threads in one image? Zephyr is not like Linux; meaning that you don't have multiple apps running on a board. Rathe

#nrf52840

Hi Gil, It's nice to see someone using TI CGT! I've been working on it but the current Zephyr code base has many GCC-ism's. Most challenging part of it is the final linking. In parts, CGT's pre-proces

Hi, # I don't think it's a good idea to multi-post. # make sure not to do so next time. $ git fetch --all $ git pull $YOUR_REMOTE origin/master:master $ git fetch --all $ git checkout master $ git mer