[PATCH] Avoid StopIteration exception for non-rtems .pc

_arch_from_arch_bsp() and _bsp_from_arch_bsp() has overly optimistic assumptions that the argument must contain a '-'-separated field which starts with "rtems". These functions are intended to find the target triplet or the bsp parts of strings like "sparc-gaisler-rtems5-leon3" and

[PATCHv2 rtems_waf] Allow vendor field in toolchain target triplet

Rework the splitting of arch and bsp to rely on the last field in the arch section starting with "rtems", instead of relying on the arch being exactly two fields in size. This makes sure that toolchains with a vendor field in their target triplet can be used with this build system. Toolchains

[PATCH rtems_waf] Allow vendor field in toolchain target triplet

Rework the splitting of arch and bsp to rely on the last field in the arch section starting with "rtems", instead of relying on the arch being exactly two fields in size. This makes sure that toolchains with a vendor field in their target triplet can be used with this build system. Toolchains

[PATCH rtems-docs 2/2] c-user/message/directives.rst: Regen from spec

Regenerate message queue directives from the rtems-central spec in order to include the detailed note about non-atomicity of broadcast. This file is selectively added, other changes in generated files are omitted. Update #4804. ---  c-user/message/directives.rst | 8  1 file changed, 8

[PATCH rtems-docs 1/2] c-user/message/operations.rst: Don't claim atomic

rtems_message_queue_broadcast() is not atomic, since it unblocks each task after copying the message into their message buffer. So remove the wording indicating that it is atomic. Also reword the overall description slightly with "each" instead of "every", and add "until no more tasks remain", in

[PATCH rtems-central 2/2] spec: Add msg broadcast non-atomicity note to doc

rtems_message_queue_broadcast() may, under certain circumstances, copy the message to tasks which were not waiting on the message queue when the broadcast started, and may copy the message multiple times to the same task. This behaviour is, based on discussion in #4804, something that might be

[PATCH rtems-central 1/2] spec: Fix none-atomic -> non-atomic typo

---  spec/rtems/message/req/broadcast.yml | 2 +-  1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spec/rtems/message/req/broadcast.yml b/spec/rtems/message/req/broadcast.yml index b0e1af12..4b2d0f41 100644 --- a/spec/rtems/message/req/broadcast.yml +++

[PATCH] score: Fix minor Rhe->The typo in doxygen

--- Intentionally not part of commit message: Another minor typo in documentation, discovered by chance while browsing the doxygen site. cpukit/include/rtems/score/coremsgimpl.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cpukit/include/rtems/score/coremsgimpl.h

[PATCH rtems-docs] c-user/message/directives.rst: byes->bytes typo

--- c-user/message/directives.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/c-user/message/directives.rst b/c-user/message/directives.rst index 9cb88e2..a13e4c7 100644 --- a/c-user/message/directives.rst +++ b/c-user/message/directives.rst @@ -727,7 +727,7 @@ Broadcasts

Re: [PATCH v2] tests/validation: Fix 64bit test failure

interface just to allow this failure to occur. Would it be possible to instead specify that if SIZE_MAX >= UINT32_MAX * (1 + buffer overhead) then this case should be skipped, or expects success? -- Martin Erik Werner Software Developer | AAC Clyde Space aac-cl

RTEMS Documentation BSD licensing

d to copy documentation to BSD-doxygen. -- Martin Erik Werner ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

RTEMS Documentation BSD (re)licensing statement for my contributions

(By request. Also added to https://devel.rtems.org/ticket/3899) All previous contributions to the RTEMS documentation authored by me (Martin Erik Werner) are, unless otherwise specified, licensed under the terms of either the Creative Commons Attribution Share Alike 4.0 International license

[PATCH] c-user: Remove spurious "is undefined. "

Remove a spurious "is undefined. " fragment which was likely a leftover from sentence re-use. --- c-user/self_contained_objects.rst | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/c-user/self_contained_objects.rst b/c-user/self_contained_objects.rst index 1c1e664..0be1423

[PATCH] c-user: Add & update ratemon get return values

Add a description of the previously missing RTEMS_NOT_DEFINED return value for rtems_rate_monotonic_get_status(). Update the RTEMS_SUCCESSFUL return value descriptions for rtems_rate_monotonic_get_status() and rtems_rate_monotonic_get_statistics() which incorrectly used the same description as

[PATCH] Fix a minor "suspect" -> "subject" wording error

--- The word "suspect" here looked like a mistake and I have changed it based on this assumption. If it is not a mistake, what does "suspect" mean in this context? c-user/self_contained_objects.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] Use EAGAIN for POSIX mq wait in ISR error

Modify the status code returned by _CORE_message_queue_Submit() when it detects a wait bout to happen in an ISR (which would be deadly) to return a status which translated to EAGAIN instead of ENOMEM. (This is only relevant for POSIX message queues, since classic message queues cannot block on

[PATCH] Remove invalid unsatisfied retval from msg submit

The return value RTEMS_UNSATISFIED cannot be returned by message queue send/urgent in the classical API, so remove this from the documentation. Based on the discussion in: https://lists.rtems.org/pipermail/devel/2020-January/056891.html Message-Id: --- c-user/message_manager.rst | 4 1

"too many" vs "unsatisfied" status from msg send

ced that if RTEMS_SCORE_COREMSG_ENABLE_BLOCKING_SEND is set, the _CORE_message_queue_Submit() function can return STATUS_MESSAGE_QUEUE_WAIT_IN_ISR which translates to RTEMS_INTERNAL_ERROR, is this status deliberately omitted from the documentation for rtems_message_queue_{send,urgent}? -- Martin Erik Wer

Re: [PATCH 1/2] barrier: Remove leftover semaphore remnants

On Wed, 2019-10-02 at 17:00 -0500, Joel Sherrill wrote: > > > On Wed, Oct 2, 2019 at 2:52 PM Martin Erik Werner < > martinerikwer...@gmail.com> wrote: (...) > > On Tue, 2019-10-01 at 18:02 -0500, Joel Sherrill wrote: > > > > > > > > > O

Re: [PATCH 1/2] barrier: Remove leftover semaphore remnants

at 3:53 PM Gedare Bloom > > wrote: > > > > > > On Wed, Sep 4, 2019 at 3:36 PM Martin Erik Werner > > > wrote: > > > > > > > > Remove various incorrect references to "lock" and "obtain" and > > to an > > > >

[Resend] [PATCH 0/2] rtems-doc barrier fixes

Hi, I'm re-sending this patch set since I received no reply previously (2019-09-04). Martin Erik Werner (2): barrier: Remove leftover semaphore remnants barrier: Remove unfinished sentence c-user/barrier_manager.rst | 45 ++--- 1 file changed, 10

[PATCH 2/2] barrier: Remove unfinished sentence

Remove the unfinished sentence "Since a barrier is, by definition, never immediately [...]" and jump directly to "The task may wait [forever or for a timeout]" instead. I cannot figure out what the unfinished sentence is supposed to be - "released"? "passed"? --- c-user/barrier_manager.rst | 7

[PATCH 1/2] barrier: Remove leftover semaphore remnants

Remove various incorrect references to "lock" and "obtain" and to an option set which is not part of the barrier interface. It looks like the barrier documentation was started based on a copy of the semaphore documentation and these things are surviving remnants. Also remove an unfinished

[PATCH 2/2] barrier: Remove unfinished sentence

Remove the unfinished sentence "Since a barrier is, by definition, never immediately [...]" and jump directly to "The task may wait [forever or for a timeout]" instead. I cannot figure out what the unfinished sentence is supposed to be - "released"? "passed"? --- c-user/barrier_manager.rst | 7

[PATCH 1/2] barrier: Remove leftover semaphore remnants

Remove various incorrect references to "lock" and "obtain" and to an option set which is not part of the barrier interface. It looks like the barrier documentation was started based on a copy of the semaphore documentation and these things are surviving remnants. Also remove an unfinished

Re: [PATCH] Address several issues from compiling examples

On Tue, 2019-09-03 at 01:48 +0200, Martin Erik Werner wrote: > Compiling the code from examples "code-block:: c" along with public > includes and a bsp exposed a few issues amongst a lot of false > positives. Address some of these: (...) As per the sent patch, I've had some

[PATCH] Address several issues from compiling examples

Compiling the code from examples "code-block:: c" along with public includes and a bsp exposed a few issues amongst a lot of false positives. Address some of these: * Terminate struct declarations with ';'. Mainly for pedantic correctness. * Show ptrdiff_t instead of size_t for the sbrk()

Re: [PATCH 2/6] or1k/shared/cache/cache.c: Remove unused methods

On Mon, 2018-10-08 at 17:33 -0500, Joel Sherrill wrote: > > > On Mon, Oct 8, 2018 at 9:37 AM Martin Erik Werner > wrote: > > On Mon, 2018-10-08 at 15:28 +0200, Sebastian Huber wrote: > > > Are the intentionally unused or is there some bug and the generic cache >

Re: [PATCH 2/6] or1k/shared/cache/cache.c: Remove unused methods

re, so it might be a special case? -- Martin Erik Werner ÅAC Microtec AB | Clyde Space Ltd. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: Future of or1k RTEMS support?

, there are still ongoing work on this for or1k at https://github.com/stffrdhrn/gcc . [0] http://aacmicrotec.com/products/spacecraft-subsystems/avionics/siriusobc/ http://aacmicrotec.com/products/spacecraft-subsystems/avionics/siriustcm/ -- Martin Erik Werner ÅAC Microtec AB | Clyde Space Ltd. On Thu, 2018

Re: [PATCH 0/1] posixtimer01 test questions and patch

.) -- Martin Erik Werner <martinerikwerner@gmail.com> ÅAC Microtec AB | Clyde Space Ltd. On Tue, 2018-05-15 at 11:21 +0200, Martin Erik Werner wrote: > When running the testsuites/psxtests/psxtimer01/ tests on our or1k > board, I've noticed a common 10ms (one clock tick) time difference when

[PATCH 0/1] posixtimer01 test questions and patch

avoid using unset errno, and to provide information about the time difference, which might be interesting, if these checks are still valid as certain failures: Martin Erik Werner (1): Fix and extend error message in posix timer test testsuites/psxtests/psxtimer01/psxtimer.c | 14 +++

[PATCH 1/1] Fix and extend error message in posix timer test

was measured. Signed-off-by: Martin Erik Werner <martin.wer...@aacmicrotec.com> --- testsuites/psxtests/psxtimer01/psxtimer.c | 14 -- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/testsuites/psxtests/psxtimer01/psxtimer.c b/testsuites/psxtests/psxtimer01/psxtimer.c

[PATCH] rtems/inttypes: Clarify hexadecimal in comments

Update comments to reflect that PRIxblksize_t PRIxblkcnt_t is hexadecimal, not decimal. Signed-off-by: Martin Erik Werner <martin.wer...@aacmicrotec.com> --- cpukit/include/rtems/inttypes.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/cpukit/include/rtems/inttyp

[PATCH] Fix comments for object lookup err. -> status map

; update the comments regarding the object lookup error to status map to match. Signed-off-by: Martin Erik Werner <martin.wer...@aacmicrotec.com> --- cpukit/rtems/src/status.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/cpukit/rtems/src/status.c b/cpukit/rtems/src/st

[PATCH] bsp-howto/console: Move misplaced var. in example

Signed-off-by: Martin Erik Werner <martinerikwer...@gmail.com> --- bsp-howto/console.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bsp-howto/console.rst b/bsp-howto/console.rst index 2bdb3c8..f8ff7ce 100644 --- a/bsp-howto/console.rst +++ b/bsp-howto/conso

[PATCH] Fix bashism in vc-key.sh

Change "==" to "=", since "==" for comparison is not available in POSIX sh. Signed-off-by: Martin Erik Werner <martinerikwer...@gmail.com> --- cpukit/sapi/vc-key.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/cpukit/sapi/vc-

[PATCH 3/3] rtems: Provide nonzero argc required by gtest init

Signed-off-by: Martin Erik Werner <martin.wer...@aacmicrotec.com> --- rtems/gtest-main.h | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/rtems/gtest-main.h b/rtems/gtest-main.h index 81ec91e..797d12e 100644 --- a/rtems/gtest-main.h +++ b/rtems/gtest-main.h @@ -39,8

[PATCH 2/3] rtems: Make prefix configurable

If the toolchain has been relocated, the configured-with-prefix will not match the desired install path. Hence enable setting prefix manually in the install-target.sh script. Signed-off-by: Martin Erik Werner <martin.wer...@aacmicrotec.com> --- rtems/install-target.s

[PATCH 1/3] rtems: Handle multi-level multilib directories

Sometimes, multilib directories have multiple levels, for example no-delay/soft-float, make sure to handle this by creating directories before installing. Signed-off-by: Martin Erik Werner <martin.wer...@aacmicrotec.com> --- rtems/Makefile | 1 + 1 file changed, 1 insertion(+) diff

[PATCH 0/3] Some fixes for Google Test on RTEMS

Based on some experimentation with Google Test on RTEMS, here are some patches that fell out of that process, which might be interesting? Martin Erik Werner (3): rtems: Handle multi-level multilib directories rtems: Make prefix configurable rtems: Provide nonzero argc required by gtest init

Re: [PATCH 0/5] or1k: Optimisation and implementation of cache manager functions

ermail/devel/2016-February/013637.html), of which the cache changes are only a subset. I'm thinking we'll hold off requesting backports until we've managed to clean up and submit the majority of those to master. -- Martin Erik Werner <martin.wer...@aacmicrotec.com> ÅAC

[PATCH 1/5] or1k: Add functions for entire cache operations

Add functions for flushing and invalidating whole cache. Since we don't have system calls that can operate on anything more than a single cache line, these simply retrieves the cache size and iterates over the full size, invalidating each line. The current implementation assumes that there's

[PATCH 0/5] or1k: Optimisation and implementation of cache manager functions

commit 5807328. No testing except compilation has been performed on the rebased patch set on master. Martin Erik Werner (5): or1k: Add functions for entire cache operations or1k: Indent & comment fix in cache.c or1k: Avoid excessive ISR toggle in cache manager or1k: Remove secon

[PATCH 3/5] or1k: Avoid excessive ISR toggle in cache manager

Previously _ISR_Local_{disable,enable}() was executed twice for each cache line operation, and since operations over the entire cache were implemented by calling the single-line operations in a loop, this made those operations rather costly. Fix the double-toggle by calling _OR1K_mtspr()

[PATCH 5/5] or1k: Avoid multiple iterations over cache

Previously, if the cache range operations were called with a range that was larger than the cache size, this would lead to multiple iterations over the cache, which is unnecessary. Limit this so that if the range is larger than the cache size, the operations will only iterate over the whole cache

[PATCH 4/5] or1k: Remove secondary functions in cache manager

Move the code of the _CPU_OR1K_Cache_{enable,disable}_* functions into the equivalent exported _CPU_cache_{enable,disable}_* functions instead, and then delete them, in order to reduce the code indirection and aid readability. This does not touch the currently unused prefetch, writeback, and lock

[PATCH 1/2] Add option to limit bootstrap to a single arch

Using the -o|--only option, it is now possible to limit the bootstrapping operation of arch-specific libbsp, libcpu and cpukit paths to a single arch, for example: $ bootstrap -p -o or1k and $ bootstrap -o or1k This is a somewhat ugly implementation, but may be sufficient for the intended