RE: A virtio front-end driver for RTEMS

2016-03-20 Thread Jinhyun
Thank you for the comment. We got little bit delayed to meet the RTEMS coding standard. Regarding the source commitment, we have following questions. 1. Shall we just post diffs to the mailing list? (FYI, our implementation includes about 10 files and 1,300~1,500 lines total) 2. Will it be ok

Re: 4.11 Branch Failures

2016-03-20 Thread Joel Sherrill
On Sun, Mar 20, 2016 at 9:31 PM, Chris Johns wrote: > On 21/03/2016 13:24, Joel Sherrill wrote: > >> >> My 4.11 build sweep >> > > Thanks for doing this. > > isn't finished yet but there are a couple of things to report: >> > > Is this rc3 or the 4.11 branch in git? > > 4.11 on

Re: 4.11 Branch Failures

2016-03-20 Thread Chris Johns
On 21/03/2016 13:24, Joel Sherrill wrote: My 4.11 build sweep Thanks for doing this. isn't finished yet but there are a couple of things to report: Is this rc3 or the 4.11 branch in git? (1) The moxie tools failed to build. Please raise a ticket. (2) There is this group of powerpc

Re: GSOC 2016 Interested in Tracing

2016-03-20 Thread vivek kukreja
Hi Chris, Isaac I implemented a C program as Isaac said to parse and understand an example CTF trace stream based on an input config. It was really helpful to understand the overall CTF structure. Now im looking at the Capture Engine code to understand how concurrent buffering is supported

Re: [PATCH] [RSB 4.11] Bump OpenRISC versions

2016-03-20 Thread Hesham Almatary
On Mon, Mar 21, 2016 at 8:24 AM, Stefan Wallentowitz wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 20.03.2016 22:17, Hesham Almatary wrote: >> Hi Stefan, >> >> Thanks you! The gcc-4.8 patch was aging, so updating it is great. >> >> Have you had a chance

Re: epiphany tools on master

2016-03-20 Thread Hesham Almatary
On Mon, Mar 21, 2016 at 8:22 AM, Chris Johns wrote: > On 21/03/2016 08:13, Hesham Almatary wrote: >> >> I am not sure about the current Adapteva's plan to push their patches >> upstream. Last time I contacted them, they said they have higher >> priorities. > > > Who did you talk

Re: [PATCH] [RSB 4.11] Bump OpenRISC versions

2016-03-20 Thread Stefan Wallentowitz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 20.03.2016 22:17, Hesham Almatary wrote: > Hi Stefan, > > Thanks you! The gcc-4.8 patch was aging, so updating it is great. > > Have you had a chance to build the or1k BSP and run ticker or hello > on or1ksim with those new patches? > > Cheers,

Re: epiphany tools on master

2016-03-20 Thread Chris Johns
On 21/03/2016 08:13, Hesham Almatary wrote: I am not sure about the current Adapteva's plan to push their patches upstream. Last time I contacted them, they said they have higher priorities. Who did you talk to? Maybe we can take this off line and see what can be done about it. Chris

Re: [PATCH] Bump OpenRISC versions

2016-03-20 Thread Chris Johns
On 21/03/2016 02:04, Joel Sherrill wrote: Chris.. this is a 4.11 patch so I think you should approve/merge it. I don't want to push onto 4.11. Plus it should really have a ticket. Given your 4.11 sweep shows something is not building I think it is ok but I will let Heshman ack this change :)

Re: Status of 4.12 and Tool Masters

2016-03-20 Thread Chris Johns
On 21/03/2016 08:15, Joel Sherrill wrote: The 4.11 build sweep is about 1/2 way through. Is this with RSB from git or the 4.11.0-rc3 release? So far, avr and epiphany fail to build. avr is a gcc ICE and apparently I didn't build an epiphany toolset. I will wait for your build to finish.

Re: epiphany tools on master

2016-03-20 Thread Hesham Almatary
Hi, I am not sure about the current Adapteva's plan to push their patches upstream. Last time I contacted them, they said they have higher priorities. On Mon, Mar 21, 2016 at 3:04 AM, Joel Sherrill wrote: > Hi > > I don't seem to have any luck building epiphany tools for either

[PATCH 3/5] libstdthreads/thrd.c: Mark path as unreachable on GCC to resolve warning

2016-03-20 Thread Joel Sherrill
--- cpukit/libstdthreads/thrd.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/cpukit/libstdthreads/thrd.c b/cpukit/libstdthreads/thrd.c index c2e439f..cc2d20f 100644 --- a/cpukit/libstdthreads/thrd.c +++ b/cpukit/libstdthreads/thrd.c @@ -96,6 +96,9 @@ thrd_exit(int res) {

[PATCH 2/5] libnetworking/sys/libkern.h: Disable non-POSIX prototype that is actually unused

2016-03-20 Thread Joel Sherrill
--- cpukit/libnetworking/sys/libkern.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/cpukit/libnetworking/sys/libkern.h b/cpukit/libnetworking/sys/libkern.h index afeaa13..7aa6e8b 100644 --- a/cpukit/libnetworking/sys/libkern.h +++ b/cpukit/libnetworking/sys/libkern.h @@ -78,7 +78,9 @@

[PATCH 1/5] cpuuse/cpuusagetop.c: Fix unused variable warning

2016-03-20 Thread Joel Sherrill
--- cpukit/libmisc/cpuuse/cpuusagetop.c | 1 - cpukit/score/src/threadglobalconstruction.c | 3 +++ testsuites/sptests/Makefile.am | 2 +- testsuites/sptests/sp13/task1.c | 9 + 4 files changed, 9 insertions(+), 6 deletions(-) diff --git

[PATCH 4/5] telnetd.c: Fix no prototype warning

2016-03-20 Thread Joel Sherrill
--- cpukit/telnetd/telnetd.c | 9 + 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/cpukit/telnetd/telnetd.c b/cpukit/telnetd/telnetd.c index 70ccbe1..8152ce3 100644 --- a/cpukit/telnetd/telnetd.c +++ b/cpukit/telnetd/telnetd.c @@ -482,17 +482,18 @@ telnetd_dflt_spawn(const

[PATCH 5/5] sptests/Makefile.am: Enable sptls02

2016-03-20 Thread Joel Sherrill
--- testsuites/sptests/Makefile.am | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/testsuites/sptests/Makefile.am b/testsuites/sptests/Makefile.am index 53adfc1..43f3d82 100644 --- a/testsuites/sptests/Makefile.am +++ b/testsuites/sptests/Makefile.am @@ -65,7 +65,7 @@ _SUBDIRS

Re: Status of 4.12 and Tool Masters

2016-03-20 Thread Chris Johns
On 21/03/2016 4:52 AM, Joel Sherrill wrote: + moxie - requires dtc to build gdb. Does sb-check look for this? Not sure where to install this from on Centos 7. Need to use RTEMS RSB for this before building Moxie. Can this be addressed in the RSB? Yes, the 4.11 branch has DTC as

Warnings on RTEMS master

2016-03-20 Thread Joel Sherrill
Hi With the gcc and RTEMS masters, the warnings have crept up again. This is the summary. As always, this is something that takes continuous vigilance and anyone in the community can contribute. Take a look at your build logs and see if you can submit a patch or few to fix some warnings.

Status of 4.12 and Tool Masters

2016-03-20 Thread Joel Sherrill
Hi I did a sweep to build all tools and targets using the master on a Centos 7 host. The big change was a feature flag rework in newlib and Sebastian fixed the compile issues before I started. Here is what I have noted: + newlib - guard for ftello/fseeko is not right. Being fixed. + newlib -

[PATCH] [RSB 4.11] Bump OpenRISC versions

2016-03-20 Thread Stefan Wallentowitz
Bump the OpenRISC toolchain to newer versions. * Binutils to 2.26 * GCC to 4.9.3 * GDB to 7.9 updates #2668 --- rtems/config/4.11/rtems-or1k.bset | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/rtems/config/4.11/rtems-or1k.bset

epiphany tools on master

2016-03-20 Thread Joel Sherrill
Hi I don't seem to have any luck building epiphany tools for either epiphany-rtems4.12 or epiphany-elf on the master of binutils-gdb, gcc, and newlib. I am posting the current "add rtems" patch for posterity. It looks like epiphany-elf isn't supported by upstream binutils yet but it is in gdb.

[PATCH] [RSB 4.12/master] Bump OpenRISC versions

2016-03-20 Thread Stefan Wallentowitz
Bump the OpenRISC toolchain to newer versions. * Binutils to 2.26 * GCC to 4.9.3 * GDB to 7.11 updates #2669 --- rtems/config/4.12/rtems-or1k.bset | 15 --- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/rtems/config/4.12/rtems-or1k.bset

Re: [PATCH] Bump OpenRISC versions

2016-03-20 Thread Joel Sherrill
On Sun, Mar 20, 2016 at 10:06 AM, Stefan Wallentowitz < ste...@wallentowitz.de> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 20.03.2016 16:04, Joel Sherrill wrote: > > Chris.. this is a 4.11 patch so I think you should approve/merge > > it. I don't want to push onto 4.11. Plus

Re: [PATCH] Bump OpenRISC versions

2016-03-20 Thread Stefan Wallentowitz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 20.03.2016 16:04, Joel Sherrill wrote: > Chris.. this is a 4.11 patch so I think you should approve/merge > it. I don't want to push onto 4.11. Plus it should really have a > ticket. Okay, should I open it? > Stefan... I am in the middle of

Re: [PATCH] Bump OpenRISC versions

2016-03-20 Thread Joel Sherrill
Chris.. this is a 4.11 patch so I think you should approve/merge it. I don't want to push onto 4.11. Plus it should really have a ticket. Stefan... I am in the middle of testing new tools on 4.12 and Chris is trying to get the 4.11 branch wrapped up for a release. Would you might submitting a

Re: GSOC 2016 Project:Porting Rock on RTEMS

2016-03-20 Thread Gedare Bloom
I have a fundamental question. Is Rock the main issue, or does the Orocos port that uses RTEMS also need to be updated and verified? Can you run Orocos/RTEMS? On Sun, Mar 20, 2016 at 8:56 AM, Gedare Bloom wrote: > You need to register an account on the wiki, and then edit the

Re: GSOC 2016 Project:Porting Rock on RTEMS

2016-03-20 Thread Gedare Bloom
You need to register an account on the wiki, and then edit the page (link at bottom). On Sat, Mar 19, 2016 at 10:35 PM, Sambeet Panigrahi wrote: > Hi > I am attaching the link to my proposal with this mail This is not a final > draft and there's a lot of scope of

[PATCH] Bump OpenRISC versions

2016-03-20 Thread Stefan Wallentowitz
Bump the OpenRISC toolchain to newer versions. * Binutils to 2.26 * GCC to 4.9.3 * GDB to 7.9 --- rtems/config/4.11/rtems-or1k.bset | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/rtems/config/4.11/rtems-or1k.bset b/rtems/config/4.11/rtems-or1k.bset index

[PATCH] [RSB] Bump OpenRISC versions

2016-03-20 Thread Stefan Wallentowitz
Hi all, the following patch bumps the tools in the OpenRISC toolchain to more recent versions. Beside this is replaces the patch sets to be applied to GCC and GDB with official releases from the OpenRISC Github repository. The patch should preferably go into branch 4.11 and the current

Should rtems_error() use fprintf()?

2016-03-20 Thread Joel Sherrill
Hi I know this is a very old piece of code and predates printk() but should this routine be changed to use printk()? Is it still safe? Especially in light of SMP demands. --joel ___ devel mailing list devel@rtems.org

[PATCH 1/5] Guard ssize_t definition by _SSIZE_T_DECLARED

2016-03-20 Thread Sebastian Huber
This guard is used by FreeBSD for example. The FreeBSD network stack is used in RTEMS. * newlib/libc/include/sys/types.h (ssize_t): Guard by _SSIZE_T_DECLARED. --- newlib/libc/include/sys/types.h | 4 1 file changed, 4 insertions(+) diff --git

Re: GSOC - LwIP and Jailhouse hypervisor as possible tasks

2016-03-20 Thread Pavel Pisa
Hello Joel, On Sunday 20 of March 2016 02:06:48 Joel Sherrill wrote: > Thanks. The one in my directory is definitely ancient and should > be ignored. It was sent to me WAY TOO LONG after it was done > to be merged. I have moved that link after newer attempts list. > Does the page mention that

[PATCH 4/5] Add timingsafe_memcmp()

2016-03-20 Thread Sebastian Huber
This function is used by LibreSSL and OpenSSH and is provided by the OpenBSD libc. * libc/include/string.h (timingsafe_memcmp): Declare. * libc/string/timingsafe_memcmp.c: New file. * libc/string/Makefile.am: Add new file. * libc/string/Makefile.in: Regenerate. ---

GSoC 2016 Participation

2016-03-20 Thread Павел Мовчан
Hello all, I want to work with RTEMS and do some work for it. I find SMP and "Condition Variables"(status?) is very interesting for me. I can do some work to improve smp locks and synchronization primitives. "Merge Leon" project also seems interesting. Maybe community can aim me to right

RE: /bin/bash: no: command not found.

2016-03-20 Thread Wang, John (IVV-1800)
So I got much further with make. Now I have the following errors: no cru libscorecup.a libscorecup_a-cpu.o libscorecpu_a-cp_asm.o /bin/bash: no: command not found. Can anyone shed some light on this? Thanks John ___ devel mailing list