Re: [PATCH] doxygen: Replace and move main page
Hello Joel, On 10.10.23 20:43, Joel Sherrill wrote: Sorry. Not sure how this kept slipping through the cracks. The 13 September ping did coincide with me being on a trip and then sick. This is the only revision I see in my inbox. There is an email which says "how about this version?" but I don't see anything on it. A few comments inline. I tried to address your remarks and checked it in. New features should be added to the user manual's feature list first. -- embedded brains GmbH Herr Sebastian HUBER Dornierstr. 4 82178 Puchheim Germany email: sebastian.hu...@embedded-brains.de phone: +49-89-18 94 741 - 16 fax: +49-89-18 94 741 - 08 Registergericht: Amtsgericht München Registernummer: HRB 157899 Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler Unsere Datenschutzerklärung finden Sie hier: https://embedded-brains.de/datenschutzerklaerung/ ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
[PATCH] validation: Add wrapped bsp_interrupt_dispatch for MicroBlaze
This adds a MicroBlaze-specific bsp_interrupt_dispatch wrapper which
fixes a linker error.
---
testsuites/validation/tc-score-isr.c | 17 +
1 file changed, 17 insertions(+)
diff --git a/testsuites/validation/tc-score-isr.c
b/testsuites/validation/tc-score-isr.c
index f29abbbfe8..9891829a84 100644
--- a/testsuites/validation/tc-score-isr.c
+++ b/testsuites/validation/tc-score-isr.c
@@ -128,6 +128,23 @@ void __wrap_bsp_interrupt_dispatch( void )
}
#endif
+#if defined(__microblaze__)
+void __real_bsp_interrupt_dispatch( uint32_t source );
+
+void __wrap_bsp_interrupt_dispatch( uint32_t source );
+
+void __wrap_bsp_interrupt_dispatch( uint32_t source )
+{
+ register uintptr_t sp __asm__( "1" );
+
+ if ( interrupted_stack_at_multitasking_start == 0 ) {
+interrupted_stack_at_multitasking_start = sp;
+ }
+
+ __real_bsp_interrupt_dispatch( source );
+}
+#endif
+
#if defined(__PPC__) || defined(__powerpc64__)
void __real_bsp_interrupt_dispatch( void );
--
2.34.1
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
Re: [PATCH] fixed warning related to spstdc17
Hello Zack, there is a bit more work to do to fix this warning. The warning fix should not result in a size increase of the uniprocessor RTEMS configuration. -- embedded brains GmbH Herr Sebastian HUBER Dornierstr. 4 82178 Puchheim Germany email: sebastian.hu...@embedded-brains.de phone: +49-89-18 94 741 - 16 fax: +49-89-18 94 741 - 08 Registergericht: Amtsgericht München Registernummer: HRB 157899 Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler Unsere Datenschutzerklärung finden Sie hier: https://embedded-brains.de/datenschutzerklaerung/ ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: [PATCH] validation: Add wrapped bsp_interrupt_dispatch for MicroBlaze
On 23.10.23 16:13, Alex White wrote: This adds a MicroBlaze-specific bsp_interrupt_dispatch wrapper which fixes a linker error. Thanks looks good. I am unable to build the MicroBlaze BSPs do to other errors for quite a while. -- embedded brains GmbH Herr Sebastian HUBER Dornierstr. 4 82178 Puchheim Germany email: sebastian.hu...@embedded-brains.de phone: +49-89-18 94 741 - 16 fax: +49-89-18 94 741 - 08 Registergericht: Amtsgericht München Registernummer: HRB 157899 Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler Unsere Datenschutzerklärung finden Sie hier: https://embedded-brains.de/datenschutzerklaerung/ ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
[docs] eng: Fix requirements how-to section
Requirements depending on application configuration should use the
described approach.
Update #3715.
---
eng/req/howto.rst | 67 +--
1 file changed, 24 insertions(+), 43 deletions(-)
diff --git a/eng/req/howto.rst b/eng/req/howto.rst
index ea4a57d..ad2b962 100644
--- a/eng/req/howto.rst
+++ b/eng/req/howto.rst
@@ -440,61 +440,42 @@ of :c:func:`rtems_signal_catch`:
Requirements Depending on Application Configuration Options
---
-Requirements which depend on application configuration options such as
+Requirements depending on application configuration options such as
:c:data:`CONFIGURE_MAXIMUM_PROCESSORS` should be written in the following
:ref:`syntax `:
**Where** , the shall .
-Use these clauses with care. Make sure all feature combinations are covered.
-Using a truth table may help. If a requirement depends on multiple features,
-use:
-
-**Where** , **where** , **where** , the
- shall .
-
-For application configuration options, use the clauses like this:
-
-:c:data:`CONFIGURE_MAXIMUM_PROCESSORS` equal to one
-
- **Where** the system was configured with a processor maximum of exactly
- one, ...
-
-:c:data:`CONFIGURE_MAXIMUM_PROCESSORS` greater than one
-
- **Where** the system was configured with a processor maximum greater than
- one, ...
-
-Please have a look at the following example used to specify
-:c:func:`rtems_signal_catch`. The example is a post-condition state
-specification of an action requirement, so there is an implicit set of
-pre-conditions and the trigger:
-
- **While** , **when** rtems_signal_catch() is called, ...
-
-The *where* clauses should be mentally placed before the *while* clauses.
+For action requirements, the **where** clauses should be added to the head of
+pre-conditions list. Please have a look at the following example used to
+specify :c:func:`rtems_task_construct`. The example is a pre-condition state
+specification of an action requirement:
.. code-block:: yaml
-post-conditions:
-- name: ASRInfo
+pre-conditions:
+- name: CPUs
states:
- - name: NopNoPreempt
+ - name: One
test-code: |
- if ( rtems_configuration_get_maximum_processors() > 1 ) {
-CheckNoASRChange( ctx );
- } else {
-CheckNewASRSettings( ctx );
+ if ( rtems_scheduler_get_processor_maximum() != 1 ) {
+${.:skip}
}
text: |
- Where the scheduler does not support the no-preempt mode, the ASR
- information of the caller of ${../if/catch:/name} shall not be
- changed by the ${../if/catch:/name} call.
-
- Where the scheduler does support the no-preempt mode, the ASR
- processing for the caller of ${../if/catch:/name} shall be done using
- the handler specified by ${../if/catch:/params[0]/name} in the mode
- specified by ${../if/catch:/params[1]/name}.
+ Where the system does not need inter-processor interrupts,
+ where the scheduler does support the no-preempt mode.
+ - name: More
+test-code: |
+ if ( rtems_scheduler_get_processor_maximum() == 1 ) {
+${.:skip}
+ }
+text: |
+ Where the system needs inter-processor interrupts,
+ where the scheduler does not support the no-preempt mode.
+
+The test case needs to run in all required configurations. This requires that
+the test case is added to multiple test suites. Use the ``${.:skip}``
+substitution to skip conditions not supported by the current configuration.
Action Requirements
---
--
2.35.3
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
