Re: [PATCH 2/3] user: Add A53 Qemu run instructions

On Fri, Dec 11, 2020 at 11:58 AM Kinsey Moore wrote: > *From:* Gedare Bloom > *Sent:* Friday, December 11, 2020 07:41 > *To:* Kinsey Moore > *Cc:* devel@rtems.org > *Subject:* Re: [PATCH 2/3] user: Add A53 Qemu run instructions > > > > > > > > On Tue, Dec 8, 2020 at 11:03 AM Kinsey Moore >

RE: [PATCH 1/2] tm27: Use generic cpu index accessor

-Original Message- From: Sebastian Huber Sent: Friday, December 11, 2020 13:00 To: Kinsey Moore ; devel@rtems.org Subject: Re: [PATCH 1/2] tm27: Use generic cpu index accessor > On 11/12/2020 16:09, Kinsey Moore wrote: > >> Unfortunately, that's the only API currently available to get

Re: CMake support

I added the suggestions by Chris Johns now and performed some more tests (for example disabling the default compiler checks, custom checks are required for RTEMS). I used RTEMS_PREFIX instead of PREFIX because PREFIX appears to be a reserved name in CMake, and RTEMS_PREFIX is also a little bit

Re: [PATCH 1/2] tm27: Use generic cpu index accessor

On 11/12/2020 16:09, Kinsey Moore wrote: -Original Message- From: Sebastian Huber Sent: Thursday, December 10, 2020 23:48 To: Kinsey Moore;devel@rtems.org Subject: Re: [PATCH 1/2] tm27: Use generic cpu index accessor On 10/12/2020 21:42, Kinsey Moore wrote: The arm_cp15 function

RE: [PATCH 2/3] user: Add A53 Qemu run instructions

From: Gedare Bloom Sent: Friday, December 11, 2020 07:41 To: Kinsey Moore Cc: devel@rtems.org Subject: Re: [PATCH 2/3] user: Add A53 Qemu run instructions On Tue, Dec 8, 2020 at 11:03 AM Kinsey Moore mailto:kinsey.mo...@oarcorp.com>> wrote: --- user/bsps/aarch64/a53.rst | 7 +++ 1 file

Re: Build FreeBSD: FAILED 6/rtems-arm on x86_64-freebsd12.1 (arm-rtems6-gcc-c25f7ea-newlib-21ec498-x86_64-freebsd12.1-1)

On 11/12/2020 18:22, sebastian.hu...@embedded-brains.de wrote: /usr/home/user/rtems-source-builder/rtems/build/arm-rtems6-gcc-c25f7ea-newlib-21ec498-x86_64-freebsd12.1-1/build/./gcc/xgcc

Re: [PATCH v2] eng: Requirements counting shall start at zero

On Fri, Dec 11, 2020 at 10:38 AM Gedare Bloom wrote: > > > On Fri, Dec 11, 2020 at 9:12 AM Frank Kühndel < > frank.kuehn...@embedded-brains.de> wrote: > >> Hello Gedare, >> >> On 12/11/20 4:41 PM, Gedare Bloom wrote: >> > >> > >> > On Fri, Dec 11, 2020 at 8:16 AM Frank Kühndel >> > > >

Re: [PATCH v2] eng: Requirements counting shall start at zero

On Fri, Dec 11, 2020 at 9:12 AM Frank Kühndel < frank.kuehn...@embedded-brains.de> wrote: > Hello Gedare, > > On 12/11/20 4:41 PM, Gedare Bloom wrote: > > > > > > On Fri, Dec 11, 2020 at 8:16 AM Frank Kühndel > > > > wrote: > > > > Hello Joel, > > >

Re: [PATCH v2] eng: Requirements counting shall start at zero

Hello Gedare, On 12/11/20 4:41 PM, Gedare Bloom wrote: > > > On Fri, Dec 11, 2020 at 8:16 AM Frank Kühndel > > wrote: > > Hello Joel, > > On 12/11/20 3:49 PM, Joel Sherrill wrote: > > > > > > On Fri, Dec 11, 2020, 8:41 AM Frank

Re: [PATCH v2] eng: Requirements counting shall start at zero

Hello Andrew, I did not intent to become the authority in numbering files. :-) Maybe Sebastian has some advice as he knows your application better than I do. I personally would be pragmatic and do what seems to be an easy to realize as well as a good solution. Greetings Frank On 12/11/20

Re: [PATCH v2] eng: Requirements counting shall start at zero

On Fri, Dec 11, 2020 at 8:16 AM Frank Kühndel < frank.kuehn...@embedded-brains.de> wrote: > Hello Joel, > > On 12/11/20 3:49 PM, Joel Sherrill wrote: > > > > > > On Fri, Dec 11, 2020, 8:41 AM Frank Kuehndel > > > > wrote: > > > > From: Frank Kühndel

Re: [PATCH v2] eng: Requirements counting shall start at zero

Hello Frank, I have a use case where the numbers will exceed 10 . It's not for numbered requirements but numbered test-files. These result from different scenarios generated by our SPIN models, as part of the qualification activity. The files are generated (and numbered) automatically, so the

Re: [PATCH v2] eng: Requirements counting shall start at zero

Hello Joel, On 12/11/20 3:49 PM, Joel Sherrill wrote: > > > On Fri, Dec 11, 2020, 8:41 AM Frank Kuehndel > > wrote: > > From: Frank Kühndel > > > --- >  eng/req/req-for-req.rst | 21

RE: [PATCH 1/2] tm27: Use generic cpu index accessor

-Original Message- From: Sebastian Huber Sent: Thursday, December 10, 2020 23:48 To: Kinsey Moore ; devel@rtems.org Subject: Re: [PATCH 1/2] tm27: Use generic cpu index accessor > On 10/12/2020 21:42, Kinsey Moore wrote: >> The arm_cp15 function for accessing the current CPU index is

Re: [PATCH v2] eng: Requirements counting shall start at zero

On Fri, Dec 11, 2020, 8:41 AM Frank Kuehndel < frank.kuehn...@embedded-brains.de> wrote: > From: Frank Kühndel > > --- > eng/req/req-for-req.rst | 21 + > 1 file changed, 21 insertions(+) > > diff --git a/eng/req/req-for-req.rst b/eng/req/req-for-req.rst > index

[PATCH v2] eng: Requirements counting shall start at zero

From: Frank Kühndel --- eng/req/req-for-req.rst | 21 + 1 file changed, 21 insertions(+) diff --git a/eng/req/req-for-req.rst b/eng/req/req-for-req.rst index 9225e95..dcc4c11 100644 --- a/eng/req/req-for-req.rst +++ b/eng/req/req-for-req.rst @@ -308,6 +308,27 @@

Re: [PATCH] tester: Add configs for AArch64 ZynqMP BSPs

looks ok to push assuming it works :) On Tue, Dec 8, 2020 at 11:03 AM Kinsey Moore wrote: > --- > .../testing/bsps/xilinx_zynqmp_ilp32.ini | 38 +++ > .../rtems/testing/bsps/xilinx_zynqmp_lp64.ini | 38 +++ > 2 files changed, 76 insertions(+) > create mode

Re: [PATCH 2/3] user: Add A53 Qemu run instructions

On Tue, Dec 8, 2020 at 11:03 AM Kinsey Moore wrote: > --- > user/bsps/aarch64/a53.rst | 7 +++ > 1 file changed, 7 insertions(+) > > diff --git a/user/bsps/aarch64/a53.rst b/user/bsps/aarch64/a53.rst > index 73735b1..e3a89f8 100644 > --- a/user/bsps/aarch64/a53.rst > +++

Re: [PATCH 5/5] bsps/arm: Move BSP_START_IN_HYP_SUPPORT option

On Wed, Dec 9, 2020 at 9:50 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > Clarify documentation. > > Update #4202. > --- > .../bsps/arm/{raspberrypi/optenhyp.yml => optstarthyp.yml} | 3 ++- > spec/build/bsps/arm/raspberrypi/grp.yml| 2 +- > 2

Re: [PATCH] eng: Requirements counting shall start at zero

I don't mind starting 0 or 1, consistency is important. If we know the max count (N) ahead of time, it can be helpful to generate with a 0-padded number. This makes every name a consistent size and can be sorted lexicographically. On Wed, Dec 9, 2020 at 6:50 AM Sebastian Huber <

Re: [PATCH] config: Fix invalid static assertions in C

On Fri, Dec 11, 2020, 7:26 AM Gedare Bloom wrote: > Hi Sebastian, > > On Fri, Dec 11, 2020 at 5:57 AM Sebastian Huber < > sebastian.hu...@embedded-brains.de> wrote: > >> Expressions in static assertions must be integral constant expressions. >> In >> integral constant expressions the use of

Re: [PATCH] config: Fix invalid static assertions in C

Hi Sebastian, On Fri, Dec 11, 2020 at 5:57 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > Expressions in static assertions must be integral constant expressions. In > integral constant expressions the use of address constant expressions is > not > allowed. > > In static

[PATCH] Add GMP as a prerequisite for GDB

--- bare/config/devel/gmp-6.1.0.cfg | 18 ++ rtems/config/6/rtems-default.bset | 1 + rtems/config/7/rtems-default.bset | 1 + source-builder/config/gmp.cfg | 60 +++ 4 files changed, 80 insertions(+) create mode 100644 bare/config/devel/gmp-6.1.0.cfg

Re: [PATCH v2 0/1] xilinx_zynq: Enable support for 4kiB MMU pages

On 11/12/2020 11:02, jan.som...@dlr.de wrote: Could someone please push these changes? I think this is the last patchset from me which is open. I check it in with minor modifications. -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89

[PATCH] config: Fix invalid static assertions in C

Expressions in static assertions must be integral constant expressions. In integral constant expressions the use of address constant expressions is not allowed. In static initializers the address constant expressions are allowed. Introduce a new macro _CONFIGURE_ASSERT_NOT_NULL() which leads to

Re: CMake support

Hi, There seems to be positive feedback, thanks for that. I can adapt the naming to be more consistent with your system. My system is currently assuming that the RTEMS tools and the BSP are both located at RTEMS_INST I guess the first command: cmake -DPREFIX=/install-point

RE: [PATCH v2 0/1] xilinx_zynq: Enable support for 4kiB MMU pages

Could someone please push these changes? I think this is the last patchset from me which is open. Cheers, Jan > -Original Message- > From: Sommer, Jan > Sent: Friday, November 27, 2020 2:43 PM > To: devel@rtems.org > Cc: Sommer, Jan > Subject: [PATCH v2 0/1] xilinx_zynq: Enable

Re: CMake support

Hi all, > I was wondering whether CMake support or an example is available or will be added in the future. We are using a framework which has different abstraction layers for OSes like (embedded) Linux, RTEMS and FreeRTOS, but we would like to use the same build system to build applications and