[PATCH 1/2] c-user: CONFIGURE_APPLICATION_DISABLE_FILESYSTEM

Improve formatting. --- c-user/config/filesystem.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/c-user/config/filesystem.rst b/c-user/config/filesystem.rst index b429a4f..8d1efbd 100644 --- a/c-user/config/filesystem.rst +++ b/c-user/config/filesystem.rst @@ -66,8 +66,

[PATCH 2/2] c-user: Improve refs and formatting in appl config

The formatting is generated through references within the specification. Update #3994. --- c-user/config/bdbuf.rst | 18 c-user/config/bsp-related.rst | 12 +++--- c-user/config/classic-api.rst | 2 +- c-user/config/classic-init-task.rst | 12 +++--- c-user/confi

[PATCH] user: Add shell environment migration aid

Close #3859. --- user/migration/v4_11-to-v5.rst | 27 +++ 1 file changed, 27 insertions(+) diff --git a/user/migration/v4_11-to-v5.rst b/user/migration/v4_11-to-v5.rst index a0cab02..0e0fb46 100644 --- a/user/migration/v4_11-to-v5.rst +++ b/user/migration/v4_11-to-v5.rst @

Configuration option for thread-stack protection.

Hello, The thread-stack protection needs to be configured by the user. Two of the options that need configuring during build time are - > Enabling thread stack protection ( THREAD_STACK_PROTECTION )- This is a high-level option similar to RTEMS_SMP, RTEMS_POSIX_API etc. > Size of the MMU pages - T

Re: Configuration option for thread-stack protection.

On 06/08/2020 14:12, Utkarsh Rai wrote: Hello, The thread-stack protection needs to be configured by the user. Two of the options that need configuring during build time are - > Enabling thread stack protection ( THREAD_STACK_PROTECTION )- This is a high-level option similar to RTEMS_SMP, RTEM

[PATCH v2 0/1] Generate application configuration option documentation

This patch adds the application configuration option documentation generated from specification items: https://git.rtems.org/rtems-central.git/tree/spec/if/acfg The header file is generated by the following script and module: https://git.rtems.org/rtems-central.git/tree/spec2doc.py https://git.

[PATCH v2 1/1] Document application configuration options

Add a new directory for Doxygen-specific documentation content. Add a Doxygen only header file containing documentation of the application configuration options. The header file is generated from specification items. Update #3994. --- cpukit/doxygen/appl-config.h | 4182

Re: Explanation about the high level design choices of Strong APA

Thanks for the detailed write-up. My only concern with your choice is whether these two function pointers, get_highest_ready and get_lowest_ready, will get called along other paths when there hasn't been a task arrival/departure? This shouldn't cause a correctness problem, but it may cause a perfor

Re: Configuration option for thread-stack protection.

On Thu, Aug 6, 2020 at 6:21 AM Sebastian Huber wrote: > > On 06/08/2020 14:12, Utkarsh Rai wrote: > > > Hello, > > The thread-stack protection needs to be configured by the user. Two of > > the options that need configuring during build time are - > > > Enabling thread stack protection ( THREAD_ST

Re: [PATCH] user: Add shell environment migration aid

ok to apply to rtems-docs/5 and master On Thu, Aug 6, 2020 at 5:31 AM Sebastian Huber wrote: > > Close #3859. > --- > user/migration/v4_11-to-v5.rst | 27 +++ > 1 file changed, 27 insertions(+) > > diff --git a/user/migration/v4_11-to-v5.rst b/user/migration/v4_11-to-v5.r

Re: [PATCH] user: Add shell environment migration aid

On Thu, Aug 6, 2020 at 9:07 AM Gedare Bloom wrote: > > ok to apply to rtems-docs/5 and master > Although, do we want to keep the v4_11-to-v5.rst in master? > On Thu, Aug 6, 2020 at 5:31 AM Sebastian Huber > wrote: > > > > Close #3859. > > --- > > user/migration/v4_11-to-v5.rst | 27

Re: Explanation about the high level design choices of Strong APA

Yes, This is a serious issue. I will work on finding this and documenting each case to make sure that there are no loose ends. Meanwhile, please have a look at the low-level description. Thank you for the review. On Thu, Aug 6, 2020 at 8:12 PM Gedare Bloom wrote: > Thanks for the detailed writ

Low level design description for _Scheduler_strong_APA_Get_lowest_scheduled

Hi, Please find the blog post- https://rtemswithrichi.wordpress.com/strong-apa-low-level-design-in-rtems/ that explains the low-level design for get_lowest_function, importance of which was explained in the earlier high-level design description mail

Re: [PATCH v2 0/1] Generate application configuration option documentation

On Thu, Aug 6, 2020 at 7:16 AM Sebastian Huber wrote: > > This patch adds the application configuration option documentation generated > from specification items: > > https://git.rtems.org/rtems-central.git/tree/spec/if/acfg > > The header file is generated by the following script and module: > >

Re: Low level design description for _Scheduler_strong_APA_Get_lowest_scheduled

The part 3 corresponding to the backtracking changes the filter_node pointer (the original node pointer passed to the function) and calls the Scheduler_SMP_Preempt, all of which is documented in the blog post. I feel like this might mean that the file is taking a higher-level role that it is suppos

Re: Configuration option for thread-stack protection.

On Thu, Aug 6, 2020 at 8:34 PM Gedare Bloom wrote: > On Thu, Aug 6, 2020 at 6:21 AM Sebastian Huber > wrote: > > > > On 06/08/2020 14:12, Utkarsh Rai wrote: > > > > > Hello, > > > The thread-stack protection needs to be configured by the user. Two of > > > the options that need configuring durin

Re: [PATCH 1/2] eng: Add application config options how-to

Thanks for this. I saw just a few typos and grammatical fixes/suggestions. On Wed, Aug 5, 2020 at 11:47 PM Sebastian Huber wrote: > > Update #3715. > --- > eng/req/howto.rst | 118 ++ > 1 file changed, 118 insertions(+) > > diff --git a/eng/req/howto.r

Re: [PATCH] user: Add shell environment migration aid

On 06/08/2020 17:07, Gedare Bloom wrote: ok to apply to rtems-docs/5 and master Unfortunately this fix doesn't work: https://devel.rtems.org/ticket/3859#comment:23 ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: Low level design description for _Scheduler_strong_APA_Get_lowest_scheduled

Hi Richi, I have a question about: "scenario where all the nodes that we go through have a higher priority (less priority number) than our filter_node(the node to schedule) in which case, we would be returning ret: the minimum priority node encountered but there would be no preemptions and filter_

Re: [PATCH v2 0/1] Generate application configuration option documentation

On 06/08/2020 17:17, Gedare Bloom wrote: On Thu, Aug 6, 2020 at 7:16 AM Sebastian Huber wrote: This patch adds the application configuration option documentation generated from specification items: https://git.rtems.org/rtems-central.git/tree/spec/if/acfg The header file is generated by the

Re: [PATCH v2 0/1] Generate application configuration option documentation

On Thu, Aug 6, 2020 at 11:57 AM Sebastian Huber wrote: > > On 06/08/2020 17:17, Gedare Bloom wrote: > > > On Thu, Aug 6, 2020 at 7:16 AM Sebastian Huber > > wrote: > >> This patch adds the application configuration option documentation > >> generated > >> from specification items: > >> > >> http

[PATCH v2] eng: Add application config options how-to

Update #3715. --- eng/req/howto.rst | 119 ++ 1 file changed, 119 insertions(+) diff --git a/eng/req/howto.rst b/eng/req/howto.rst index 9a28427..c84003c 100644 --- a/eng/req/howto.rst +++ b/eng/req/howto.rst @@ -34,6 +34,125 @@ environment in your shel

Re: [PATCH 1/2] eng: Add application config options how-to

Hello Gedare, thanks for the review. I tried to fix most of the issues in v2. On 06/08/2020 18:57, Gedare Bloom wrote: +Generate Content after Changes +^^ + +Once you are done with the modifications of an existing item or the creation of The rest of this document is

Re: [PATCH 1/2] eng: Add application config options how-to

On Thu, Aug 6, 2020 at 12:24 PM Sebastian Huber wrote: > > Hello Gedare, > > thanks for the review. I tried to fix most of the issues in v2. > > On 06/08/2020 18:57, Gedare Bloom wrote: > >> +Generate Content after Changes > >> +^^ > >> + > >> +Once you are done with th

[PATCH] Doxyfile: Change version to 6.0.0

Update #4020. --- Doxyfile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Doxyfile b/Doxyfile index 9a8a6376fa..c794938191 100644 --- a/Doxyfile +++ b/Doxyfile @@ -38,7 +38,7 @@ PROJECT_NAME = RTEMS # could be handy for archiving the generated documentation or if so

[PATCH] eng: Add Doxyfile update to release process

--- eng/release-process.rst | 2 ++ 1 file changed, 2 insertions(+) diff --git a/eng/release-process.rst b/eng/release-process.rst index 8399a9e..c1ee7be 100644 --- a/eng/release-process.rst +++ b/eng/release-process.rst @@ -322,6 +322,8 @@ the needed changes. * :file:`cpukit/aclocal/versi

Pale color for definition terms at docs.rtems.org

Hello, after the Sphinx update I think the color of the definition terms is quite pale: https://docs.rtems.org/branches/master/c-user/event_manager.html#directives Removing the "dt" stuff from my-style.css seems to fix the problem. However, I have absolutely no idea what I changed and what t

Re: Pale color for definition terms at docs.rtems.org

On 7/8/20 3:50 pm, Sebastian Huber wrote: > Hello, > > after the Sphinx update I think the color of the definition terms is quite > pale: > > https://docs.rtems.org/branches/master/c-user/event_manager.html#directives > > Removing the "dt" stuff from my-style.css seems to fix the problem. Howev

Re: Pale color for definition terms at docs.rtems.org

On 07/08/2020 08:20, Chris Johns wrote: --8<--- -    color: #; --8<--- Please remove only this line and lets see what happens. This change seems to fix the issue: diff --git a/common/_static/my-styles.css b/common/_static/my-styles.css index bc67c33..5b6a9d5 100644 --- a/common/_s

Re: Pale color for definition terms at docs.rtems.org

On 7/8/20 4:38 pm, Sebastian Huber wrote: > On 07/08/2020 08:20, Chris Johns wrote: > >> --8<--- >> >>> -    color: #; >> --8<--- >> >> Please remove only this line and lets see what happens. > > This change seems to fix the issue: Could you please push this? Thanks Chris > > diff --g