Re: [rtems commit] sp13: Update configuration to account for messages on fourth message queue

This test fix is all right, but it is not clear why this worked before. Something must have changed in RTEMS or the tool chain to trigger this bug and this might be an additional problem or not. On 15/04/15 21:21, Joel Sherrill wrote: Abusing this topic more, this is the complete analysis. I

RDUC2015 canceled

Hello, my last week's email to speak up for RDUC participation did not generate a great echo, so today we decided to cancel the RDUC2015 conference. It seems the way we prepared the conference did not meet the community requirements and expectations. In the long run I would like to have a

GCC build with for OR1K

Hello, I wanted to build the gcc5.0.0 for the or1k without patches and it did not work. Are there any patches missing? Below, the terminal output is given. *** Configuration or1k-unknown-rtems4.11 not supported make[1]: *** [configure-gcc] Error 1 make[1]: Leaving directory

Re: GCC build with for OR1K

Hi Alexander, The current GCC upstream support for OpenRISC is obsolete, it dates back to the old or32 port which is now replaced by or1k tools. OpenRISC folks are working on pushing their latest GCC or1k work upstream but they currently have some issues with FSF papers. For RTEMS or1k port to

[PING][PATCH v2] Change the assert in _Thread_Dispatch_decrement_disable_level

While cpu_self-thread_dispatch_disable_level shouldn't ever be zero, it would be better to check it before doing the decrement. Changes in v2: * Modified the asserts as requested in https://lists.rtems.org/pipermail/devel/2015-February/009821.html. ---

Re: [PATCH] sp13: Document message buffer usage and adjust configuration

Do you have any intuition to answer Sebastian's concern about why this test suddenly exposed a problem? (git-bisect?) On Thu, Apr 16, 2015 at 11:55 AM, Joel Sherrill joel.sherr...@oarcorp.com wrote: --- testsuites/sptests/sp13/system.h | 31 ++- 1 file changed, 26

[PATCH] sp13: Document message buffer usage and adjust configuration

--- testsuites/sptests/sp13/system.h | 31 ++- 1 file changed, 26 insertions(+), 5 deletions(-) diff --git a/testsuites/sptests/sp13/system.h b/testsuites/sptests/sp13/system.h index 3b170bf..f879096 100644 --- a/testsuites/sptests/sp13/system.h +++

Re: [PATCH] sp13: Document message buffer usage and adjust configuration

On 4/16/2015 11:14 AM, Gedare Bloom wrote: Do you have any intuition to answer Sebastian's concern about why this test suddenly exposed a problem? (git-bisect?) No. There have been so many changes lately that I assume something got tighter in confdefs.h. That's usually what it is. In general,

qemu fails to build with RSB on CentOS 6

Hi Has anyone seen this failure? $ make lt LINK vscclient /usr/bin/ld: -f may not be used without -shared collect2: ld returned 1 exit status make: *** [vscclient] Error 1 -- Joel Sherrill, Ph.D. Director of Research Development joel.sherr...@oarcorp.comOn-Line

zynq network testing on qemu

Hi Is there a short howto/example for this using the new TCP/IP stack? Luckily I have a qemu on a Fedora machine since I can't built it on the my CentOS VM right now. -- Joel Sherrill, Ph.D. Director of Research Development joel.sherr...@oarcorp.comOn-Line Applications

Re: qemu fails to build with RSB on CentOS 6

ld is really ld or gold? Version? El 16/4/2015 18:52, Joel Sherrill joel.sherr...@oarcorp.com escribió: Hi Has anyone seen this failure? $ make lt LINK vscclient /usr/bin/ld: -f may not be used without -shared collect2: ld returned 1 exit status make: *** [vscclient] Error 1 -- Joel