[PATCH] Patch attempt two to avoid nameclash of PAGESIZE define

This commit excludes the PAGESIZE legacy define because there is a nameclash with a define of the same name coming from the RTEMS header limits.h. --- .../stm32h7/include/Legacy/stm32_hal_legacy.h | 172 +- 1 file changed, 88 insertions(+), 84 deletions(-) diff --git a/bsps/arm/st

Re: [PATCH] Patch attempt two to avoid nameclash of PAGESIZE define

I just resent the patch and I hope this can be applied properly. Like already mentioned, when loading this file in Ubuntu 20.04, something was done to the line endings automatically.. But maybe this is the reason the patch could not be applied before, because I had the same issue of not being able

Re: [PATCH] Updated tick implementation for HAL_GetTick

Okay, good to know. Do you think it's okay if my simpler implementation is used completely? Another option would be to use the simple function for the oscillator init functions (sth like a private HAL_GetTick_OscInit function). But maybe you have a better idea. Kind Regards Robin On Tue, 20 Apr

Re: [PATCH] STM32H743ZI Nucleo and basic lwIP support

I'm sorry I have to dig this up and bother you again but it's something that i spotted when browsing the STM CubeH7 code and which is a similar problem to the UART3 issue and might affect NUCLEO users who would like to use libbsd networking. Similarly to the UART3, the pins for the ETH initializati

Re: [PATCH] STM32H743ZI Nucleo and basic lwIP support

Actually, the configurations for GPIOA and GPIOC are completely overlapping and could be reused to the NUCLEO BSP. Kind Regards Robin On Wed, 21 Apr 2021 at 11:23, Robin Müller wrote: > I'm sorry I have to dig this up and bother you again but it's something > that i spotted when browsing the ST

Re: Write the BSP for ARM Versatile Express device

Hi Gedare, For the last few days, I am reading the rtems source code, trying to understand the build system, how a bsp is built. I just has a few questions: - it seems like the configure.ac and Makefile.am for each BSP (c/src/lib/libbsp/) is separate from the BSP source code (bsps/). However not a

Re: Write the BSP for ARM Versatile Express device

On Wed, Apr 21, 2021, 5:32 AM Đức Anh wrote: > Hi Gedare, > > For the last few days, I am reading the rtems source code, trying to > understand the build system, how a bsp is built. I just has a few questions: > - it seems like the configure.ac and Makefile.am for each BSP > (c/src/lib/libbsp/) i

[PATCH] rtems: Generate

Change license to BSD-2-Clause according to file histories and documentation re-licensing agreement. Update #3899. Update #3993. --- cpukit/include/rtems/rtems/support.h | 404 +-- 1 file changed, 320 insertions(+), 84 deletions(-) diff --git a/cpukit/include/rtems/rtems/

[PATCH 0/8] Generate documentation for managers

This patch adds the next round of generated documentation. The first free patches just split up the existing documentation into multiple files so that parts of it can be generated. The fourth patch adds new glossar terms. The other patches add the generated documentation for the Initialization,

[PATCH 1/8] c-user: Split up initialization manager

This makes it easier to automatically generate parts of the module documentation in the future. Update #3993. --- c-user/index.rst | 2 +- c-user/initialization/background.rst | 48 + c-user/initialization/directives.rst | 41 c-use

[PATCH 4/8] c-user: Add user extensions glossary terms

--- c-user/glossary.rst | 40 +-- c-user/user-extensions/background.rst | 13 +++-- 2 files changed, 42 insertions(+), 11 deletions(-) diff --git a/c-user/glossary.rst b/c-user/glossary.rst index 71a0242..dc765ec 100644 --- a/c-user/glossary.rst +++ b

[PATCH 3/8] c-user: Split up multiprocessing manager

This makes it easier to automatically generate parts of the module documentation in the future. Update #3993. --- c-user/index.rst | 2 +- .../background.rst} | 89 --- c-user/multiprocessing/directives.rst | 44 +

[PATCH 5/8] c-user: Generate initialization manager docs

The documentation is a consolidation of the comments in Doxygen markup and the documentation sources in Sphinx markup. The documentation was transfered to interface specification items. The documentation source files were generated from the items by a script. Update #3993. --- c-user/initializa

[PATCH 7/8] c-user: Generate multiprocessing manager docs

The documentation is a consolidation of the comments in Doxygen markup and the documentation sources in Sphinx markup. The documentation was transfered to interface specification items. The documentation source files were generated from the items by a script. Update #3993. --- c-user/multiproce

[PATCH 2/8] c-user: Split up fatal error manager

This makes it easier to automatically generate parts of the module documentation in the future. Update #3993. --- .../background.rst} | 300 -- c-user/fatal-error/directives.rst | 226 + c-user/fatal-error/index.rst

[PATCH 6/8] c-user: Generate fatal error manager docs

The documentation is a consolidation of the comments in Doxygen markup and the documentation sources in Sphinx markup. The documentation was transfered to interface specification items. The documentation source files were generated from the items by a script. Update #3993. --- c-user/fatal-erro

[PATCH 8/8] c-user: Generate dual-ported memory manager docs

The documentation is a consolidation of the comments in Doxygen markup and the documentation sources in Sphinx markup. The documentation was transfered to interface specification items. The documentation source files were generated from the items by a script. Update #3993. --- c-user/dual-porte

Re: [PATCH] rtems: Generate

On Wed, Apr 21, 2021 at 7:46 AM Sebastian Huber wrote: > > Change license to BSD-2-Clause according to file histories and > documentation re-licensing agreement. > > Update #3899. > Update #3993. > --- > cpukit/include/rtems/rtems/support.h | 404 +-- > 1 file changed, 320

Re: [PATCH] rtems: Generate

On 21/04/2021 16:19, Gedare Bloom wrote: +/* Generated from spec:/rtems/support/if/group */ + /** - * @addtogroup ClassicTasks + * @defgroup RTEMSAPIClassicSupport Support Services + * + * @ingroup RTEMSAPIClassic + * + * @brief Items of this group should move to other groups. I don't underst

Re: [PATCH 4/8] c-user: Add user extensions glossary terms

On Wed, Apr 21, 2021 at 7:50 AM Sebastian Huber wrote: > > --- > c-user/glossary.rst | 40 +-- > c-user/user-extensions/background.rst | 13 +++-- > 2 files changed, 42 insertions(+), 11 deletions(-) > > diff --git a/c-user/glossary.rst b/c-user/gloss

Re: [PATCH 8/8] c-user: Generate dual-ported memory manager docs

On Wed, Apr 21, 2021 at 7:50 AM Sebastian Huber wrote: > > The documentation is a consolidation of the comments in Doxygen markup > and the documentation sources in Sphinx markup. The documentation was > transfered to interface specification items. The documentation source > files were generated

Re: [PATCH 8/8] c-user: Generate dual-ported memory manager docs

On 21/04/2021 17:28, Gedare Bloom wrote: +:c:macro:`RTEMS_INVALID_ADDRESS` +The ``length`` parameter was `NULL id? everything else looks ok Thanks a lot for the quick review. -- embedded brains GmbH Herr Sebastian HUBER Dornierstr. 4 82178 Puchheim Germany email: sebastian.hu...@embedded

Re: [PATCH] Updated tick implementation for HAL_GetTick

On 21/04/2021 11:00, Robin Müller wrote: Okay, good to know. Do you think it's okay if my simpler implementation is used completely? Another option would be to use the simple function for the oscillator init functions (sth like a private HAL_GetTick_OscInit function). But maybe you have a bett

Re: [PATCH] Updated tick implementation for HAL_GetTick

On 21/04/2021 19:30, Sebastian Huber wrote: On 21/04/2021 11:00, Robin Müller wrote: Okay, good to know. Do you think it's okay if my simpler implementation is used completely? Another option would be to use the simple function for the oscillator init functions (sth like a private HAL_GetTick

[PATCH] psx13: Reworked and relicensed

Changed the way the tests were structured, added rtems_test_assert()'s, updated psx13.scn and the license. --- testsuites/psxtests/psx13/psx13.scn | 24 +- testsuites/psxtests/psx13/test.c| 879 +--- 2 files changed, 335 insertions(+), 568 deletions(-) diff --

[PATCH] sb: Merge mailer changes from rtems-tools

This adds the improved mailer.py script from rtems-tools. Closes #4388 --- source-builder/sb/mailer.py | 192 ++-- source-builder/sb/options.py| 9 ++ source-builder/sb/setbuilder.py | 2 + 3 files changed, 171 insertions(+), 32 deletions(-) diff --git a/s

Re: [PATCH] sb: Merge mailer changes from rtems-tools

Hi Alex, Is there a chance the password can end up in a log file? See... https://git.rtems.org/rtems-source-builder/tree/source-builder/sb/options.py#n584 Chris On 22/4/21 8:00 am, Alex White wrote: > This adds the improved mailer.py script from rtems-tools. > > Closes #4388 > --- > source-bu

Re: [PATCH] sb: Merge mailer changes from rtems-tools

On Wed, Apr 21, 2021 at 5:06 PM Chris Johns wrote: > > Hi Alex, > > Is there a chance the password can end up in a log file? I did not see the command line options in the email when I sent it to myself so it wasn't on my radar, but it could have ended up in a log file, yes. I should do the sam

Re: [PATCH] sb: Merge mailer changes from rtems-tools

On 22/4/21 11:48 am, Alex White wrote: > > On Wed, Apr 21, 2021 at 5:06 PM Chris Johns wrote: >> >> Hi Alex, >> >> Is there a chance the password can end up in a log file? > > I did not see the command line options in the email when I sent it to myself > so > it wasn't on my radar, but it could

Re: [PATCH RTEMS v2 0/1] bsp/beagle: Refactored i2c driver and Updated

Hello Christian, Reminder to push the patches. Thanks, Niteesh On Sun, Apr 18, 2021 at 11:57 PM Christian Mauderer wrote: > Hello Niteesh, > > looks good to me. I'll wait two or three days before pushing so that > others can review the libbsd patch too. Please ping me on Wednesday if I > didn'