[PATCH] score: Simplify _Addresses_Is_aligned()

The CPU_ALIGNMENT must not be zero, this is also checked via a static assertion. Fix formatting. --- cpukit/include/rtems/score/address.h | 8 ++-- 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/cpukit/include/rtems/score/address.h b/cpukit/include/rtems/score/address.h index

Re: RSB documentation

I added a build of the partially restructured user manual here: https://ftp.rtems.org/pub/rtems/people/sebh/user.pdf On 13/01/2019 23:03, Chris Johns wrote: On 11/1/19 8:13 pm, Sebastian Huber wrote: At which position in the manual should it be placed? I think we should organize the chapters

Re: Rework parts of the user manual

On 13/01/2019 23:04, Chris Johns wrote: On 12/1/19 1:59 am, Sebastian Huber wrote: this is the first patch set targeting the user manual. My goal is to write an easy to follow quick start chapter which references other chapters for the details. Is there a build of this I could please review?

Re: rtems-test : getting result invalid

On Mon, 14 Jan 2019 at 03:39, Chris Johns wrote: > On 13/1/19 5:55 pm, Vijay Kumar Banerjee wrote: > > On Sun, 13 Jan 2019 at 08:41, Chris Johns > > wrote: > > > > On 13/1/19 7:19 am, Vijay Kumar Banerjee wrote: > > > > > > With the recent change to the qemu

RE: Strange RTEMS DMA Access on Zynq [Solved]

Thanks for this additional tidbit. I'm new to using DMA but haven't seen this behavior on any of the testing I've done so far with the AXI DMA, however, I do check the status register of the DMA and wait for the DMA to transition to the IDLE state prior to marking the DMAed data ready for use.

Re: Strange RTEMS DMA Access on Zynq [Solved]

On 14/1/19 9:02 am, Misra, Avinash wrote: > Thank you for your insightful email below, it went a long way towards solving > my issue. I wanted to describe what I ran into here in case someone else runs > into this in the future. Thank you for the follow up and nice work getting it running. >

Re: [PATCH] Fix 'build_max_size_human' ref. before assignment

On 14/1/19 8:05 am, Chris Johns wrote: > On 11/1/19 4:31 pm, Sebastian Huber wrote: >> - Am 11. Jan 2019 um 0:11 schrieb Chris Johns chr...@rtems.org: >> >>> On 10/1/19 11:17 pm, Sebastian Huber wrote: This patch resulted in this mail report issue: Your mail to 'build' with the s

Re: rtems-test : getting result invalid

On 13/1/19 5:55 pm, Vijay Kumar Banerjee wrote: > On Sun, 13 Jan 2019 at 08:41, Chris Johns > wrote: > > On 13/1/19 7:19 am, Vijay Kumar Banerjee wrote: > > > > With the recent change to the qemu options I'm getting results invalid > when > > running rtem

Re: Rework parts of the user manual

On 12/1/19 1:59 am, Sebastian Huber wrote: > this is the first patch set targeting the user manual. My goal is to write an > easy to follow quick start chapter which references other chapters for the > details. Is there a build of this I could please review? Thanks Chris ___

Re: RSB documentation

On 11/1/19 8:13 pm, Sebastian Huber wrote: > At which position in the manual should it be placed? I think we should > organize the chapters according to the relevance for new users and how the > are used later during application development. I would use the RSB chapter as > a reference chapter c

RE: Strange RTEMS DMA Access on Zynq [Solved]

Hi Chris, Thank you for your insightful email below, it went a long way towards solving my issue. I wanted to describe what I ran into here in case someone else runs into this in the future. My issue was comprised of 2 parts: 1.) Turns out I had an alignment issue with the DMA to begin with, w

RE: Zynq RTEMS 5 SMP Crashing on call to connect in socket.h [Solved]

Hi, My issue turned out to be a configuration issue where I was using the incorrect scheduler. I was originally using #define CONFIGURE_SCHEDULER_PRIORITY_AFFINITY_SMP when in fact I should have been using #define CONFIGURE_SCHEDULER_EDF_SMP. This thread (https://lists.rtems.org/pipermail/deve

Re: clang-format Style for RTEMS

Hello, to evaluate the effort needed to adapt clang-format for RTEMS, we are currently trying to implement the option to put the ")" at the end of a function declaration in a separate line, e.g.: bool _Thread_Initialize( Thread_Information *information, [...] Objects_Name

Re: [PATCH] Fix 'build_max_size_human' ref. before assignment

On 11/1/19 4:31 pm, Sebastian Huber wrote: > - Am 11. Jan 2019 um 0:11 schrieb Chris Johns chr...@rtems.org: > >> On 10/1/19 11:17 pm, Sebastian Huber wrote: >>> This patch resulted in this mail report issue: >>> >>> Your mail to 'build' with the subject >>> >>>     Build Linux: FAILED 6/rtems

[PATCH] FIXED: wrong configure switch for stm32f4 BSP

--- c/src/lib/libbsp/arm/stm32f4/configure.ac | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/c/src/lib/libbsp/arm/stm32f4/configure.ac b/c/src/lib/libbsp/arm/stm32f4/configure.ac index 7b621aa6d4..00ca0b73ae 100644 --- a/c/src/lib/libbsp/arm/stm32f4/configure.ac +++ b/c/src/l

Re: Status of RISCV port on sis

On 1/13/19 2:48 PM, Sebastian Huber wrote: > - Am 13. Jan 2019 um 0:09 schrieb Jiri Gaisler j...@gaisler.se: > >> On 1/11/19 1:36 PM, Jiri Gaisler wrote: >>> On 1/9/19 10:46 AM, Sebastian Huber wrote: Hello Jiri, could you please rebase your work to this RTEMS commit:

Re: Status of RISCV port on sis

- Am 13. Jan 2019 um 0:09 schrieb Jiri Gaisler j...@gaisler.se: > On 1/11/19 1:36 PM, Jiri Gaisler wrote: >> On 1/9/19 10:46 AM, Sebastian Huber wrote: >>> Hello Jiri, >>> >>> could you please rebase your work to this RTEMS commit: >>> >>> https://git.rtems.org/rtems/commit/?id=b9ffc41c9678fb3