Re: [PATCH] MAINTAINERS: Add myself to Write After Approval.

Hello Gedare, thanks for the approval. I'll coordinate that with Sebastian or just wait till the merge. Regards Christian Am 23.01.2018 um 00:38 schrieb Gedare Bloom: > Ahem, ask Sebastian to also put it on the no-preinstall branch. I'm > not quite sure the state of the master "freeze" at this

[PATCH] Xilinx AXI I2C driver IP race condition causes clock glitch.

Setting the PIRQ to 0 before reading the data produces a short clock pulse. Moving the write to after reading the data fixes the issue. Close #3173 --- cpukit/dev/i2c/xilinx-axi-i2c.c | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/cpukit/dev/i2c/xilinx-axi-i2c.c b/cpukit

Re: no-preinstall: Ready to merge

On Mon, Jan 22, 2018 at 5:59 PM, Chris Johns wrote: > On 23/01/2018 10:50, Joel Sherrill wrote: > > On Mon, Jan 22, 2018 at 4:35 PM, Chris Johns > > wrote: > > > > On 23/01/2018 01:49, Sebastian Huber wrote: > > > Hello, > > > > > > I installed all BSPs o

qoriq build failure on master

Hi powerpc-qoriq_core_0 and powerpc-qoriq_core_1 fail to build on the master. I have no changes. gmake[6]: Entering directory `/data/home/joel/rtems-work/rtems-testing/rtems/build-powerpc-qoriq_core_0-rtems/powerpc-rtems5/c/qoriq_core_0/testsuites/samples/capture' powerpc-rtems5-gcc -B../../../..

Re: no-preinstall: Ready to merge

On 23/01/2018 10:50, Joel Sherrill wrote: > On Mon, Jan 22, 2018 at 4:35 PM, Chris Johns > wrote: > > On 23/01/2018 01:49, Sebastian Huber wrote: > > Hello, > > > > I installed all BSPs of the master and then all BSPs of the > no-preinstall > > branch

Re: no-preinstall: Ready to merge

On Mon, Jan 22, 2018 at 4:35 PM, Chris Johns wrote: > On 23/01/2018 01:49, Sebastian Huber wrote: > > Hello, > > > > I installed all BSPs of the master and then all BSPs of the no-preinstall > > branch. The difference in installed BSP files is this: > > > > https://ftp.rtems.org/pub/rtems/people

Re: [PATCH] MAINTAINERS: Add myself to Write After Approval.

Ahem, ask Sebastian to also put it on the no-preinstall branch. I'm not quite sure the state of the master "freeze" at this point. You could also wait until after the merge happens. On Mon, Jan 22, 2018 at 6:37 PM, Gedare Bloom wrote: > Approved! > > On Mon, Jan 22, 2018 at 3:58 AM, Christian Mau

Re: [PATCH] MAINTAINERS: Add myself to Write After Approval.

Approved! On Mon, Jan 22, 2018 at 3:58 AM, Christian Mauderer wrote: > From: Christian Mauderer > > --- > MAINTAINERS | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/MAINTAINERS b/MAINTAINERS > index 35a149a932..2d91ecb149 100644 > --- a/MAINTAINERS > +++ b/MAINTAINERS > @@ -49,6 +49,7

Re: no-preinstall: Ready to merge

On 23/01/2018 01:49, Sebastian Huber wrote: > Hello, > > I installed all BSPs of the master and then all BSPs of the no-preinstall > branch. The difference in installed BSP files is this: > > https://ftp.rtems.org/pub/rtems/people/sebh/tmp/headers-diff.txt > > There are no removals. In the no-

Re: TEST BUILD strings

On 22/01/2018 20:07, Sebastian Huber wrote: > On 21/01/18 22:39, Chris Johns wrote: >>> This makes it easier to get the connection from the test output to the RTEMS >>> build options. >>> >> Does rtems-test need to be updated? > > The rtems-test program seems to not care about a particular TEST_BU

Re: [PATCH] rtems: Remove unused configuration files.

On 22/01/2018 21:11, Sebastian Huber wrote: > On 22/01/18 01:06, Joel Sherrill wrote: >> >> >> I am open to any ideas that improve how we use and manage the RSB. >> >> >> I don't want to move away from release branches or including the versions >> in the files. >> >> Having the versions in the

Re: no-preinstall: Architecture-specific header files

On 19/1/18 6:21 pm, Sebastian Huber wrote: > Hello, > > the architecture-specific header files are currently in: > > cpukit/score/cpu/@RTEMS_CPU@ > > For example: > > cpukit/score/cpu/sparc/rtems/score/cpu.h > > The new include directory for architecture-specific header files after the > prein

no-preinstall: Ready to merge

Hello, I installed all BSPs of the master and then all BSPs of the no-preinstall branch.  The difference in installed BSP files is this: https://ftp.rtems.org/pub/rtems/people/sebh/tmp/headers-diff.txt There are no removals.  In the no-preinstall installation, there are more header files pre

Re: [GSoC] Introduction and Hello World proof

I just came across this[3], so I'll follow the same instructions and (1) send the screenshot to Gedare/Joel and (2) add myself to the WIP wiki page. [3] https://lists.rtems.org/pipermail/devel/2018-January/019909.html ___ devel mailing list devel@rtems.o

[GSoC] Introduction and Hello World proof

Hey everyone! # Intro I'm still gaining familiarity with RTEMS, so I'm not sure about projects I might be interested in, but I'll make sure I communicate and discuss things as that changes. A little bit about who I am; I'm a final year (i.e. year 4) engineering student at Thakur College of Engin

[PATCH] rfs: Fix for 64-bit targets

The RTEMS_BLKIO_SETBLKSIZE IO control expects an uint32_t parameter and not a size_t which is 64-bits on 64-bit targets. Update #3082. --- cpukit/libfs/src/rfs/rtems-rfs-buffer.c | 2 +- cpukit/libfs/src/rfs/rtems-rfs-buffer.h | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a

Re: [PATCH] rtems: Remove unused configuration files.

On 22/01/18 01:06, Joel Sherrill wrote: I am open to any ideas that improve how we use and manage the RSB. I don't want to move away from release branches or including the versions in the files. Having the versions in the files makes it easy to upgrade all but one or two architectures.

Re: TEST BUILD strings

On 21/01/18 22:39, Chris Johns wrote: This makes it easier to get the connection from the test output to the RTEMS build options. Does rtems-test need to be updated? The rtems-test program seems to not care about a particular TEST_BUILD content: https://lists.rtems.org/pipermail/build/2018

RE: new to rtems , looking for some help

Hi Vijay, I usually start the configuration from the top level directory of rtems, but I would assume that you need to give configure the same options about which platform and BSP to build as in the normal setup. Just running ./configure will probably not work. Check out the getting started pag

[PATCH] MAINTAINERS: Add myself to Write After Approval.

From: Christian Mauderer --- MAINTAINERS | 1 + 1 file changed, 1 insertion(+) diff --git a/MAINTAINERS b/MAINTAINERS index 35a149a932..2d91ecb149 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -49,6 +49,7 @@ Daniel Hellstrom dan...@gaisler.com Ben Gras b...@rtems.or