Re: Where to Store Requirements for RTEMS Components

On 23/05/2019 07:35, Chris Johns wrote: On 23/5/19 12:25 am, Sebastian Huber wrote: We definitely need a repository to store the requirements files (Doorstop, YAML). This is the first thing we have to know. If it later turns out that the choice was bad, we can still remove it from one repository

Re: Potential SIS or RTEMS/libbsd problem

On 22/05/2019 22:34, Jiri Gaisler wrote: On 5/22/19 7:43 PM, Jiri Gaisler wrote: On 5/22/19 9:49 AM, Sebastian Huber wrote: On 22/05/2019 09:39, Jiri Gaisler wrote: On 5/22/19 8:03 AM, Sebastian Huber wrote: Hello, in the libbsd there is a test for the Epoch Based Reclamation: https://git.r

Re: Where to Store Requirements for RTEMS Components

On 23/5/19 12:25 am, Sebastian Huber wrote: > We definitely need a repository to store the requirements files (Doorstop, > YAML). This is the first thing we have to know. If it later turns out that the > choice was bad, we can still remove it from one repository and do a subtree > import in another

Re: [PATCH] score: Compact objects class indices

On 22/05/2019 15:55, Joel Sherrill wrote: On Wed, May 22, 2019 at 8:40 AM Sebastian Huber > wrote: On 22/05/2019 15:23, Joel Sherrill wrote: > I'm OK with this. > > Is the statement that the API and class numbers are not > guaran

Re: Potential SIS or RTEMS/libbsd problem

On 5/22/19 7:43 PM, Jiri Gaisler wrote: > On 5/22/19 9:49 AM, Sebastian Huber wrote: >> On 22/05/2019 09:39, Jiri Gaisler wrote: >>> On 5/22/19 8:03 AM, Sebastian Huber wrote: Hello, in the libbsd there is a test for the Epoch Based Reclamation: https://git.rtems.org/rtems

Re: Potential SIS or RTEMS/libbsd problem

On 5/22/19 9:49 AM, Sebastian Huber wrote: > On 22/05/2019 09:39, Jiri Gaisler wrote: >> On 5/22/19 8:03 AM, Sebastian Huber wrote: >>> Hello, >>> >>> in the libbsd there is a test for the Epoch Based Reclamation: >>> >>> https://git.rtems.org/rtems-libbsd/tree/testsuite/epoch01/test_main.c >>> >>

Re: Where to Store Requirements for RTEMS Components

Hello Joel, On 22/05/2019 16:06, Joel Sherrill wrote: Where to store the artifacts and what component to do first are independent topics and should be on separate threads. I have changed the subject. On Wed, May 22, 2019 at 7:29 AM Ting Peng mailto:ting.p...@embedded-brains.de>> wrote:

Re: taking the Interrupt Manager Extension as an example for the qualification process

On Wed, May 22, 2019 at 3:37 AM Ting Peng wrote: > Hello, > > As we need to choose one RTEMS software component as an example to have > an overview of the qualification process, Sebastian Huber suggests to > take the Interrupt Manager Extension > ( > https://docs.rtems.org/doxygen/branches/master

Where to Store Requirements for RTEMS Components

Where to store the artifacts and what component to do first are independent topics and should be on separate threads. I have changed the subject. On Wed, May 22, 2019 at 7:29 AM Ting Peng wrote: > Hello, > > As to the requirements documentation, we need to decide a place to store > those require

Re: [PATCH] score: Compact objects class indices

On Wed, May 22, 2019 at 8:40 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 22/05/2019 15:23, Joel Sherrill wrote: > > I'm OK with this. > > > > Is the statement that the API and class numbers are not > > guaranteed to be held constant across releases something > > that shoul

Re: [PATCH] score: Compact objects class indices

On 22/05/2019 15:23, Joel Sherrill wrote: I'm OK with this. Is the statement that the API and class numbers are not guaranteed to be held constant across releases something that should be explicitly in a comment or requirement? The question is how can an application get one of the class number

Re: [PATCH] score: Compact objects class indices

I'm OK with this. Is the statement that the API and class numbers are not guaranteed to be held constant across releases something that should be explicitly in a comment or requirement? On Wed, May 22, 2019 at 12:52 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > --- > cpukit/

Re: Renaming examples-v2 to rtems-examples.

On Tue, May 21, 2019 at 7:24 PM Chris Johns wrote: > Hi, > > The examples-v2 repo's name should be rtems-examples. I would like to make > this > change. It will require a local repo edit of the URL to point to the new > name. > > Comments? > We've talked about this for years on and off. On refle

Re: taking the Interrupt Manager Extension as an example for the qualification process

Hello, As to the requirements documentation, we need to decide a place to store those requirements documentation. One suggestion is to store in rtems/reqs folder, the other is to store in rtems-docs/reqs folder. We suggest to put the requirements related files (by Doorstop) inside rtems/reqs

taking the Interrupt Manager Extension as an example for the qualification process

Hello, As we need to choose one RTEMS software component as an example to have an overview of the qualification process, Sebastian Huber suggests to take the Interrupt Manager Extension (https://docs.rtems.org/doxygen/branches/master/group__rtems__interrupt__extension.html) as the example. Th

Re: Potential SIS or RTEMS/libbsd problem

On 22/05/2019 09:39, Jiri Gaisler wrote: On 5/22/19 8:03 AM, Sebastian Huber wrote: Hello, in the libbsd there is a test for the Epoch Based Reclamation: https://git.rtems.org/rtems-libbsd/tree/testsuite/epoch01/test_main.c When I run this test using the leon3 BSP on real hardware (150MHz NGM

Re: Potential SIS or RTEMS/libbsd problem

On 5/22/19 8:03 AM, Sebastian Huber wrote: > Hello, > > in the libbsd there is a test for the Epoch Based Reclamation: > > https://git.rtems.org/rtems-libbsd/tree/testsuite/epoch01/test_main.c > > When I run this test using the leon3 BSP on real hardware (150MHz NGMP FP) > the test completes succ