Re: Make nxboot img_header public?

Thanks for the input everyone. Discussion was very useful and here is the PR that followed, and did not result in the exposure of the nxboot struct to the kernel On 05/05/2025 18:53, Alin Jerpelea wrote: On Tue, Apr 29, 2025 at 7:49 PM Tim Hard

Re: sched lock/unlock issue on rp2350

WOW! Nice catch! Question to some people with more experience in the scheduler: Why wasn't this issue detected before? It was added more than 9 months ago. Is there some way to test and enforce that nxsched_process_delivered() and other schedule functions are working as expected? BR, Alan On

Re: sched lock/unlock issue on rp2350

Hi Serg, I did an analysis here and this macro was introduced in Jan 10 2024, so it was more than 1 year ago: https://github.com/apache/nuttx/commit/9de9f8168d6de8eab8d3a97aac21aacc4e84dd84 BR, Alan On Tue, May 6, 2025 at 1:12 PM Alan C. Assis wrote: > WOW! Nice catch! > > Question to some p

Re: sched lock/unlock issue on rp2350

This file: https://github.com/apache/nuttx/commit/9de9f8168d6de8eab8d3a97aac21aacc4e84dd84#diff-ac1d3cade3d9ab380d40fe31f8c006b3035c7b53d04c28e23d9f1ce9a176572c On Tue, May 6, 2025 at 1:18 PM Alan C. Assis wrote: > Hi Serg, > > I did an analysis here and this macro was introduced in Jan 10 2024,

Re: sched lock/unlock issue on rp2350

Hi, I am still researching the sched problem on my config Found this macro code  from last September,  looks like pre vs prev  typo, right? #definedq_insert_mid(pre,mid,next)\ do\ {\ mid->flink =next;\ mid->blink =prev;\ pre->flink =mid;\ next->blink =mid;\ }\ while(0) On 4/24/25 15:06, huj

GitHub NuttX master branch protections

Hello world :-) I found a free moment to setup github master branch protections as discussed before, for now PR is in Draft mode for careful review. Who can we contact from Apache Admins to ask to verification? https://github.com/apache/nuttx/pull/16324 * We do not have "Settings" tab in the Apa

Re: GitHub NuttX master branch protections

Hello Tomek :-) Thanks for doing that! I have found that the easiest/quickest way to talk to the Infra folks is by Slack [1]. If you don't want to use Slack, you can write to Infra's users list (also see [1]). I recommend to try slack, but either way, give them the link to the PR and ask nicely

Re: RFC - AVR fixes and support for AVR DA/DB family

Alan just posted the PR with your AVR updates :-) https://github.com/apache/nuttx/pull/16323 Thank you! :-) Tomek On Tue, May 6, 2025 at 2:37 AM Tomek CEDRO wrote: > > Okay, git clone works from that location, I pushed the PR but Alan is > working on this one too so he takes over, thanks for y

Re: GitHub NuttX master branch protections

Thank you Nathan :-) I have talked with @Humbedooh on Slack, he said the config looks okay :-) I am not really sure about this "contexts" part, particularly the exact naming convention in GitHub, so I am leaving this for now and hope it wont break anything :-) contexts: - Check

Re: sched lock/unlock issue on rp2350

Yeah, but this macro is working because of coincidental match with variable prev already defined in the scope. On 5/6/25 23:19, Alan C. Assis wrote: This file: https://github.com/apache/nuttx/commit/9de9f8168d6de8eab8d3a97aac21aacc4e84dd84#diff-ac1d3cade3d9ab380d40fe31f8c006b3035c7b53d04c28e23d

Re: GitHub NuttX master branch protections

Looks good and looks like it has been merged! Thank you Tomek for tackling this!!! Cheers, Nathan On Tue, May 6, 2025 at 4:46 PM Tomek CEDRO wrote: > Thank you Nathan :-) > > I have talked with @Humbedooh on Slack, he said the config looks okay :-) > > I am not really sure about this "contexts"

Enhancing documentation

Hello everyone, I just opened a PR here for migrating some of the README.txt files to RST files (for board documentation, https://github.com/apache/nuttx/pull/16328). This is part of the long list of old README files that need to be migrated, all laid out in issue #11077 (https://github.com/apac

Re: RFC - AVR fixes and support for AVR DA/DB family

I noticed, thanks. To reply to the comments and feedback in the PR: 1. The discussion about AVR_LINUXGCC_TOOLCHAIN_IS_GCC - my overall goal was to minimize changes for boards and AVR families I am not using (and have no experience with them and, most importantly, cannot test.) Setting DEBUG_O