[PATCH 1/3] rtemstoolkit: Fix macro's use of 'is'

From: Chris Johns Updates #4111 --- rtemstoolkit/macros.py | 90 +- 1 file changed, 45 insertions(+), 45 deletions(-) diff --git a/rtemstoolkit/macros.py b/rtemstoolkit/macros.py index 4eb8829..be983f1 100644 --- a/rtemstoolkit/macros.py +++ b/rtemstoolki

[PATCH 3/3] rtemstoolkit/linux: Fix the host support

From: Chris Johns Updates #4111 --- rtemstoolkit/linux.py | 20 1 file changed, 4 insertions(+), 16 deletions(-) diff --git a/rtemstoolkit/linux.py b/rtemstoolkit/linux.py index 15c6132..1ce6739 100644 --- a/rtemstoolkit/linux.py +++ b/rtemstoolkit/linux.py @@ -33,6 +33,7 @

[PATCH] bsps/arm: Workaround for Errata 845369

Add a workaround for Cortex-A9 Errata 845369: Under Very Rare Timing Circumstances Transition into Streaming Mode Might Create Data Corruption 845369: Under Very Rare Timing Circumstances Transition into Streaming Mode Might Create Data Corruption. Close #4115. --- bsps/arm/include/bsp/arm-a9mpco

Re: [PATCH 0/1] c-user: Generate I/O Manager documentation

On 29/09/2020 16:59, Sebastian Huber wrote: This is the first generated documentation of a manager. For the PDF output please have a look at: https://ftp.rtems.org/pub/rtems/people/sebh/c-user.pdf Please review the layout. I changed the layout to use definition lists instead of tables. The b

Re: waf bsp_defaults sometimes includes multiple BSPs

On Fri, Oct 2, 2020 at 12:57 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 01/10/2020 23:38, Joel Sherrill wrote: > > > I am generating a uniquely named ini file per BSP. In doing an ls -l, > > I noticed the size varied by at least a factor of three. This is > > because when

Re: waf bsp_defaults sometimes includes multiple BSPs

On 02/10/2020 16:26, Joel Sherrill wrote: Maybe we should change it to: def is_in_white_list(variant, white_list): if not white_list: return True for pattern in white_list: if re.match(pattern + "$", variant): return True

Approachability of Documentation Generation

Hi The other thread has a mix of detailed "review this" versus philosophy on how to make the documentation generation process approachable so Sebastian isn't the only human capable of maintaining it. I want to talk at a high level about making the process approachable. The major factor in the push

white space in build path?

Can we make spaces in paths work, or be checked/rejected, in the waf build without too much trouble? https://devel.rtems.org/ticket/3450 If so, we may want to move this ticket and set as something to do. If not, I would close this as wontfix. ___ devel

Re: white space in build path?

On Fri, Oct 2, 2020 at 11:43 AM Gedare Bloom wrote: > Can we make spaces in paths work, or be checked/rejected, in the waf > build without too much trouble? > I'd be prone to make it an error and not worry about it deeper in the code. It would have to be properly quoted everywhere which might be

Re: Approachability of Documentation Generation

On Fri, Oct 2, 2020 at 8:57 AM Joel Sherrill wrote: > > Hi > > The other thread has a mix of detailed "review this" versus philosophy on how > to make the documentation generation process approachable so Sebastian isn't > the only human capable of maintaining it. I want to talk at a high level

Interest in Virtual RTEMS Workshop

Hi In the past, we have internally discussed an RTEMS Workshop but always got hung up on the basic logistics. There had to be a host site which usually means cost. Although OAR now has access to a facility that could host about 40-50. Travel required to all be in a central location would be burden

[PATCH v4] cpukit/librcxx: Add a C++ thread interface with attributes

From: Chris Johns --- cpukit/include/rtems/c++/error| 65 +++ cpukit/include/rtems/c++/thread | 469 ++ cpukit/librtemscxx/error.cc | 76 cpukit/librtemscxx/thread.cc | 416 +++ spec/build/cpukit/grp.yml

Re: waf default number of jobs

On 2/10/20 5:53 am, Joel Sherrill wrote: > On Thu, Oct 1, 2020 at 2:39 PM Sebastian Huber > > > wrote: > > On 01/10/2020 20:09, Joel Sherrill wrote: > > > What was the rationale behind the choice of the default for the number > > of jobs for