Re: Scope of tracing for gsoc project

On Wed, Feb 10, 2021 at 12:11 PM Nenad Obradović < nenad.obradovic1...@gmail.com> wrote: > Couple of weeks ago I was trying to port RTEMS on HIFive Unleashed (dev. > board). I stopped doing it because of lack of time. > I wanted to merge HiFIVEs FSBL and RTEMS riscv Start.s so that the image > is

Re: Remaining Waf Conversion Tickets for Community and GSoC Students

On Wed, Feb 10, 2021, 5:31 PM Chris Johns wrote: > On 11/2/21 3:19 am, Joel Sherrill wrote: > > On Wed, Feb 10, 2021 at 9:58 AM Gedare Bloom > > wrote: > > On Wed, Feb 10, 2021 at 7:28 AM Joel Sherrill > > wrote: > > > On Tue, Feb 9, 2

Re: Should we document a time zone for the RTEMS epoch?

On 11/2/21 7:25 am, Gedare Bloom wrote: > On Wed, Feb 10, 2021 at 9:56 AM Joel Sherrill > wrote: > On Wed, Feb 10, 2021, 10:53 AM Sebastian Huber > > wrote: > On 10/02/2021 17:47, Joel Sherrill wrote: >

Re: Remaining Waf Conversion Tickets for Community and GSoC Students

On 11/2/21 3:19 am, Joel Sherrill wrote: > On Wed, Feb 10, 2021 at 9:58 AM Gedare Bloom > wrote: > On Wed, Feb 10, 2021 at 7:28 AM Joel Sherrill > wrote: > > On Tue, Feb 9, 2021 at 11:20 PM Sebastian Huber >

Re: Remaining Waf Conversion Tickets for Community and GSoC Students

On 11/2/21 10:07 am, Joel Sherrill wrote: > > > On Wed, Feb 10, 2021 at 5:00 PM Chris Johns > wrote: > > On 11/2/21 2:36 am, Sebastian Huber wrote: > > On 10/02/2021 16:19, Joel Sherrill wrote: > > > >> On Wed, Feb 10, 2021 at 8:40 AM Sebastian Huber >

Re: Remaining Waf Conversion Tickets for Community and GSoC Students

On 10/2/21 4:20 pm, Sebastian Huber wrote: > On 08/02/2021 10:40, Chris Johns wrote: >>> It is written in Python 3.6. >> We still need to support python 2. Maybe having this file support both could >> be >> part of the project. > I think this BSP builder is a development tool which can use Python

Re: Remaining Waf Conversion Tickets for Community and GSoC Students

On Wed, Feb 10, 2021 at 5:00 PM Chris Johns wrote: > On 11/2/21 2:36 am, Sebastian Huber wrote: > > On 10/02/2021 16:19, Joel Sherrill wrote: > > > >> On Wed, Feb 10, 2021 at 8:40 AM Sebastian Huber > >> >> > wrote: > >> > >> On 10/02/2021 15:27, Jo

Re: Remaining Waf Conversion Tickets for Community and GSoC Students

On 11/2/21 2:36 am, Sebastian Huber wrote: > On 10/02/2021 16:19, Joel Sherrill wrote: > >> On Wed, Feb 10, 2021 at 8:40 AM Sebastian Huber >> > > wrote: >> >>     On 10/02/2021 15:27, Joel Sherrill wrote: >> >>     > On Tue, Feb 9, 2021 at 11:20 PM Sebas

Re: Revisiting Minimum with Static Allocation

On Wed, Feb 10, 2021 at 2:36 PM Gedare Bloom wrote: > > > On Wed, Feb 10, 2021 at 10:57 AM Joel Sherrill wrote: > >> Hi >> >> The minimum sample is intended to show how to construct the minimum >> footprint RTEMS application. I suspect that with Sebastian's recent work on >> static allocation an

Capstone and Covoar

Hi Alex is getting closer to having covoar working well again and he and I having audited some results for sanity. Hopefully this will turn into patches in the next week or so. (putting pressure on him there :) ) Alex did some benchmarking and objdump appears to be taking 75-80% of the execution

Re: Revisiting Minimum with Static Allocation

On Wed, Feb 10, 2021 at 10:57 AM Joel Sherrill wrote: > Hi > > The minimum sample is intended to show how to construct the minimum > footprint RTEMS application. I suspect that with Sebastian's recent work on > static allocation and reducing footprint, the minimum sample may be able to > benefit

Re: [PATCH v2 00/12] Generate documentation for managers

On Wed, Feb 10, 2021 at 9:46 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 10/02/2021 17:42, Gedare Bloom wrote: > > > Is (will be) there a section to explain the Constraints and how to > > interpret them? Mainly, what kind of constraints are specified, and > > what should b

Re: Should we document a time zone for the RTEMS epoch?

On Wed, Feb 10, 2021 at 9:56 AM Joel Sherrill wrote: > > > On Wed, Feb 10, 2021, 10:53 AM Sebastian Huber < > sebastian.hu...@embedded-brains.de> wrote: > >> On 10/02/2021 17:47, Joel Sherrill wrote: >> >> > >> > >> > On Wed, Feb 10, 2021, 10:30 AM Sebastian Huber >> > > >

Re: Question regarding RSB and open projects

On Thu, Feb 11, 2021 at 12:26 AM Ayushman Mishra wrote: > I tested the environment ./source-builder/sb-check , it gave this > result: RTEMS Source Builder - Check, 6 (61dcadee0825) > Environment is ok > When I used ../source-builder/sb-set-builder > --prefix=/home/ayush/quickstart1/rtems/6 --targ

Re: Question regarding RSB and open projects

On Wed, Feb 10, 2021, 12:57 PM Ayushman Mishra wrote: > I tested the environment ./source-builder/sb-check , it gave this > result: RTEMS Source Builder - Check, 6 (61dcadee0825) > Environment is ok > When I used ../source-builder/sb-set-builder > --prefix=/home/ayush/quickstart1/rtems/6 --target

Re: Question regarding RSB and open projects

I tested the environment ./source-builder/sb-check , it gave this result: RTEMS Source Builder - Check, 6 (61dcadee0825) Environment is ok When I used ../source-builder/sb-set-builder --prefix=/home/ayush/quickstart1/rtems/6 --target=sparc-rtems6 --with-rtems-bsp=erc32 --with-rtems-tests=yes 6/rtem

Revisiting Minimum with Static Allocation

Hi The minimum sample is intended to show how to construct the minimum footprint RTEMS application. I suspect that with Sebastian's recent work on static allocation and reducing footprint, the minimum sample may be able to benefit from tweaking. I just checked rtl22xx_t and it is < 16K code and 2

Re: Should we document a time zone for the RTEMS epoch?

On Wed, Feb 10, 2021, 10:53 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 10/02/2021 17:47, Joel Sherrill wrote: > > > > > > > On Wed, Feb 10, 2021, 10:30 AM Sebastian Huber > > > > wrote: > > > > On 10/02/2021 07:53, Sebastian

Re: Should we document a time zone for the RTEMS epoch?

On 10/02/2021 17:47, Joel Sherrill wrote: On Wed, Feb 10, 2021, 10:30 AM Sebastian Huber > wrote: On 10/02/2021 07:53, Sebastian Huber wrote: > Hello, > > I try to update the clock manager documentation and noticed that there

Re: [PATCH v2 07/12] c-user: Add control block acronyms

On 10/02/2021 17:48, Gedare Bloom wrote: +    DPCB DPMCB? +        This term is an acronym for Dual-Ported Memory Control Block. I checked the exiting documentation again, it is DPCB. I would not change it. -- embedded brains GmbH Herr Sebastian HUBER Dornierstr. 4 82178 Puchheim

Re: [PATCH v2 06/12] c-user: Add labels to the manager chapters

On Wed, Feb 10, 2021 at 9:48 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 10/02/2021 17:45, Gedare Bloom wrote: > > > > > -For more information on user extensions, refer to :ref:`User > > Extensions Manager`. > > +For more information on user extensions, refer t

Re: [PATCH v2 07/12] c-user: Add control block acronyms

On Wed, Feb 10, 2021 at 9:28 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > Update #3993. > --- > c-user/glossary.rst | 14 +- > 1 file changed, 13 insertions(+), 1 deletion(-) > > diff --git a/c-user/glossary.rst b/c-user/glossary.rst > index c3907f5..65e1fd7 10064

Re: [PATCH v2 06/12] c-user: Add labels to the manager chapters

On 10/02/2021 17:45, Gedare Bloom wrote: -For more information on user extensions, refer to :ref:`User Extensions Manager`. +For more information on user extensions, refer to :ref:`RTEMSAPIClassicUserext`. Is there a naming rule you used, especially to determine how to abbrev

Re: Should we document a time zone for the RTEMS epoch?

On Wed, Feb 10, 2021, 10:30 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 10/02/2021 07:53, Sebastian Huber wrote: > > > Hello, > > > > I try to update the clock manager documentation and noticed that there > > is no time zone specified for the RTEMS epoch. In the timecounte

Re: [PATCH v2 00/12] Generate documentation for managers

On 10/02/2021 17:42, Gedare Bloom wrote: Is (will be) there a section to explain the Constraints and how to interpret them? Mainly, what kind of constraints are specified, and what should be assumed (like, if a directive does not say it can be called from thread context, then it implicitly can

Re: [PATCH v2 06/12] c-user: Add labels to the manager chapters

On Wed, Feb 10, 2021 at 9:28 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > Update #3993. > --- > c-user/board_support_packages.rst| 2 +- > c-user/clock/index.rst | 2 ++ > c-user/config/scheduler-general.rst | 2 +- > c-user/dual-ported-memory/index.rst |

Re: Remaining Waf Conversion Tickets for Community and GSoC Students

On Wed, Feb 10, 2021 at 10:27 AM Gedare Bloom wrote: > > > On Wed, Feb 10, 2021 at 9:20 AM Joel Sherrill wrote: > >> >> >> On Wed, Feb 10, 2021 at 9:58 AM Gedare Bloom wrote: >> >>> On Wed, Feb 10, 2021 at 7:28 AM Joel Sherrill wrote: >>> > >>> > >>> > >>> > On Tue, Feb 9, 2021 at 11:20 PM Seb

Re: [PATCH v2 00/12] Generate documentation for managers

Is (will be) there a section to explain the Constraints and how to interpret them? Mainly, what kind of constraints are specified, and what should be assumed (like, if a directive does not say it can be called from thread context, then it implicitly cannot)? On Wed, Feb 10, 2021 at 9:28 AM Sebasti

Re: Rules for Commit Messages

On 10/02/2021 16:38, Gedare Bloom wrote: https://devel.rtems.org/wiki/Developer/Git#GitCommits We also have: https://docs.rtems.org/branches/master/user/support/contrib.html It lacks details for the commit messages. -- embedded brains GmbH Herr Sebastian HUBER Dornierstr. 4 82178 Puchheim

Re: Should we document a time zone for the RTEMS epoch?

On 10/02/2021 07:53, Sebastian Huber wrote: Hello, I try to update the clock manager documentation and noticed that there is no time zone specified for the RTEMS epoch. In the timecounter initialization we use: static struct timehands th0 = { [...] #ifdef __rtems__     .th_bintime = { .sec

[PATCH v2 06/12] c-user: Add labels to the manager chapters

Update #3993. --- c-user/board_support_packages.rst| 2 +- c-user/clock/index.rst | 2 ++ c-user/config/scheduler-general.rst | 2 +- c-user/dual-ported-memory/index.rst | 2 ++ c-user/event/index.rst | 2 ++ c-user/interrupt/index.rst | 2 ++ c-user/io/

[PATCH v2 12/12] c-user: Generate clock manager documentation

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/clock/dire

[PATCH v2 09/12] c-user: Generate semaphore manager documentation

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/semaphore/

[PATCH v2 10/12] c-user: Generate barrier manager documentation

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/barrier/di

[PATCH v2 11/12] c-user: Generate user extensions 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/user-exten

[PATCH v2 08/12] c-user: Move deprecated/removed directives

This makes it easier to automatically generate parts of the manager documentation in the future. Update #3993. --- c-user/clock/index.rst| 1 + c-user/clock/removed-directives.rst | 81 c-user/task/deprecated-directives.rst | 46 + c-user/task/index.rst

[PATCH v2 05/12] c-user: Clarify object services documentation

Unify the wording across similar directives of other managers. Update #3993. --- c-user/object-services/directives.rst | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/c-user/object-services/directives.rst b/c-user/object-services/directives.rst index 19d4d82..54f

[PATCH v2 01/12] c-user: Clarify timer manager documentation

Unify the wording across similar directives of other managers. Add "CONSTRAINTS" section. Update #3993. --- c-user/timer/directives.rst | 212 ++ c-user/timer/index.rst| 2 + c-user/timer/introduction.rst | 2 +- 3 files changed, 164 insertions(+), 5

[PATCH v2 07/12] c-user: Add control block acronyms

Update #3993. --- c-user/glossary.rst | 14 +- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/c-user/glossary.rst b/c-user/glossary.rst index c3907f5..65e1fd7 100644 --- a/c-user/glossary.rst +++ b/c-user/glossary.rst @@ -1,7 +1,7 @@ .. SPDX-License-Identifier: CC-BY-SA

[PATCH v2 04/12] c-user: Clarify IO manager documentation

Unify the wording across similar directives of other managers. Update #3993. --- c-user/io/directives.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/c-user/io/directives.rst b/c-user/io/directives.rst index a6cd755..0683c4c 100644 --- a/c-user/io/directives.rst +++

[PATCH v2 00/12] Generate documentation for managers

This patch adds the next round of generated documentation. Patches 1 to 5 try to unify the documentation accross managers. The other patches add the generated documentation for the Semaphore, Barrier, User Extensions, and Clock Managers. Here is the updated document for review: https://ftp.rtem

[PATCH v2 03/12] c-user: Clarify partition manager documentation

--- c-user/partition/directives.rst | 24 +++- 1 file changed, 15 insertions(+), 9 deletions(-) diff --git a/c-user/partition/directives.rst b/c-user/partition/directives.rst index 0d35136..98c0eb1 100644 --- a/c-user/partition/directives.rst +++ b/c-user/partition/directives.

[PATCH v2 02/12] c-user: Clarify event manager documentation

Unify the wording across similar directives of other managers. Add "CONSTRAINTS" section. Update #3993. --- c-user/event/directives.rst | 57 --- c-user/event/introduction.rst | 2 +- 2 files changed, 41 insertions(+), 18 deletions(-) diff --git a/c-user/event

Re: Remaining Waf Conversion Tickets for Community and GSoC Students

On Wed, Feb 10, 2021 at 9:20 AM Joel Sherrill wrote: > > > On Wed, Feb 10, 2021 at 9:58 AM Gedare Bloom wrote: > >> On Wed, Feb 10, 2021 at 7:28 AM Joel Sherrill wrote: >> > >> > >> > >> > On Tue, Feb 9, 2021 at 11:20 PM Sebastian Huber < >> sebastian.hu...@embedded-brains.de> wrote: >> >> >> >

Re: Remaining Waf Conversion Tickets for Community and GSoC Students

On Wed, Feb 10, 2021 at 9:58 AM Gedare Bloom wrote: > On Wed, Feb 10, 2021 at 7:28 AM Joel Sherrill wrote: > > > > > > > > On Tue, Feb 9, 2021 at 11:20 PM Sebastian Huber < > sebastian.hu...@embedded-brains.de> wrote: > >> > >> > >> On 08/02/2021 10:40, Chris Johns wrote: > >> >> It is written i

Re: [PATCH 0/8] Generate documentation for managers

Hello Frank, thanks for the review. On 10/02/2021 11:35, Frank Kühndel wrote: Hello Sebastian, this actually really improves the documentation. The new constraints sections makes it clearer when a function can be used. Moreover, there are new descriptions of all parameters. I guess you must ha

Re: Remaining Waf Conversion Tickets for Community and GSoC Students

On Wed, Feb 10, 2021 at 7:28 AM Joel Sherrill wrote: > > > > On Tue, Feb 9, 2021 at 11:20 PM Sebastian Huber > wrote: >> >> >> On 08/02/2021 10:40, Chris Johns wrote: >> >> It is written in Python 3.6. >> > We still need to support python 2. Maybe having this file support both >> > could be >>

Re: Rules for Commit Messages

Thanks. Did we miss moving this to the docs? On Wed, Feb 10, 2021 at 9:38 AM Gedare Bloom wrote: > https://devel.rtems.org/wiki/Developer/Git#GitCommits > > On Wed, Feb 10, 2021 at 8:06 AM Joel Sherrill wrote: > > > > Hi > > > > I was looking for guidance on how we write a commit message to pr

Re: Remaining Waf Conversion Tickets for Community and GSoC Students

On Wed, Feb 10, 2021 at 9:36 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 10/02/2021 16:19, Joel Sherrill wrote: > > > On Wed, Feb 10, 2021 at 8:40 AM Sebastian Huber > > > > wrote: > > > > On 10/02/2021 15:27, Joel Sherrill w

Re: Rules for Commit Messages

https://devel.rtems.org/wiki/Developer/Git#GitCommits On Wed, Feb 10, 2021 at 8:06 AM Joel Sherrill wrote: > > Hi > > I was looking for guidance on how we write a commit message to provide it to > someone. Unfortunately, I don't see it in the Software Engineering Guide > although I admit I coul

Re: Remaining Waf Conversion Tickets for Community and GSoC Students

On 10/02/2021 16:19, Joel Sherrill wrote: On Wed, Feb 10, 2021 at 8:40 AM Sebastian Huber > wrote: On 10/02/2021 15:27, Joel Sherrill wrote: > On Tue, Feb 9, 2021 at 11:20 PM Sebastian Huber > mailto:sebastian.hu...@embedded-brains.de>

Re: Remaining Waf Conversion Tickets for Community and GSoC Students

On Wed, Feb 10, 2021 at 8:40 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 10/02/2021 15:27, Joel Sherrill wrote: > > > On Tue, Feb 9, 2021 at 11:20 PM Sebastian Huber > > > > wrote: > > > > > > On 08/02/2021 10:40, Chris Johns

Rules for Commit Messages

Hi I was looking for guidance on how we write a commit message to provide it to someone. Unfortunately, I don't see it in the Software Engineering Guide although I admit I could have missed it. I assume it would be something like this: [area|file]: Brief description Longer description hopefully

Re: Remaining Waf Conversion Tickets for Community and GSoC Students

On 10/02/2021 15:27, Joel Sherrill wrote: On Tue, Feb 9, 2021 at 11:20 PM Sebastian Huber > wrote: On 08/02/2021 10:40, Chris Johns wrote: >> It is written in Python 3.6. > We still need to support python 2. Maybe having this file sup

Re: Remaining Waf Conversion Tickets for Community and GSoC Students

On Tue, Feb 9, 2021 at 11:20 PM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > > On 08/02/2021 10:40, Chris Johns wrote: > >> It is written in Python 3.6. > > We still need to support python 2. Maybe having this file support both > could be > > part of the project. > I think this B

Re: [PATCH 0/8] Generate documentation for managers

Hello Sebastian, this actually really improves the documentation. The new constraints sections makes it clearer when a function can be used. Moreover, there are new descriptions of all parameters. I guess you must have looked in the source code, to figure out the correct set of errors each directi