How to submit hello world proof?

2019-02-06 Thread Ravindra Meena
Hi,

I have completed the GSOC getting started and have modified the hello world
program. Now I would like to submit proof. How should I proceed?

Thanks

-- 
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
, Dhanbad
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH] Coverage: Add support for TSIM format

2019-02-06 Thread Vijay Kumar Banerjee
On Wed, 6 Feb 2019 at 02:35, Chris Johns  wrote:

> On 6/2/19 1:41 am, Vijay Kumar Banerjee wrote:
> > On Tue, 5 Feb 2019 at 03:37, Chris Johns  > > wrote:
>  On 1/2/19 10:47 pm, Vijay Kumar Banerjee wrote:
> > >  self.trace = trace
> > >  self.prefix = prefix
> > > +self.bsp = bsp
> > >
> > >  def _find_covoar(self):
> > >  covoar_exe = 'covoar'
> > > @@ -316,10 +323,18 @@ class covoar(object):
> > >  if not path.exists(symbol_file):
> > >  raise error.general('coverage: no symbol set file:
> %s'%
> > (symbol_file))
> > >  exe = self._find_covoar()
> > > -command = exe + ' -S ' + symbol_file + \
> > > -  ' -O ' + covoar_result_dir + \
> > > -  ' -E ' + self.explanations_txt + \
> > > -  ' -p ' + self.project_name + ' ' +
> self.executables
> > > +if 'qemu' in self.bsp.split('-'):
> >
> > Are you checking for 'qemu' in the BSP name? The naming used here is
> a
> > convention and making the code depend on a naming convention is
> fragile. Lets
> > not do this.
> >
> > There is a `%{qemu-cmd}` macro defined which must exist for a qemu
> run so it is
> > better to check for this. However ...
> >
> > I'm not able to get it with macros.find(). What's the right way to find
> it?
>
> Find should work and `get` should also work and may be simpler.
>
> > Also, there's a 'cov_format' in testing.mc  that is
> hardcoded
> > to 'QEMU'. Can this value be updated from the cfg files ?
>
> I do not mind but maybe this logic is not needed if you can create the
> command
> line in a .cfg file. This means you can bring the needed options together
> from
> the BSP file which could hold the `-f TSIM` option you need and the code
> here is
> common for all coverage.
>
> > > +command = exe + ' -S ' + symbol_file + \
> > > +  ' -O ' + covoar_result_dir + \
> > > +  ' -E ' + self.explanations_txt + \
> > > +  ' -p ' + self.project_name + ' ' +
> self.executables
> > > +else:
> > > +command = exe + ' -S ' + symbol_file + \
> > > +  ' -O ' + covoar_result_dir + \
> > > +  ' -E ' + self.explanations_txt + \
> > > +  ' -f TSIM' + \
> > > +  ' -p ' + self.project_name + ' ' +
> self.executables
> >
> > ... I would prefer the command be managed in the config files and
> this code
> > removed. Do you think this can be done?
> >
> > the exe and the symbol_files are generated by the script itself. I think
> we have
> > to call covoar from the script only.
>
> That is fine, it is just the command line that I am asking about.
>
> something like the attached patch?

> Chris
>
From 33939f89efd1b876b69401e11362bf482af2bdde Mon Sep 17 00:00:00 2001
From: Vijay Kumar Banerjee 
Date: Fri, 1 Feb 2019 01:01:42 +0530
Subject: [PATCH v2] Coverage: Add support for TSIM format

---
 tester/rt/coverage.py   | 31 ++---
 tester/rtems/testing/bsps/leon3-sis-cov.ini | 12 
 2 files changed, 28 insertions(+), 15 deletions(-)

diff --git a/tester/rt/coverage.py b/tester/rt/coverage.py
index 9fc9b64..846b098 100644
--- a/tester/rt/coverage.py
+++ b/tester/rt/coverage.py
@@ -45,6 +45,7 @@ from rtemstoolkit import path
 from rtemstoolkit import log
 from rtemstoolkit import execute
 from rtemstoolkit import macros
+from rtemstoolkit import version
 
 
 import options
@@ -288,14 +289,20 @@ class covoar(object):
 '''
 Covoar runner
 '''
-def __init__(self, base_result_dir, config_dir, executables, explanations_txt, trace, prefix):
+def __init__(self,
+ base_result_dir,
+ config_dir,
+ executables,
+ trace,
+ prefix,
+ covoar_cmd):
 self.base_result_dir = base_result_dir
 self.config_dir = config_dir
 self.executables = ' '.join(executables)
-self.explanations_txt = explanations_txt
-self.project_name = 'RTEMS-5'
+self.project_name = 'RTEMS-' + str(version.version())
 self.trace = trace
 self.prefix = prefix
+self.covoar_cmd = covoar_cmd
 
 def _find_covoar(self):
 covoar_exe = 'covoar'
@@ -317,9 +324,11 @@ class covoar(object):
 raise error.general('coverage: no symbol set file: %s'% (symbol_file))
 exe = self._find_covoar()
 command = exe + ' -S ' + symbol_file + \
-  ' -O ' + covoar_result_dir + \
-  ' -E ' + self.explanations_txt + \
-  ' -p ' + self.project_name + ' ' + self.executables
+   ' -O ' + covoar_result_dir + \
+   ' -p ' + self.project_

Re: How to submit hello world proof?

2019-02-06 Thread Vijay Kumar Banerjee
On Wed, 6 Feb 2019 at 13:40, Ravindra Meena  wrote:

> Hi,
>
> Hello Ravindra,

> I have completed the GSOC getting started and have modified the hello
> world program. Now I would like to submit proof. How should I proceed?
>
>  Great!
generate a patch of your modification, using the `git format-patch` command
and send it to
j...@rtems.org along with a screenshot of your working hello world.

> Thanks
>
> --
> *Ravindra Kumar Meena*,
> B. Tech. Computer Science and Engineering,
> Indian Institute of Technology (Indian School of Mines)
> , Dhanbad
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH] Coverage: Add support for TSIM format

2019-02-06 Thread Chris Johns
On 6/2/19 7:24 pm, Vijay Kumar Banerjee wrote:
> @@ -317,9 +324,11 @@ class covoar(object):
>  raise error.general('coverage: no symbol set file: %s'% 
> (symbol_file))
>  exe = self._find_covoar()
>  command = exe + ' -S ' + symbol_file + \
> -  ' -O ' + covoar_result_dir + \
> -  ' -E ' + self.explanations_txt + \
> -  ' -p ' + self.project_name + ' ' + self.executables
> +   ' -O ' + covoar_result_dir + \
> +   ' -p ' + self.project_name + \
> +   ' ' + self.executables + ' '

Can all these be placed in a macro variable and then accessed here?

Maybe in defaults.mc?

Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel


Re: [PATCH] Coverage: Add support for TSIM format

2019-02-06 Thread Vijay Kumar Banerjee
On Wed, 6 Feb 2019 at 14:04, Chris Johns  wrote:

> On 6/2/19 7:24 pm, Vijay Kumar Banerjee wrote:
> > @@ -317,9 +324,11 @@ class covoar(object):
> >  raise error.general('coverage: no symbol set file: %s'%
> (symbol_file))
> >  exe = self._find_covoar()
> >  command = exe + ' -S ' + symbol_file + \
> > -  ' -O ' + covoar_result_dir + \
> > -  ' -E ' + self.explanations_txt + \
> > -  ' -p ' + self.project_name + ' ' + self.executables
> > +   ' -O ' + covoar_result_dir + \
> > +   ' -p ' + self.project_name + \
> > +   ' ' + self.executables + ' '
>
> Can all these be placed in a macro variable and then accessed here?
>
> Maybe in defaults.mc?
>
I tried this but it seems like all these need bsp name or version. So we
can't add them in default.mc
or testing.mc. If we want to move it to the configuration files then we'll
have to add it in the bsp ini file (like the explanations file has been
added ). Do we want to have it in bsp file? It might make the ini file
complicated.


>
> Chris
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Fwd: [rtems commit] fs: Add struct dirent::d_type support

2019-02-06 Thread Jiri Gaisler
This patch breaks jffs2_fsscandir01 on griscv:

*** BEGIN OF TEST FSSCANDIR JFFS2 ***
*** TEST VERSION: 5.0.0.03fcbb15d24e2eec41bac9f5dee30bbf7dc888b8-modified
*** TEST STATE: EXPECTED-PASS
*** TEST BUILD: RTEMS_NETWORKING RTEMS_POSIX_API RTEMS_SMP
*** TEST TOOLS: 9.0.1 20190128 (RTEMS 5, RSB 
c41b9d0df7e5b4a5056ca50c2534380a44e92769, Newlib 3b2133317)
Initializing filesystem JFFS2
/home/jiri/ibm/src/rtems/rtems/c/src/../../testsuites/fstests/fsscandir01/init.c:
 49 2 <= n || n == 4

*** FATAL ***
fatal source: 5 (RTEMS_FATAL_SOURCE_EXIT)


Works OK on SPARC however. Could somebody please test this on qemu/riscv32 so I 
would know if it is a generic RISCV issue or a problem in sis-riscv?

Thanks, Jiri.


 Forwarded Message 
Subject:[rtems commit] fs: Add struct dirent::d_type support
Date:   Tue, 05 Feb 2019 09:17:21 +
From:   Sebastian Huber 
Reply-To:   v...@rtems.org
To: v...@rtems.org



Module: rtems
Branch: master
Commit: 03fcbb15d24e2eec41bac9f5dee30bbf7dc888b8
Changeset: 
http://git.rtems.org/rtems/commit/?id=03fcbb15d24e2eec41bac9f5dee30bbf7dc888b8

Author: Sebastian Huber 
Date: Tue Nov 27 12:45:53 2018 +0100

fs: Add struct dirent::d_type support

---

cpukit/libfs/src/dosfs/msdos_dir.c | 11 
cpukit/libfs/src/imfs/imfs_dir_default.c | 3 ++
cpukit/libfs/src/jffs2/include/linux/fs.h | 5 ++
cpukit/libfs/src/jffs2/src/fs-rtems.c | 11 ++--
cpukit/libfs/src/nfsclient/src/nfs.c | 3 ++
testsuites/fstests/fsscandir01/init.c | 89 +--
6 files changed, 91 insertions(+), 31 deletions(-)

diff --git a/cpukit/libfs/src/dosfs/msdos_dir.c 
b/cpukit/libfs/src/dosfs/msdos_dir.c
index a13caaf..fee6491 100644
--- a/cpukit/libfs/src/dosfs/msdos_dir.c
+++ b/cpukit/libfs/src/dosfs/msdos_dir.c
@@ -236,6 +236,17 @@ msdos_dir_read(rtems_libio_t *iop, void *buffer, size_t 
count)
continue;
}
+#ifdef DT_DIR
+ if ((*MSDOS_DIR_ATTR(entry)) & MSDOS_ATTR_DIRECTORY)
+ {
+ tmp_dirent.d_type = DT_DIR;
+ }
+ else
+ {
+ tmp_dirent.d_type = DT_REG;
+ }
+#endif
+
/*
* Move the entry to the return buffer
*
diff --git a/cpukit/libfs/src/imfs/imfs_dir_default.c 
b/cpukit/libfs/src/imfs/imfs_dir_default.c
index 03ef115..7bb4f37 100644
--- a/cpukit/libfs/src/imfs/imfs_dir_default.c
+++ b/cpukit/libfs/src/imfs/imfs_dir_default.c
@@ -74,6 +74,9 @@ static ssize_t IMFS_dir_read(
dir_ent->d_off = current_entry;
dir_ent->d_reclen = sizeof( *dir_ent );
dir_ent->d_ino = IMFS_node_to_ino( imfs_node );
+#ifdef DT_DIR
+ dir_ent->d_type = IFTODT( imfs_node->st_mode );
+#endif
dir_ent->d_namlen =
MIN( imfs_node->namelen, sizeof( dir_ent->d_name ) - 1 );
dir_ent->d_name[ dir_ent->d_namlen ] = '\0';
diff --git a/cpukit/libfs/src/jffs2/include/linux/fs.h 
b/cpukit/libfs/src/jffs2/include/linux/fs.h
index 8da9880..a638e7b 100644
--- a/cpukit/libfs/src/jffs2/include/linux/fs.h
+++ b/cpukit/libfs/src/jffs2/include/linux/fs.h
@@ -3,12 +3,17 @@
#include 
#include 
+#include 
#include 
+#ifdef DT_DIR
+#define RTEMS_JFFS2_HAVE_D_TYPE
+#else
#define DT_UNKNOWN 0
#define DT_DIR 4
#define DT_REG 8
#define DT_LNK 10
+#endif
#define ATTR_MODE (1U << 0)
#define ATTR_UID (1U << 1)
diff --git a/cpukit/libfs/src/jffs2/src/fs-rtems.c 
b/cpukit/libfs/src/jffs2/src/fs-rtems.c
index 17a4985..aae208c 100644
--- a/cpukit/libfs/src/jffs2/src/fs-rtems.c
+++ b/cpukit/libfs/src/jffs2/src/fs-rtems.c
@@ -423,7 +423,7 @@ static int rtems_jffs2_fstat(
return 0;
}
-static int rtems_jffs2_fill_dirent(struct dirent *de, off_t off, uint32_t ino, 
const char *name)
+static int rtems_jffs2_fill_dirent(struct dirent *de, off_t off, uint32_t ino, 
const char *name, unsigned char type)
{
int eno = 0;
size_t len;
@@ -433,6 +433,9 @@ static int rtems_jffs2_fill_dirent(struct dirent *de, off_t 
off, uint32_t ino, c
de->d_off = off * sizeof(*de);
de->d_reclen = sizeof(*de);
de->d_ino = ino;
+#ifdef RTEMS_JFFS2_HAVE_D_TYPE
+ de->d_type = type;
+#endif
len = strlen(name);
de->d_namlen = len;
@@ -466,14 +469,14 @@ static ssize_t rtems_jffs2_dir_read(rtems_libio_t *iop, 
void *buf, size_t len)
off = begin;
if (off == 0 && off < end) {
- eno = rtems_jffs2_fill_dirent(de, off, inode->i_ino, ".");
+ eno = rtems_jffs2_fill_dirent(de, off, inode->i_ino, ".", DT_DIR);
assert(eno == 0);
++off;
++de;
}
if (off == 1 && off < end) {
- eno = rtems_jffs2_fill_dirent(de, off, inode->i_parent->i_ino, "..");
+ eno = rtems_jffs2_fill_dirent(de, off, inode->i_parent->i_ino, "..", DT_DIR);
assert(eno == 0);
++off;
++de;
@@ -482,7 +485,7 @@ static ssize_t rtems_jffs2_dir_read(rtems_libio_t *iop, 
void *buf, size_t len)
while (eno == 0 && off < end && fd != NULL) {
if (fd->ino != 0) {
if (off == fd_off) {
- eno = rtems_jffs2_fill_dirent(de, off, fd->ino, fd->name);
+ eno = rtems_jffs2_fill_dirent(de, off, fd->ino, fd->name, fd->type);
++off;
++de;
}
diff --git a/cpukit/libfs/src/nfsclient/src/nfs.c 
b/cpukit/libfs/src/nfsclient/src/nfs.c
index ddb4dda..bb338d5 100644
--- a/cpukit/libfs/src/nfsclient/src/nfs.c
+++ b/cpukit/libfs/src/nfsclient/src/nfs.c
@@

RTEMs hello world proof | GSOC 2019 Aspirant

2019-02-06 Thread Ravindra Meena
Hi RTEMs developer,

I am GSOC 2019 aspirant. I have completed the hello world program and also
created the patch.

I would love to contribute more and looking forward to being GSOC 2019
student at RTEMs.

Please find the attached file for your reference.

Thank you

-- 
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
, Dhanbad
From 12c9fd371c09a20cd5ef70872760d192c1e9164d Mon Sep 17 00:00:00 2001
From: Ravindra Meena 
Date: Wed, 6 Feb 2019 18:12:14 +0530
Subject: [PATCH] Ravindra's hello world

---
 testsuites/samples/hello/init.c | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/testsuites/samples/hello/init.c b/testsuites/samples/hello/init.c
index 34ded37..29f4471 100644
--- a/testsuites/samples/hello/init.c
+++ b/testsuites/samples/hello/init.c
@@ -22,7 +22,10 @@ static rtems_task Init(
 {
   rtems_print_printer_fprintf_putc(&rtems_test_printer);
   TEST_BEGIN();
-  printf( "Hello World\n" );
+  printf( "\n\n*** GSOC HELLO WORLD TEST ***\n" );
+  printf( "This is ravindra's hello world!\n" );
+  printf( "Welcome to RTEMS and Google Summer of Code 2019\n" );
+  printf( "*** END OF GSOC HELLO WORLD TEST ***\n" );
   TEST_END();
   rtems_test_exit( 0 );
 }
-- 
2.7.4

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH] Coverage: Add support for TSIM format

2019-02-06 Thread Chris Johns
On 6/2/19 9:33 pm, Vijay Kumar Banerjee wrote:
> 
> 
> 
> On Wed, 6 Feb 2019 at 14:04, Chris Johns  > wrote:
> 
> On 6/2/19 7:24 pm, Vijay Kumar Banerjee wrote:
> > @@ -317,9 +324,11 @@ class covoar(object):
> >              raise error.general('coverage: no symbol set file: %s'%
> (symbol_file))
> >          exe = self._find_covoar()
> >          command = exe + ' -S ' + symbol_file + \
> > -                  ' -O ' + covoar_result_dir + \
> > -                  ' -E ' + self.explanations_txt + \
> > -                  ' -p ' + self.project_name + ' ' + self.executables
> > +                   ' -O ' + covoar_result_dir + \
> > +                   ' -p ' + self.project_name + \
> > +                   ' ' + self.executables + ' '
> 
> Can all these be placed in a macro variable and then accessed here?
> 
> Maybe in defaults.mc ?
> 
> I tried this but it seems like all these need bsp name or version. So we can't
> add them in default.mc 
> or testing.mc . If we want to move it to the configuration
> files then we'll have to add it in the bsp ini file (like the explanations 
> file
> has been added ). Do we want to have it in bsp file? It might make the ini 
> file
> complicated.

You can add references to the BSP's macro entry "%{bsp}" in defaults.mc. All
then need to do is expand the macro when you need it. For example:

https://git.rtems.org/rtems-tools/tree/tester/rt/config.py#n146

If you print the macros instance in the config class you will see what it
contains. For example this command:

$ /opt/work/chris/rtems/tools/rtems-tools.git/tester/rtems-run \
 --rtems-tools=/opt/work/rtems/5 --rtems-bsp=psim-run \
 `find . -name hello.exe`

 [ Added `print(self.macros)` as the first line of `def _dir_execute()` ]

The macro values of interest are:

[psim-run] w,r[]
 _target:  'none' 'none'  '%{%{bsp_arch}-rtems%{version}'
 arch: 'none' 'none'  'powerpc'
 bsp:  'none' 'none'  'psim'
 bsp_arch: 'none' 'none'  '%{arch}'
 bsp_run_cmd:  'none' 'none'
'%{rtems_tools}/%{bsp_arch}-rtems%{rtems_version}-run'
 bsp_run_opts: 'none' 'none'  '-f
%{_rtscripts}/bsps/psim-device-tree'
 console_stdio:'none' 'none'  '1'
 exe_trace:'none' 'none'  'output'
 rtems_tools:  'none' 'none'  '/opt/work/rtems/5/bin'
 rtems_version:'none' 'none'  '5'
 run_cmd:  'none' 'none'
'/opt/work/rtems/5/bin/powerpc-rtems5-run'
 run_opts: 'none' 'none'  '-f
/opt/work/chris/rtems/tools/rtems-tools.git/tester/rtems/testing/bsps/psim-de \
  vice-tree'
 test_disable_header:  'none' 'none'  '1'
 test_executable:  'none' 'none'
'./powerpc-rtems5/c/psim/testsuites/samples/hello.exe'
 test_executable_opts: 'none' 'none'  ''
 test_index:   'none' 'none'  '1'
 test_total:   'none' 'none'  '1'
 tester:   'none' 'none'  '%{_rtscripts}/run.cfg'

This means in `defaults.mc` you can use `%{arch}-%{bsp}` etc and if you expand
the macro the values will be recursively resolved.

Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

OAR is standing up hardware testing capabilities / EVB5200 issue

2019-02-06 Thread Lou Woods
Hi,

With the help of Chris Johns and Joel Sherrill, I've set up a means to download 
and test the RTEMS test suite on the BeagleBone Black and Freescale EVB5200B 
(Icecube).  The BBB passed 569 of the 590 tests. There were 12 failures, but 
these could be test framework related.  I haven't investigated them yet.  I 
appreciate your help guys.

I'm having issues with the EVB5200 though.  Of the 591 tests only 1 passed.  
Each test I investigated simply reset the board as soon as U-Boot transferred 
control.  I'm using the latest icecube BSP build fresh from the git master.  
The log snippet at the bottom is from RTEMS tester and demonstrates a typical 
failure.  As seen below I'm using the load address 0x100 and the entry 
point 0x4 per the wiki page: https://devel.rtems.org/wiki/TBR/BSP/Gen5200

The only test that passes is the minimum test.  I've also manually built hello 
and tested it outside of the test framework with the same result.  Any ideas?

Here is the mkimg script:
$ cat bin/rtems-icecube-mkimg
#! /bin/sh

OBJCOPY_FOR_TARGET=powerpc-rtems5-objcopy
OBJCOPY="$OBJCOPY_FOR_TARGET"

START_ADDR=0x4
ENTRY_ADDR=0x4

for EXE_NAME in $*
do
  if [ ! -f $EXE_NAME ]; then
   echo "error: not found: $EXE_NAME"
   exit 1
  fi
  echo "Image: $EXE_NAME"
  ${OBJCOPY} -R -S -O binary "$EXE_NAME" "$EXE_NAME.bin" || exit 1
  cat "$EXE_NAME.bin" | gzip -9 >"$EXE_NAME.gz"
  mkimage \
   -A ppc -O rtems -T kernel -a $START_ADDR -e $ENTRY_ADDR -n "RTEMS" \
   -d "$EXE_NAME.gz" "$EXE_NAME.img"
done

exit 0

The EVB5200 U-Boot boot command is:
bootcmd=dhcp; setenv serverip 192.168.1.94; tftp 100 icecube.img; bootm; 
reset


Tester run log snippet:
=>  tftp: ./powerpc-rtems5/c/icecube/testsuites/benchmarks/linpack.exe.img
] BOOTP broadcast 1
] DHCP client bound to address 192.168.1.82
] Using FEC ETHERNET device
] TFTP from server 192.168.1.94; our IP address is 192.168.1.82
] Filename 'icecube.img'.
] Load address: 0x100
] Loading: #
] done
] Bytes transferred = 66040 (101f8 hex)
] ## Booting image at 0100 ...
]Image Name:   RTEMS
]Image Type:   PowerPC RTEMS Kernel Image (gzip compressed)
]Data Size:65976 Bytes = 64.4 kB
]Load Address: 0004
]Entry Point:  0004
]Uncompressing Kernel Image ... OK
] ## Transferring control to RTEMS (at address 0004) ...
]
]
] U-Boot 1.1.3 (Apr  5 2006 - 21:06:06)
]
] CPU:   MPC5200 v2.2 at 462 MHz
]Bus 132 MHz, IPB 132 MHz, PCI 33 MHz
] Board: Freescale MPC5200 (Lite5200B)

Thanks for any help you can provide,
Lou
OARCorp
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: Fwd: [rtems commit] fs: Add struct dirent::d_type support

2019-02-06 Thread Sebastian Huber

On 06/02/2019 11:47, Jiri Gaisler wrote:


This patch breaks jffs2_fsscandir01 on griscv:

*** BEGIN OF TEST FSSCANDIR JFFS2 ***
*** TEST VERSION: 5.0.0.03fcbb15d24e2eec41bac9f5dee30bbf7dc888b8-modified
*** TEST STATE: EXPECTED-PASS
*** TEST BUILD: RTEMS_NETWORKING RTEMS_POSIX_API RTEMS_SMP
*** TEST TOOLS: 9.0.1 20190128 (RTEMS 5, RSB 
c41b9d0df7e5b4a5056ca50c2534380a44e92769, Newlib 3b2133317)


Sorry, I missed to update the Newlib for the or1k and riscv targets. 
Please update the RSB and rebuild the riscv tools.


--
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail  : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel