[PATCH 1/2] c-user: Avoid Sphinx-specifics in appl config

This helps to generate Doxygen markup from the application configuration option specification items. Update #3994. --- c-user/config/bsp-related.rst | 8 ++-- c-user/config/classic-api.rst | 63 - c-user/config/classic-init-task.rst | 2 +- c-user/config/

[PATCH 2/2] c-user: Canonicalize document internal references

This helps to generate Doxygen markup from the application configuration option specification items. Update #3994. --- c-user/config/classic-api.rst | 7 +-- c-user/config/general.rst | 6 +- c-user/config/posix-api.rst | 11 ++-- c-user/config/scheduler-general.rst | 87

[PATCH 0/1] Generate application configuration option documentation

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

[PATCH 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 | 4125

[PATCH] sptests/sp21: Fix deprecated warning

--- testsuites/sptests/sp21/init.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/testsuites/sptests/sp21/init.c b/testsuites/sptests/sp21/init.c index f44f2ba851..71abe467a9 100644 --- a/testsuites/sptests/sp21/init.c +++ b/testsuites/sptests/sp21/init.c @@ -7,6 +7,8 @@ * http://www.rte

Re: RTEMS 6 and GCC 10 Status

On 05/07/2020 19:13, Joel Sherrill wrote: Good job! Should these be the first entries in the RTEMS 6 release description? I added: https://github.com/RTEMS/rtems-release/blob/master/rtems-notes-6.txt Should we rename this file to rtems-notes-6.md? I added also a migration from v5 to v6 sect

[PATCH] user: Add v5 to v6 migration help

--- user/migration/index.rst| 1 + user/migration/v5-to-v6.rst | 20 2 files changed, 21 insertions(+) create mode 100644 user/migration/v5-to-v6.rst diff --git a/user/migration/index.rst b/user/migration/index.rst index 76012b5..06af484 100644 --- a/user/migration/inde

Re: RTEMS 6 and GCC 10 Status

On Tue, Jul 7, 2020 at 8:03 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 05/07/2020 19:13, Joel Sherrill wrote: > > Good job! > > > > Should these be the first entries in the RTEMS 6 release description? > > I added: > > https://github.com/RTEMS/rtems-release/blob/master/rt

libbsd rtems 5 branches

Hi What's the difference between these two branches? remotes/origin/5 remotes/origin/5-freebsd-12 --joel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: libbsd rtems 5 branches

On 07/07/2020 15:19, Joel Sherrill wrote: Hi What's the difference between these two branches?   remotes/origin/5 This branch synchronizes with the FreeBSD master.   remotes/origin/5-freebsd-12 This branch synchronizes with the FreeBSD 12 branch. Both are for RTEMS 5. -- Sebastian Hu

Re: [GSoC 2020: Daily Update]: Building EPICS with RTEMS5

On Tue, Jul 7, 2020 at 5:33 AM Gedare Bloom wrote: > On Mon, Jul 6, 2020 at 5:49 PM Joel Sherrill wrote: > > > > > > > > On Mon, Jul 6, 2020, 6:14 PM Gedare Bloom wrote: > >> > >> On Mon, Jul 6, 2020 at 10:12 AM Mritunjay Sharma > >> wrote: > >> > > >> > Hello everyone, > >> > > >> > Thank you

Re: [GSoC 2020: Daily Update]: Building EPICS with RTEMS5

[UPDATE]: I tried building EPICS with RTEMS5 for pc-386 and pc-386-qemu. Everything worked fine while building the pc-386 with RTEMS5. After this when I entered epics-base and made the following change: epics-base/os/CONFIG_SITE.Common.RTEMS RTEMS_VERSION = 5 RTEMS_BASE = /home/mritunjay/develop

Re: [GSoC 2020: Daily Update]: Building EPICS with RTEMS5

I’m away from my keyboard. If you use the epics Adaption to rtems from my github “playground?” and bsp’s with —enable-networks should compile. Heinz FHI, Heinz Junkes > On 7. Jul 2020, at 18:14, Mritunjay Sharma > wrote: > >  > [UPDATE]: I tried building EPICS with RTEMS5 for pc-386 and pc-

Re: [GSoC 2020: Daily Update]: Building EPICS with RTEMS5

From: Heinz Junkes Sent: Wednesday, July 8, 2020 1:05 AM To: Mritunjay Sharma Cc: Gedare Bloom; Joel Sherrill; Chris Johns; RTEMS Devel Subject: Re: [GSoC 2020: Daily Update]: Building EPICS with RTEMS5 I’m away from my keyboard. If you use the epics Adaption to

Re: RTEMS 6 and GCC 10 Status

On 7/7/20 11:03 pm, Sebastian Huber wrote: > On 05/07/2020 19:13, Joel Sherrill wrote: >> Should these be the first entries in the RTEMS 6 release description? > > I added: > > https://github.com/RTEMS/rtems-release/blob/master/rtems-notes-6.txt Thank you. > Should we rename this file to rtems-

Re: [PATCH] common: Remove probably superfluous import

On 7/7/20 3:29 pm, Sebastian Huber wrote: > The purpose of this import is unclear. > > This import caused the following error with Sphinx 3.0: > > Extension error: > Could not import extension rtemsdomain (exception: cannot import name 'l_') > --- > common/rtemsdomain.py | 1 - > 1 file changed,

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

Hi Sebastian, Thank you for this patch. I am sorry but I would like to see this central repo issue resolved before any generated files are added to any of the project's repos. I understand to some level the path you are taking and moving along but these generated files are coming from a personal

Re: [PATCH 1/2] c-user: Avoid Sphinx-specifics in appl config

On 7/7/20 9:06 pm, Sebastian Huber wrote: > This helps to generate Doxygen markup from the application configuration > option specification items. I do not understand this and the second part of this patch. I am suspicious this is introducing constraints on what we can use in the documentation. M

Re: [PATCH] common: Remove probably superfluous import

On 08/07/2020 03:11, Chris Johns wrote: On 7/7/20 3:29 pm, Sebastian Huber wrote: The purpose of this import is unclear. This import caused the following error with Sphinx 3.0: Extension error: Could not import extension rtemsdomain (exception: cannot import name 'l_') --- common/rtemsdomai

[PATCH] Use *.md extension for the release notes

--- rtems-notes-5.txt => rtems-notes-5.md | 0 rtems-notes-6.txt => rtems-notes-6.md | 0 rtems-release | 4 ++-- 3 files changed, 2 insertions(+), 2 deletions(-) rename rtems-notes-5.txt => rtems-notes-5.md (100%) rename rtems-notes-6.txt => rtems-notes-6.md (100%) diff

Re: [PATCH] common: Remove probably superfluous import

On 8/7/20 2:33 pm, Sebastian Huber wrote: > On 08/07/2020 03:11, Chris Johns wrote: > >> On 7/7/20 3:29 pm, Sebastian Huber wrote: >>> The purpose of this import is unclear. >>> >>> This import caused the following error with Sphinx 3.0: >>> >>> Extension error: >>> Could not import extension rtem

Re: [PATCH] Use *.md extension for the release notes

OK to push. On 8/7/20 2:37 pm, Sebastian Huber wrote: > --- > rtems-notes-5.txt => rtems-notes-5.md | 0 > rtems-notes-6.txt => rtems-notes-6.md | 0 > rtems-release | 4 ++-- > 3 files changed, 2 insertions(+), 2 deletions(-) > rename rtems-notes-5.txt => rtems-notes-5.m

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

Hello Chris, thanks for the detailed response. On 08/07/2020 03:55, Chris Johns wrote: Hi Sebastian, Thank you for this patch. I am sorry but I would like to see this central repo issue resolved before any generated files are added to any of the project's repos. I understand to some level th

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

[It seems Thunderbird misformatted the e-mail, maybe this one looks better.] Hello Chris, thanks for the detailed response. On 08/07/2020 03:55, Chris Johns wrote: Hi Sebastian, Thank you for this patch. I am sorry but I would like to see this central repo issue resolved before any generate

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

On 08/07/2020 07:35, Sebastian Huber wrote: It seems to me the key is the central repo and how it functions, how easy or hard it is to learn about it and how well it will work in practice. A key concern is taking it from a single person repo, ie you, to a project wide repo with concurrent up

Re: NEW BUILD SYSTEM: Cannot build rtems-libbsd

Hello, On Tue, Jul 7, 2020 at 10:42 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > Hello, > > the problem is that the new build system doesn't export optimization > flags such as -Wl,--gc-sections. The libbsd build should enable this > linker option unconditionally. > Thank you

Re: NEW BUILD SYSTEM: Cannot build rtems-libbsd

On 08/07/2020 08:10, Niteesh G. S. wrote: On Tue, Jul 7, 2020 at 10:42 AM Sebastian Huber > wrote: Hello, the problem is that the new build system doesn't export optimization flags such as -Wl,--gc-sections. The libbsd build should enable

Re: NEW BUILD SYSTEM: Cannot build rtems-libbsd

On 08/07/2020 08:13, Sebastian Huber wrote: > On 08/07/2020 08:10, Niteesh G. S. wrote: > >> On Tue, Jul 7, 2020 at 10:42 AM Sebastian Huber >> > > wrote: >> >>     Hello, >> >>     the problem is that the new build system doesn't export optimization >>  

Re: NEW BUILD SYSTEM: Cannot build rtems-libbsd

On Wed, Jul 8, 2020 at 11:52 AM Christian Mauderer < christian.maude...@embedded-brains.de> wrote: > On 08/07/2020 08:13, Sebastian Huber wrote: > > On 08/07/2020 08:10, Niteesh G. S. wrote: > > > >> On Tue, Jul 7, 2020 at 10:42 AM Sebastian Huber > >> >>

Re: NEW BUILD SYSTEM: Cannot build rtems-libbsd

On 08/07/2020 08:35, Niteesh G. S. wrote: > On Wed, Jul 8, 2020 at 11:52 AM Christian Mauderer > > wrote: > > On 08/07/2020 08:13, Sebastian Huber wrote: > > On 08/07/2020 08:10, Niteesh G. S. wrote: > > > >> On Tue, Jul 7, 2020 at 10:

RE: [PATCH v1 1/1] bsps/pc386: Fix IPI for non-consecutive APICIDs

Hello, Could someone please push this patch to the branches 5 and master? Or do I need a ticket for the 5 branch first? Cheers, Jan > -Original Message- > From: Sommer, Jan > Sent: Friday, July 3, 2020 2:32 PM > To: devel@rtems.org > Cc: Sommer, Jan > Subject: [PATCH v1 1/1] bsps/pc