Re: RSB format changes to meet coding standard
On 19/4/2024 7:15 pm, andrew.butterfi...@scss.tcd.ie wrote: > Will you also do this with the formal code in rtems-central/formal ? Sorry, I do not use it so would prefer not to update it just yet. I think it best left to the leaders of that repo. > I do remember using yapf at some point – I have no problem in your doing this > here. Great. > I expect to be proposing an update to the formal stuff > (models,code,documentation) over the Summer period as well. Great and looking forward to see the results. We will be on GitLab soon and that will help us all with merge requests as well as coordinating these activities, for example GitLab has Epics. Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: [PATCH] bsps/powerpc: Introduction of interrupt locks
On 19/4/2024 6:12 pm, Christian MAUDERER wrote: > it is tested on an MVME2500 which uses the powerpc/qoriq_e500 in an SMP > configuration. Great and thanks. I should have access next week to MVME2700 hardware and can test it there. I doubt there will be an issue looking at the change but this group of BSPs has had issues in the past, eg interrupts on some boards did not work for over 10 years after a change, ie RTEMS 4.10 until 5. I am OK to push the change and if I find anything I will raise it. Thanks Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
RTEMS 6 branching
Hi, There has been some discussion about when we will branch and it is timely we discuss this. This is my input. :) While I create the releases I am not solely responsible for milestone dates or thresholds for a release. Please test the RC snaphots on our ftp server. Saying you have is as important as reporting issues. 1. Are all the things need for the release resolved? Tickets reviewed? 2. The tickets are now in GitLab and locked down in Trac so how does that work if we make a release now? I do not think it does. 3. GitLab is going to happen soon so do we take this moment in time and make 6 with GitLab and learn what we need to do easing dot releases that always follow? If we do not we may end up with 6.1 and then 6.2 that has differences. 4. GitLab breaks the release scripts for the release notes (ChangeLog). Amar and I have discussed a few options but we are yet to test and settle on anything. As is the case with these things easy is often is a series of small things that take time to get right. 5. Have the docs been reviewed for RTEMS 5 vs RTEMS 6 changes? Are they updated for a separated legacy network stack, net services and waf building? 6. I have a few small patches to push and then an update to the RSB to pick those changes up before I can create RC4. Thanks Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
